On Thu, 20 Sep 2007 12:59:04 -0700, Dennis Peterson wrote: > micah wrote: > > >> You will note that i've tried -HUP, -USR1 and -USR2. >> >> I still do appreciate your replies, >> micah > > I got out the source code for a quick read and didn't see anywhere in > there where signals would force reloading the config file. Given that it > can result in inconsistent results I question the wisdom of even trying > it. For example - change the run-as user to say, root, then send a > signal (assuming one exists) to a clamd process currently running as > user clamav. No way is it going to be able to su to user root (or any > other user for that matter).
I'm not sure why I didn't pull out the source and look, that would have been the easiest. I understand your point regarding inconsistent results, but that can be handled in the same ways that other services that provide this functionality handle it. If its a variable that has an ambiguity in terms of inconsistencies as you describe then a reload of the config files simply doesn't make that change, only a restart can change them. Having a graceful way of reloading configuration files, without restarting the entire service is very useful in environments where you do not want to have any service interruption when you just need to change something trivial. micah _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
