On Thu, 2024-06-20 at 22:59 +0200, Ekaitz Zarraga wrote:
> Hi,
>
> On 2024-06-20 22:54, Andreas Enge wrote:
> > Am Thu, Jun 20, 2024 at 07:42:44PM +0100 schrieb Dale Mellor:
> > > I'm sure guix lint tried to push my code out to them the last time I
> > > tr
On Thu, 2024-06-20 at 19:00 +0200, Andreas Enge wrote:
> Am Wed, Jun 19, 2024 at 09:36:29AM +0100 schrieb Dale Mellor:
> > No, it's not. I use Guix as a tool to develop my own projects, private
> > and
> > personal for reasons I'm keeping to myself.
On Tue, 2024-06-18 at 07:19 -0700, Ian Eure wrote:
> Hi MSavoritias,
>
> Thank you for the email.
>
> I’m going to lay out this situation as clearly as I can, in the
> hope that others will better understand, and hopefully treat it
> with the seriousness it deserves.
>
> 1. Guix requests SWH t
Hello Carlo,
On Tue, 2024-02-06 at 23:10 +1100, Carlo Zancanaro wrote:
> The nginx{,-upstream,-server}-configuration records have fields for
> {extra,raw}-content, which do allow arbitrary configuration lines to
> be
> added to their config. I think this is a sensible escape hatch to
> have
> to p
Hello,
I am in the process of moving my production machine
to a pure Guix setup, and feeling some pain which I
feel is somewhat unnecessary.
There are two extremes supported by the Guix system
in configuring services: either a native application
configuration file is given and used verbatim
On Mon, 2016-11-07 at 09:53 +0100, Ludovic Courtès wrote:
> Hi,
>
> Carlo Zancanaro skribis:
>
> > I've had problems with Shepherd and its daemonize action. If I run
> > daemonize (as the first thing when Shepherd starts) then it fails to handle
> > signals from child processes.
>
> Could it be
I'm running shepherd stand-alone in a Debian system. But I am seeing
zombie processes which have been kicked off by shepherd, and they do not
get re-spawned.
Any suggestions?
