On Wednesday 25 November 2015 19:05:44 Alan McKinnon wrote: > On 24/11/2015 17:24, Peter Humphrey wrote: --->8 > > The installation-default file causes the start-stop-daemon to catch an > > unexpected interrupt and report an error, even though the chronyd > > process > > continues to run. > > > > Any time I run 'strace -ff -o/tmp/chronyd.strace /etc/init.d/chronyd > > start' the init process runs normally and I'm left with scores of trace > > files, none of which help because the stray interrupt wasn't detected. --->8 > Ugh, don't you just hate issues like that? The problem with "solutions" > like start-stop-daemon is they have to deal with whatever the daemon > feels like returning (an infinite number of permutations), so support > for daemon is never complete.
I've been offered one suggestion which will need me to make a local overlay with a small code change. I'll try that and see what happens. > Regardless of what one thinks of systemd, this is one of the things it > set out to deal with. There's only one way to start something, and it > behaves one way, making behaviour considerably more predictable. So it does occasionally have one benefit then. > [ A bit of a rant I know, but I'm still smarting from years of rancid > and Cisco logins - basically the same kind of problem you are having on > a much larger scale...] I'll be content with my tiny scale, thanks very much :) -- Rgds Peter
