Where I'm at we are using rsync to keep some stuff in sync (duh!).
The remote (source) machine we may or may not have easy root
access to, and we'd really rather not have to go there.
So, I'm running rsync as a daemon under my userid.
Obviously, not wanting to be root over there, we are not putting
anything in the startup scripts to start up rsync. So, IF
the machine gets rebooted we need to restart rsyncd (as it were).
(The reason for all this sillyness has to do with rsh permissions
for the userid that must actually perform the writing of the files
over here, and our inability - REGARDLESS of anything else - to
be able to allow rsh or ssh to work between the machines without
passwords. Lets not go there ;-)
We have our copy job scheduled via cron.
So, what I wanted to do was to start rsync up as a daemon sometime
BEFORE the cron job-based copy script runs, if its not already
running.
No problem, I say - just have a little script that checks over
there to see if rsync is running, and if NOT fire it off with...
rsh!
OOPS! Rsync checks and says "Oh, look, stdin is a socket, I'll NOT
go into daemon mode and instead talk over that socket". Not at all
what I need.
So, I modified the source (Luke ;-) and added one more option:
--force-non-inetd
which means "Look, I don't care if stdin IS a socket, if I say
--daemon then I *MEAN* --daemon, regardless of where stdin happens
to be pointing!" (ie --force-non-inetd will do NOTHING unless
you also say --daemon)
Is this (really minor) patch worth sending along to the list?
Does anyone else want such a thing?
Can someone come up with a better option string than 'force-non-inetd'???
Thanks!
rc
Rusty Carruth Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
Voice: (480) 345-3621 SnailMail: Schlumberger ATE
FAX: (480) 345-8793 7855 S. River Parkway, Suite 116
Ham: N7IKQ @ 146.82+,pl 162.2 Tempe, AZ 85284-1825
ICBM: 33 20' 44"N 111 53' 47"W
