I think you need to use an absolute path to the log file. I recall other folks having issues before. Try that and let us know. --adam http://gordonizer.com On Fri, Aug 24, 2012 at 5:15 AM, Oliver Zemann <oliver.zemann@gmail.com>wrote:
Yes i did but the problem is that this application is a install4j application which does not handle stdio/stderr/stdout - so this is dropped. I do not see anything from the stdout :/
2012/8/24 ceki <ceki@qos.ch>:
Have you tried enabling logback's internal status messages?
<configuration debug="true" scan=...> ... </configuration>
On 24.08.2012 12:52, Oliver Zemann wrote:
Hi, i have the absolut identical file for Windows which works as expected (logging), but not for linux:
http://rifers.org/paste/show/1801
There is just no logging - i started everything as root. Even when i use the FileAppender with its file name property set to "somelog.log" or "/root/somelog.log" it just saves nothing and i have no idea why.
I used updatedb && locate to find a file called like this but there was nothing. Also lsof with a grep find nothing opened. So it is really not logging.
Regards, Oli
-- Ceki http://tinyurl.com/proLogback _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user