This appears to be fixed by adding the close_after_write true
option. I'm not sure that I understand *why* not using this option causes it to exit or just not write anything, but that seems to be what happens. I'm not sure if this is a Catalyst of Log::Dispatch issue. On 29/02/12 13:08 Robert Rothenberg wrote: > On my development machine, Log::Dispatch works fine with the following > option in myapp.conf: > > <Log::Dispatch> > class File::Locked > filename /var/opt/myapp/log/catalyst.log > min_level info > mode append > format "[%d] [%p] %m <at %F line %L>%n" > </Log::Dispatch> > > but when it runs with the --background option, it exits rather than logging > anything. As far as I can tell, the user has the correct permissions. > > On a testing server, where it runs in the background, it does not output > anything, but does not exit. The user it runs as has permissions to write to > the directory, and even creates the log file if it doesn't exist, but > nothing is actually written to it. > > Any ideas why this is happening? _______________________________________________ List: Catalyst@lists.scsys.co.uk Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.scsys.co.uk/ Dev site: http://dev.catalyst.perl.org/
