On Sat, Jan 02, 2021 at 11:41:52AM -0800, Wayne Davison
wrote:
> On Fri, Jan 1, 2021 at 2:13 PM raf wrote:
>
> > maybe the pidfile should be locked
> >
>
> https://download.samba.org/pub/rsync/NEWS#3.2.0
>
> ..wayne..
lovely. it must have been an old version.
cheers,
raf
--
Please use
On Fri, Jan 1, 2021 at 2:13 PM raf wrote:
> maybe the pidfile should be locked
>
https://download.samba.org/pub/rsync/NEWS#3.2.0
..wayne..
--
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options:
On Fri, Jan 01, 2021 at 11:31:11AM +, Chris Green via rsync
wrote:
> Francis.Montagnac--- via rsync wrote:
> >
> > Hi.
> >
> > On Fri, 01 Jan 2021 09:57:38 + Chris Green via rsync wrote:
> >
> > > My backup system crashed a couple of nights ago due to a power cut
> > > (can't really
Francis.Montagnac--- via rsync wrote:
>
> Hi.
>
> On Fri, 01 Jan 2021 09:57:38 + Chris Green via rsync wrote:
>
> > My backup system crashed a couple of nights ago due to a power cut
> > (can't really blame it!) and I went and restarted it after the power
> > came back. However, as I note
Hi.
On Fri, 01 Jan 2021 09:57:38 + Chris Green via rsync wrote:
> My backup system crashed a couple of nights ago due to a power cut
> (can't really blame it!) and I went and restarted it after the power
> came back. However, as I note above, files in /home/chris/tmp/pid
> aren't cleared
I just got bitten by a (fairly) subtle problem due to having an
inappropriate location for 'pid file' in my rsyncd.conf.
What I had was:-
pid file = /home/chris/tmp/pid
This works fine until the system running rsync in daemon mode crashes
rather than being properly shut down. The pid file
