You wrote: > My undertanding of the proper action for reload is to close open file > descriptors, reread configuration files, and reopen file descriptors. > clamd only closes and reopens it's log file on HUP, so it seemed to > me that it failed the test for 'supports reload'.
Indeed. > If you really > wanted to reread the configuration, you would need to stop and then > start clamd, hence the choice of force-reload being the same as > restart. Correct. > When I was setting this up, it seemed to me to be a useful shorthand > to let 'reload' reopen the log file (so that things like logrotate > would have a useful target). If that is wrong, I can change it. That seems like a useful functionality but I think it is wrong to overload the "reload" action with it. In the least, it will confuse people. Using a different name for the init script action would be better. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
