From: Danny Milosavljevic <dannym@scratchpost.org>
To: Jan <tona_kosmicznego_smiecia@interia.pl>
Cc: guix-devel@gnu.org
Subject: Re: Install script supporting sysV init?
Date: Tue, 28 Jan 2020 15:52:34 +0100 [thread overview]
Message-ID: <20200128155234.2ca6b419@scratchpost.org> (raw)
In-Reply-To: <20200128140655.26042789@kompiuter>
[-- Attachment #1: Type: text/plain, Size: 757 bytes --]
Hi Jan,
cool!
Could you try what happens in the corner cases:
(1) Try to start it twice. The second start attempt should fail and $? should reflect that
(2) Try to stop it twice. I'm pretty sure that should work (do nothing) the second time. What does sysv say should happen? Should it error?
(3) Does status work?
(4) Put a nonsensical (non-existent) pid into the pid file and try to stop it. Or start it. What does sysv say should happen? Should it clean up?
If the pid of the wrong process is in the pid file and one tries to stop it or start it, what does sysv say should happen? Should one check the args whether it's the correct program?
If these things are handled correctly, we can add it to guix master.
BR,
Danny
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-01-28 14:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-26 22:02 Install script supporting sysV init? Jan
2020-01-26 22:38 ` Danny Milosavljevic
2020-01-27 16:09 ` Jan
2020-01-27 18:05 ` Julien Lepiller
2020-01-28 13:06 ` Jan
2020-01-28 14:52 ` Danny Milosavljevic [this message]
2020-01-28 15:25 ` Danny Milosavljevic
2020-01-28 22:54 ` Jan
2020-01-28 22:58 ` Danny Milosavljevic
2020-01-28 23:07 ` Jan
2020-01-28 23:19 ` Danny Milosavljevic
2020-01-30 14:11 ` Jan
2020-01-28 10:34 ` Ludovic Courtès
2020-02-05 19:44 ` Joshua Branson
2020-02-05 20:10 ` Jan
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200128155234.2ca6b419@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).