Hi, Thanks for this useful utility. I've installed collectl 3.6.5 to run as a daemon to monitor the system resources of my embedded product.
Unfortunately the busybox start-stop-daemon [1] my system uses only accepts the --test option with the --stop option, not --start. As such I've made the attached use_stop_to_test_if_running.patch patch. I believe using --test with --stop would be safe in all installations using the start-stop-daemon. [1] http://git.busybox.net/busybox/tree/debianutils/start_stop_daemon.c I have another issue, I don't think much can be done about it, but if anyone can suggest anything, it would be greatly appreciated. collectl takes a fairly long time to start, during which the CPU is very busy. Even on my fast desktop, it can take almost a second to start. This is easily seen just by requesting help, see following examples. Is this simply the time required for perl to parse the source files? Would it be possible to separate the code required for playback mode from that of daemon/capture mode? root@centaur-3_0009:~# time collectl --help > /dev/null real 0m30.418s user 0m23.880s sys 0m1.990s root@centaur-3_0009:~# time collectl --help > /dev/null real 0m21.656s user 0m18.200s sys 0m0.880s Except for the above, everything works wonderfully. Thanks again for the fine utility. -- Chris
use_stop_to_test_if_running.patch
Description: Binary data
------------------------------------------------------------------------------ Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________ Collectl-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/collectl-interest
