supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: Jonathan de Boyne Pollard <J.deBoynePollard-newsgroups@NTLWorld.COM>
To: Supervision <supervision@list.skarnet.org>
Subject: svscan --help
Date: Thu, 31 Jan 2019 21:53:13 +0000	[thread overview]
Message-ID: <f82b7e3c-ff4a-243f-a6c3-1cdb2a273f58@NTLWorld.COM> (raw)
In-Reply-To: <em4e294a5f-49fc-4789-b813-54b60b6acd90@elzian>

Laurent Bercot:
> s6-svscan is pretty mild in that aspect.

In fairness, the original Bernstein program was somewhat more forgiving:

 > /package/admin/djbwares % command/svscan --help
 > svscan: fatal: unable to chdir to --help: file does not exist
 > /package/admin/djbwares %

People used this program wrongly so often with the Bernstein tools that 
I gained a Frequently Given Answer about it in 2002.

* http://jdebp.eu./FGA/daemontools-spurious-supervise-directories.html

I take the view that if the user gives a command that takes a specific 
number of arguments the wrong number of arguments, that's an error.  A 
quick if (1 != args.size()) test saves this support pain, and having to 
explain this *yet again*.

 > /package/admin/nosh % command/svscan 1 2
 > svscan: FATAL: One directory name is required.
 > /package/admin/nosh % command/svscan
 > svscan: FATAL: One directory name is required.
 > /package/admin/nosh % command/svscan /dev/null
 > svscan: FATAL: /dev/null: Not a directory
 > /package/admin/nosh %

I defined the directory argument as mandatory in service-dt-scanner, 
a.k.a. svscan, though.

 > /package/admin/nosh % command/svscan --help
 > Usage: svscan [-?] [--help] [--usage] [--input-activation] {directory}
 >
 > Main options:
 >     --input-activation Use input activation for log services.
 > /package/admin/nosh %

It's not exactly the same program, after all.

* http://jdebp.eu./Softwares/nosh/guide/commands/service-dt-scanner.xml

* http://jdebp.eu./Softwares/djbwares/guide/commands/svscan.xml

Users should indeed read the doco.  It is written to be read.  (-:


  reply	other threads:[~2019-01-31 21:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-31 18:32 s6 bites noob Kelly Dean
2019-01-31 18:46 ` Kelly Dean
2019-01-31 20:19 ` Laurent Bercot
2019-01-31 21:53   ` Jonathan de Boyne Pollard [this message]
2019-02-01  0:36   ` Laurent Bercot
2019-02-01  4:18     ` Kelly Dean
2019-02-01  5:27       ` Colin Booth
2019-02-01  5:29       ` Colin Booth
2019-02-03  8:53   ` Kelly Dean
2019-02-03 10:19     ` Laurent Bercot
2019-02-04  7:42       ` Kelly Dean
2019-02-04 13:52         ` Laurent Bercot
2019-02-05  9:26           ` Kelly Dean
2019-02-05 19:44             ` Laurent Bercot
2019-02-03 10:39     ` svscan and supervise Jonathan de Boyne Pollard

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=f82b7e3c-ff4a-243f-a6c3-1cdb2a273f58@NTLWorld.COM \
    --to=j.deboynepollard-newsgroups@ntlworld.com \
    --cc=supervision@list.skarnet.org \
    /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.
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 NNTP newsgroup(s).