On 5/17/05, Dennis Peterson <[EMAIL PROTECTED]> wrote: > You said it shouldn't log to / and there's no reason it shouldn't if that > is where one wishes it to log. There's lots of reasons why that would be a > bad idea, but it's an admin decision, not an application issue.
It sounds like clam is creating the log files *before* the root startup process hands over control to the user defined in the config files. In 0.84 and prior, it sounds like there was something that handed off an open filehandle to the defined user, but that filehandle was opened by root... I'm not sure if that's possible or not, so please correct me if I'm wrong.. :) It seems that the current behaviour is more correct, but still not completely correct.. I would expect that when clamav starts, all control should be handed to the defined user immediately and then files should be created, opened, etc... It's possible that the current problems are mostly due to pre-existing logfiles that are already owned by root, as opposed to new installations. To be honest, I haven't tried a new install to see if the files are still created with "improper" permissions. > dp ... did I mention I'm anal? Isn't anal a required attribute for those who are security conscious? ;) -- Jason 'XenoPhage' Frisvold [EMAIL PROTECTED] _______________________________________________ http://lurker.clamav.net/list/clamav-users.html
