On Thursday 26 November 2015 18:15:26 James wrote: > And this is an different approach suggesting for Peter's Chrony issues > so it might warrant a new thread anyway. > > <snip> > 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 > <end/snip> > > So, a while back the excellent tools of trace-cmd and kernelshark (part of > trace-cmd) were added to the portage tree. > > Here is a little 'diddy' that might get you going [1]. Also, there is much > posted on the use of ftrace, trace-cmd and kernelshark. These very > powerful tools take a while to master. Often, I try to recreate deep > performance problems on minimal system, just to reduce the amount of data > one has to parse. --->8 > [1] > http://fabbritech.blogspot.com/2013/11/using-ftrace-and-kernelshark-part-2 > .html
Thanks anyway, but it turns out to have been a spurious parameter in the init script (see my other message). -- Rgds Peter
