in Linux console application about quicklogger HOT 3 CLOSED

Hi SamJokO,
I think problem was with file provider. When you fork a process, you clone all but with different PID, but new process uses same file. In Windows, if you want to log different process you need to set GlobalLogFileProvider.AutoFileNameByProcess := True before Enable FileLogger provider
and your filename will be filename + _ + processId + .log. Not irmplemented in Linux, but please confirm if this is your problem a i will try to implement it.

from quicklogger.

Hi, exilon.
Thank u for your suggestion.
But, that's not the point. (I think...)
i try fork after GlobalFileLogger. not sharing file pointer. (i did fork after halt(1))
i test some log into TLogFileProvider.WriteLog.
used tstringlist and finally savetofile.
but, it's not working.
i think thread is suspended or not execute.
it's so weired.

from quicklogger.

Hi, exilon.

Logger created in Quick.Logger "initialization" section.
it means program launching after first allocation Logger instance.
but. linux fork is only one thread(main-thread) copy.
fork is not safety in multithread.
i try logger.free after fork --> first exception (because. memory copy success, but thread not working. it means possible memory leak in library)
btw, after exception create new instance.
Logger := TLogger.Create; <-- like this.
it's successfully working well.
i think fork and initialization's combination problem.

Thank you.

p.s : sorry for my poor english.

from quicklogger.