From: erik quanstrom <quanstro@coraid.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Authentication questions
Date: Tue, 6 May 2008 12:09:30 -0400 [thread overview]
Message-ID: <f8406de4ac7ef9a8ff910be4c3b04854@coraid.com> (raw)
In-Reply-To: <050620081519.27908.482076F30006648500006D0422230650029B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net>
> As long as I'm at it, though, I've got a question about listen.
> It's filling a rather large logfile with lots of address in
> use errors. As I look into things, it appears that I'm starting
> listen both in /bin/cpurc and in /cfg/phantom/cpurc with the
> latter specifying the -t option. That definitely seems to
> be one too many. It looks from what I've got that I should
> comment out the one in /bin/cpurc. What is the convention
> on that?
you need to use a different directory if you're starting a second
listen with the -t option. e.g. /rc/bin/service.auth. there shouldn't
be any duplication in scripts (save one starting in !) between the
normal and the -t directories.
not sure if this helps, but i perfer the old style bit switch statement.
i tacked on a bit of our cpurc for reference.
- erik
fn external{
bind -b '#l1' /net.alt
bind -b '#I1' /net.alt
ip/ipconfig -x /net.alt -g 12.51.113.1 ether /net.alt/ether1 $1 /123
ndb/cs -x /net.alt -f /lib/ndb/external
switch($2){
case recursive
ndb/dns -sx /net.alt -f /lib/ndb/external
case notrecursive
ndb/dns -Rrsx/net.alt -f /lib/ndb/external
}
}
echo cpurc $sysname
switch ($sysname) {
case tyty
timesync $time
ndb/dns -s
ip/dhcpd
ip/tftpd
auth/keyfs -wp
auth/secstored >/dev/null >[2=1]
auth/cron >>/sys/log/cron >[2=1] &
aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service il
aux/listen -q -t /rc/bin/service.auth -d /rc/bin/service tcp
external 12.51.113.2 none
aux/listen -q -t /rc/bin/service.extauth -d /rc/bin/service.ext /net.alt/tcp
[...]
prev parent reply other threads:[~2008-05-06 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 18:47 Brian L. Stuart
2008-05-05 19:10 ` Christian Kellermann
2008-05-05 19:17 ` Brian L. Stuart
2008-05-05 20:07 ` Brian L. Stuart
2008-05-05 21:04 ` Steve Simon
2008-05-06 11:28 ` a
2008-05-06 15:19 ` Brian L. Stuart
2008-05-06 15:27 ` Brian L. Stuart
2008-05-06 15:48 ` a
2008-05-06 19:33 ` Brian L. Stuart
2008-05-06 16:09 ` erik quanstrom [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=f8406de4ac7ef9a8ff910be4c3b04854@coraid.com \
--to=quanstro@coraid.com \
--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).