Future RSYNC enhancement/improvement suggestions

[Martin Pool]

On 22 Apr 2002, Jan Rafaj <rafaj at cedric.vabo.cz> wrote:
> 
> 
> On Mon, 22 Apr 2002, Stefan Nehlsen wrote:
> 
> > On Fri, Apr 19, 2002 at 12:23:06PM +0200, Jan Rafaj wrote:
> >
> > > - perhaps if the network connection between rsync client and server
> > >   stalls for some reason, implement something like 'tcp keepalive'
> > >   feature ?

TCP connections don't timeout anyhow.  Possibly a dial-on-demand line
or a firewall might drop the connection, but there should be enough
traffic that this is not a problem.

> PS: 4th point - how about adding feature that would enable rsync
> to store the PID of the running process somewhere ? (like,
> I hate to 'ps ax | grep' for the rsync on a machine where
> other rsync instances might be running, controlled by other means
> than my script :)

For the daemon you can use the "pid file" configuration option.  For
clients, you should just remember the pid when you create the process,
e.g. by using the $! shell special parameter.  There's no
straightforward means to find out the pid of the remote child, but I'm
not really convinced that's very important.  If you're debugging rsync
it's fairly easy to do by peeking into /proc, using lsof, or some
similar os-dependent mechanism.

-- 
Martin