Thanks, that worked. And yes, that is truely odd. I wonder how many scripts
were rendered useless because of this change... :)
I have a new problem however. amdump works, but only for one disk.
All of the disks to be backed up are on the same machine (the tape server and
client are the same in this case) but only one directory get's backed up.
The others just don't. The e-mail report comes back like this for all but 1
share:
192.168.1. /usr/local lev 0 FAILED [disk /usr/local offline on 192.168.1.10?]
There is no difference between the entry in disklist that works and the ones
that don't.
192.168.1.10 /home always-full
192.168.1.10 /etc always-full
192.168.1.10 /boot always-full
192.168.1.10 /root always-full
192.168.1.10 /u1 always-full *** the one that works ***
192.168.1.10 /usr/local always-full
#192.168.1.10 /mnt/win always-full
**above never ever works, commented out***
If someone could share some insight that would help me understand why this is
happening I would be grateful.
Thanks again,
Andrew
-------------------------------------------------------------
>>>>> "Toby" == Toby Bluhm <[EMAIL PROTECTED]> writes:
Toby> Hitting the PID with -HUP did not do the trick
Toby> for me.
xinetd needs a SIGUSR1 (or USR2; there is a slight difference,
check the manpage) to reload its config. SIGHUP just makes it
dump its current state to /tmp. Why they decided to do it this
way is anybody's guess :)
-- Jon
