home-shepherd is flooding tty

  • Done
  • quality assurance status badge
Details
2 participants
  • Dariqq
  • Ludovic Courtès
Owner
unassigned
Submitted by
Dariqq
Severity
normal
D
D
Dariqq wrote on 24 Jul 18:16 +0200
(address . bug-guix@gnu.org)
e311cffc-3202-4e51-a2e5-82c9deca765a@posteo.net
Hi,

Today I connected to my laptop running guix home over ssh as the first
session and got greeted with a lot of shepherd logs from the
on-first-login script from guix-home starting the user shepherd:



Starting service root...
Service root started.
Service root running with value #t.
Service root has been started.
WARNING: Use of `load' in declarative module (#{ g107}#). Add
#:declarative? #f to your define-module invocation.
Daemonizing...

Some deprecated features have been used. Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information. Set it to "no" to suppress
this message.
Restarting signal handler.
Now running as process 2026.
Starting services...
Configuration successfully loaded from
'/gnu/store/004jm8s9km3j70gh4nhw8fzlbjls5wxa-shepherd.conf'.
Starting service dbus...
Service dbus has been started.
Service dbus started.
Service dbus running with value 2027.
[...]
Successfully started 4 services in the background.



As I don't want to see these messages I have patched the
add-shell-profile-file procedure in gnu/home/services/shells.scm to send
the output of the on-first-login-script into the void as a workaround.

The shepherd manual mentions a --quit option (there seems to be also
--silent but not documented). Looking at the shepherd code though these
don't seem to do anything which is also not mentioned anywhere causing
even more confusion.
D
D
Dariqq wrote on 16 Sep 15:23 +0200
(address . 72277@debbugs.gnu.org)
65ff85e1-644a-4f8d-9c46-25d6e98b569d@posteo.net
On 24.07.24 18:16, Dariqq wrote:
Toggle quote (35 lines)
> Hi,
>
> Today I connected to my laptop running guix home over ssh as the first
> session and got greeted with a lot of shepherd logs from the on-first-
> login script from guix-home starting the user shepherd:
>
>
>
> Starting service root...
> Service root started.
> Service root running with value #t.
> Service root has been started.
> WARNING: Use of `load' in declarative module (#{ g107}#).  Add
> #:declarative? #f to your define-module invocation.
> Daemonizing...
>
> Some deprecated features have been used.  Set the environment
> variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
> program to get more information.  Set it to "no" to suppress
> this message.
> Restarting signal handler.
> Now running as process 2026.
> Starting services...
> Configuration successfully loaded from '/gnu/
> store/004jm8s9km3j70gh4nhw8fzlbjls5wxa-shepherd.conf'.
> Starting service dbus...
> Service dbus has been started.
> Service dbus started.
> Service dbus running with value 2027.
> [...]
> Successfully started 4 services in the background.
>
>
>

The guile deprecation warning seems to be coming from using the
deprecated way of daemonizing the shepherd. This has been fixed in

Toggle quote (9 lines)
> As I don't want to see these messages I have patched the add-shell-
> profile-file procedure in gnu/home/services/shells.scm to send the
> output of the on-first-login-script into the void as a workaround.
>
> The shepherd manual mentions a --quit option (there seems to be also --
> silent but not documented). Looking at the shepherd code though these
> don't seem to do anything which is also not mentioned anywhere causing
> even more confusion.

The devel shepherd now understands --silent (and --quiet):


When running the shepherd@0.15 with a backported version of the above
commmit and --silent all that is left is the warning

> WARNING: Use of `load' in declarative module (#{ g107}#). Add
> #:declarative? #f to your define-module invocation.

and when using the devel shepherd this is also gone and shepherd is
completely silent.


It would be nice to add an option to home-shepherd-configuration to
autolaunch the shepherd with --silent once it is available in a tagged
release.
L
L
Ludovic Courtès wrote on 19 Sep 15:10 +0200
Re: bug#72277: home-shepherd is flooding tty
(name . Dariqq)(address . dariqq@posteo.net)(address . 72277@debbugs.gnu.org)
871q1f7psh.fsf@gnu.org
Hi,

Dariqq <dariqq@posteo.net> skribis:

Toggle quote (4 lines)
> It would be nice to add an option to home-shepherd-configuration to
> autolaunch the shepherd with --silent once it is available in a tagged
> release.

I believe we can make this change right away since 0.10.x supports
‘--silent’ (it doesn’t have any effect as of 0.10.5 but it’s not
rejected).

Would you like to prepare a patch?

Thanks,
Ludo’.
D
D
Dariqq wrote on 14 Oct 19:40 +0200
(name . Ludovic Courtès)(address . ludo@gnu.org)(address . 72277-done@debbugs.gnu.org)
7c10c6d2-9729-4a10-adbc-fc9be8c0f2e2@posteo.net
Hi Ludo,

Thank you very much for the review of the shepherd patch and the patch
for the silent? field to enable it.

Closing the original issue as well.

On 19.09.24 15:10, Ludovic Courtès wrote:
Toggle quote (16 lines)
> Hi,
>
> Dariqq <dariqq@posteo.net> skribis:
>
>> It would be nice to add an option to home-shepherd-configuration to
>> autolaunch the shepherd with --silent once it is available in a tagged
>> release.
>
> I believe we can make this change right away since 0.10.x supports
> ‘--silent’ (it doesn’t have any effect as of 0.10.5 but it’s not
> rejected).
>
> Would you like to prepare a patch?
>
> Thanks,
> Ludo’.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 72277@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 72277
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch