Closed kartikm closed 6 years ago
@TinoDidriksen Can you look into this?
I don't Python much, and I am not knowledgeable of this codebase. So if it's critical: @sushain97 @unhammer
A quick glance at the code looks correct (https://github.com/apertium/apertium-apy/blob/master/apertium_apy/apy.py#L248).
Seems like @jonorthwash added the lines: https://github.com/apertium/apertium-apy/commit/cf48209eda132ccdf90db2b7cbf8c8501e6fb670
I've never used --daemon
, and still don't see the point, why not just >apy.log 2>apy.err
?
(Also, why is an option named --daemon doing --redirect-output-to-log-path?)
Redirection is not always an option, so passing filenames helps. But I guess this solves the mystery: --log-path
is only applicable when --daemon
Edit: Oh, but you have --daemon
on and still doesn't work? Hell if I know then.
I have no idea anymore what my thinking was when I added the logic for logging. Please feel free to adjust as makes sense.
Any updates on this bug?
Do we need a v0.11.4 release for this?
Release with tarball would be nice!
Release is out to PyPi. My apologies for the delay.
New version of apertium-apy (>= 0.11.3) doesn't honor logging -P / --log-path= anymore
Test case:
mkdir /tmp/apy-log /usr/bin/apertium-apy -j1 -m300 --daemon --log-path /tmp/apy-log -p 50000 /usr/share/apertium/modes
This prevents logging for service to files. Only stdout is shown.