Re: was code added to detect or die on sighup recently?

Kevin Korb wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any non-daemon software is supposed to exit (and cleanup) when hit with a hangup signal. Pretty sure it isn't new to rsync. But I didn't send it a hangup signal. By calling snaprun in a subshell (snaprun "$@" https://l

Re: was code added to detect or die on sighup recently?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Any non-daemon software is supposed to exit (and cleanup) when hit with a hangup signal. Pretty sure it isn't new to rsync. On 08/04/2014 08:12 PM, L. A. Walsh wrote: > > I have a script that normally runs my snapshot that I haven't used > for the p

was code added to detect or die on sighup recently?

I have a script that normally runs my snapshot that I haven't used for the past several days because something seemed to be going wrong and I wanted to run things manually. But running the script twice today, I got: snaphome Found 15 mounted dated, snaps or snap archives »[snapper#2120]base_m

[Bug 6672] transfer & set nano-second times on files

https://bugzilla.samba.org/show_bug.cgi?id=6672 --- Comment #2 from Teodor Milkov 2014-08-04 08:24:25 UTC --- Maybe the easiest fix here would be, to extend cmp_time() in util.c to receive two more parameters: file1_st_mtimensec and file2_st_mtimensec? I guess this is not going to be portable...