> 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
[...]
