all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: EuAndreh <eu@euandre.org>
To: Adam Kandur <kefironpremise@gmail.com>,
	Liliana Marie Prikler <liliana.prikler@gmail.com>,
	guix-devel@gnu.org
Subject: Re: trying to write my own herd service
Date: Sat, 05 Nov 2022 10:26:20 -0300	[thread overview]
Message-ID: <166765478019.6444.8967244068283208603@localhost> (raw)
In-Reply-To: <bc84b6284ad3a8091804235eaedc26073c3e9588.camel@gmail.com>

> >          (start #~(make-forkexec-constructor
> >                    (list
> >                     (string-append
> > #$go-github-com-KefirTheAutomator-daemon "/bin/daemon")
> >                     " -pidFile=/var/run/my-daemon.pid"
> >                     " -logFile=/var/log/my-daemon.log")))

[...]

> Your process probably dies too often, thus causing shepherd to disable
> it.

I'd guess that it is dying too often because it is failing to be launched.  The
extra spaces before the "-pidFile" and "-logFile" arguments aren't ignored, like
when in a shell, but are included explicitly.  A contrived equivalent example
is:

    $ ls -l
    total 36
    drwxr-xr-x  6 andreh users 4096 Nov  4 19:42 Desktop
    drwxr-xr-x  7 andreh users 4096 Oct 31 21:07 Documents
    ...
    $ ls '-l'
    total 36
    drwxr-xr-x  6 andreh users 4096 Nov  4 19:42 Desktop
    drwxr-xr-x  7 andreh users 4096 Oct 31 21:07 Documents
    ...
    $ ls ' -l'
    ls: cannot access ' -l': No such file or directory

I believe that a similar thing is happening to the options to your program, and
it is failing to execute because of that.  You could confirm it by looking that
the logs.


      reply	other threads:[~2022-11-05 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 23:21 trying to write my own herd service Adam Kandur
2022-11-05  9:02 ` Liliana Marie Prikler
2022-11-05 13:26   ` EuAndreh [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=166765478019.6444.8967244068283208603@localhost \
    --to=eu@euandre.org \
    --cc=guix-devel@gnu.org \
    --cc=kefironpremise@gmail.com \
    --cc=liliana.prikler@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.