GNU Shepherd 0.9.0 released

GNU Shepherd 0.9.0 released

[Ludovic Courtès]

[-- Attachment #1: Type: text/plain, Size: 3504 bytes --]

We are pleased to announce the GNU Shepherd version 0.8.1.  This release
represents 49 commits by 3 people, bringing a new concurrent,
event-driven core, improved logging, and on-demand service startup.


• About

  The GNU Daemon Shepherd or GNU Shepherd is a service manager written
  in Guile that looks after the herd of system services.  It provides a
  replacement for the service-managing capabilities of SysV-init (or any
  other init) with a dependency-based system with a convenient
  interface.  The GNU Shepherd may also be used by unprivileged users to
  manage per-user daemons (e.g., tor, privoxy, mcron, etc.)  It is
  written in Guile Scheme, and is configured and extended using Guile.

  The GNU Shepherd is developed jointly with the GNU Guix project; it is
  used as the init system of Guix, GNU’s advanced GNU/Linux distribution.

  https://www.gnu.org/software/shepherd/


• Download

  Here are the compressed sources and a GPG detached signature[*]:
    https://ftp.gnu.org/gnu/shepherd/shepherd-0.9.0.tar.gz
    https://ftp.gnu.org/gnu/shepherd/shepherd-0.9.0.tar.gz.sig

  Use a mirror for higher download bandwidth:
    https://ftpmirror.gnu.org/shepherd/shepherd-0.9.0.tar.gz
    https://ftpmirror.gnu.org/shepherd/shepherd-0.9.0.tar.gz.sig

  Here are the SHA1 and SHA256 checksums:

  df84c15e21b00e6237af1c243ff77dfee2373626  shepherd-0.9.0.tar.gz
  c180778397694fccc051606d97ab646c8cb07e9d65712e21f154e8155986bce5  shepherd-0.9.0.tar.gz

  [*] Use a .sig file to verify that the corresponding file (without the
  .sig suffix) is intact.  First, be sure to download both the .sig file
  and the corresponding tarball.  Then, run a command like this:

    gpg --verify shepherd-0.9.0.tar.gz.sig

  If that command fails because you don't have the required public key,
  then run this command to import it:

    gpg --keyserver keys.openpgp.org \
        --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5

  and rerun the 'gpg --verify' command.

  This release was bootstrapped with the following tools:
    Autoconf 2.71
    Automake 1.16.5
    Makeinfo 6.7
    Help2man 1.48.5


• Changes since version 0.8.1 (excerpt from the NEWS file)

  ** The Shepherd now depends on Fibers 1.1.0 or later
  ** ‘shepherd’ no longer blocks when waiting for PID files, etc.
  ** Services without #:log-file have their output written to syslog
  ** Services with #:log-file have their output timestamped
  ** New ‘make-inetd-constructor’ procedure for inetd-style services
  ** New ‘make-systemd-constructor’ for systemd-style “socket activation”
  ** New ‘start-in-the-background’ procedure
  ** Services can now be “transient” (see the manual for details)
  ** New #:supplementary-groups parameter for ‘make-forkexec-constructor’
  ** New #:create-session? parameter for ‘make-forkexec-constructor’
  ** New #:resource-limits parameter for ‘make-forkexec-constructor’
  ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
  ** Do not reboot upon ‘quit’ when running as root but not PID 1
  ** Improved documentation and examples
  ** The Shepherd can no longer be built with Guile 2.0
  ** Work around Guile 3.0.[5-7] compiler bug
     (<https://bugs.gnu.org/47172>)
  ** Updated translations: da, de, sv, uk

Please report bugs to bug-guix@gnu.org.
Join guix-devel@gnu.org for discussions.

Ludovic, on behalf of the Shepherd herd.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

Re: GNU Shepherd 0.9.0 released

[Zhu Zihao]

[-- Attachment #1: Type: text/plain, Size: 434 bytes --]


Ludovic Courtès <ludo@gnu.org> writes:

> [[PGP Signed Part:Undecided]]
> We are pleased to announce the GNU Shepherd version 0.8.1.  This release
> represents 49 commits by 3 people, bringing a new concurrent,
> event-driven core, improved logging, and on-demand service startup.

"version 0.8.1"

A bug here? :)

-- 
Retrieve my PGP public key:

  gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F

Zihao

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]

Re: GNU Shepherd 0.9.0 released

[Liliana Marie Prikler]

Am Mittwoch, dem 06.04.2022 um 23:25 +0200 schrieb Ludovic Courtès:
>   ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
Should that not be $XDG_STATE_DIR?


Cheers

Re: GNU Shepherd 0.9.0 released

[Brian Cully]

Liliana Marie Prikler <liliana.prikler@gmail.com> writes:

> Am Mittwoch, dem 06.04.2022 um 23:25 +0200 schrieb Ludovic Courtès:
>>   ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
> Should that not be $XDG_STATE_DIR?

	I believe it should be $XDG_STATE_HOME, in fact. See:
	https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

---[snip]---
 $XDG_STATE_HOME defines the base directory relative to which
 user-specific state files should be stored. If $XDG_STATE_HOME is
 either not set or empty, a default equal to $HOME/.local/state should
 be used.
 ---[snip]---

-bjc

bug#54828: ssh disconnects when reconfiguring system

[Vagrant Cascadian]

[-- Attachment #1: Type: text/plain, Size: 403 bytes --]

Ever since switching to a system generation using the new shepherd
0.9.0, whenever I'm reconfiguring my system over an ssh connection, the
ssh connection drops out during the switch...

I hadn't noticed this happening before using the new shepherd.

Thankfully I always use tmux or screen and can just reconnect and resume
where I left off... but it is still a bit disconcerting!


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

bug#54828: ssh disconnects when reconfiguring system

[Vagrant Cascadian]

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]

On 2022-04-09, Vagrant Cascadian wrote:
> Ever since switching to a system generation using the new shepherd
> 0.9.0, whenever I'm reconfiguring my system over an ssh connection, the
> ssh connection drops out during the switch...
>
> I hadn't noticed this happening before using the new shepherd.
>
> Thankfully I always use tmux or screen and can just reconnect and resume
> where I left off... but it is still a bit disconcerting!

This was a duplicate of https://issues.guix.gnu.org/54812

... which is in theory fixed... though other outstanding issues prevent
the fix from being verified:

  https://issues.guix.gnu.org/54833
  https://issues.guix.gnu.org/54840
  

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

Re: GNU Shepherd 0.9.0 released

[Ludovic Courtès]

Hi,

(Stripping Cc: list.)

Brian Cully <bjc@spork.org> skribis:

> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
>
>> Am Mittwoch, dem 06.04.2022 um 23:25 +0200 schrieb Ludovic Courtès:
>>>   ** Log file of unprivileged ‘shepherd’ is now under $XDG_DATA_DIR
>> Should that not be $XDG_STATE_DIR?
>
> 	I believe it should be $XDG_STATE_HOME, in fact. See:
> 	https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html
>
> ---[snip]---
>  $XDG_STATE_HOME defines the base directory relative to which
>  user-specific state files should be stored. If $XDG_STATE_HOME is
>  either not set or empty, a default equal to $HOME/.local/state should
>  be used.
>  ---[snip]---

I was referring to this commit:

  https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=c6382a6898f2851d78b675f209787c5ff9ad4320

But actually a later commit uses XDG_STATE_HOME:

  https://git.savannah.gnu.org/cgit/shepherd.git/commit/?id=ec2a0b07a6dedcbec3cf6bb7328b144a117873e8

So I guess I just got confused and made a mistake in ‘NEWS’?

Ludo’.