From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] CPURC and starting SSH
Date: Sun, 28 Apr 2013 13:57:11 +0200 [thread overview]
Message-ID: <b0b668139a669dfb3bbe1dd82ca28193@proxima.alt.za> (raw)
Unless my copy of /rc/bin/cpurc is out of date, it contains a
self-confessed "dicey check" to ensure that TCP services are not
started twice. In the list of possible candidates to be checked is
"22" (ssh, of course) which, at least in my case, is started in
/cfg/$sysname/cpurc as it may not be appropriate on all CPU servers.
I believe that "22" ought to be dropped from that list, in my
situation it caused the services not to be started, I assume my
situation is not unique.
A few additional points from my experience:
. I'm not convinced that the "dicey check" is even necessary: what
is the worst-case scenario? That a slew of error messages may
arise from a second invocation of aux/listen? I suspect even that
isn't likely. If it is, redirecting
>[2]/dev/null
would not be a novel idea.
. Eventually, the documentation starts to make sense, but there are
a few issues that can be cleared up here: netssh is essential, but
I'm not sure it belongs in /rc/bin/cpurc, it goes better in
/cfg/$sysname/cpurc, in my opinion, where it can directly precede
aux/listen -t /rc/bin/service.auth ssh
Note the "ssh" that links to "ssh22" as the name of the service
recommended in the man page. I have a feeling that this idea is
not yet cast in stone, but it is interesting.
++L
next reply other threads:[~2013-04-28 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-28 11:57 lucio [this message]
2013-04-28 13:37 ` erik quanstrom
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=b0b668139a669dfb3bbe1dd82ca28193@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@9fans.net \
/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).