So apparently the zones machine bounced up and down a couple of times today. After it finally came back up, my updates rsync cron began to fail with:
----- Start forwarded message -----
@ERROR: chroot failed
rsync error: error starting client-server protocol (code 5) at main.c(1296)
[receiver=2.6.8]
----- End forwarded message -----
when logging into the machine, I found that there was no rsync daemon running,
but rsync seemed to be trying to respond on the port. After prodding around a
bit (it would've been helpful if lsof worked), it turns out that inetd had
"rsync --daemon" as a service. Unfortunately, no matter what I tried to
disable rsync in inetd, it kept responding. So I disabled inetd instead.
The normal rsync daemon is now up and running correctly.
If someone needs inetd running, please get it to stop trying to do rsync.
/me hates Solaris 10
--
Randomly Generated Tagline:
Sattinger's Law:
It works better if you plug it in.
pgp3fkmhLU4Iu.pgp
Description: PGP signature
