#1467 closed defect (Fixed)
Log to file when not daemonized
| Reported by: | Cameron Tacklind | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 2.x |
| Component: | Core | Version: | 1.3.1 |
| Keywords: | log, logfile | Cc: | Cameron Tacklind |
Description
Deluged makes the assumption that when you tell it not to daemonize on startup, you don't want it to output to a log file. While this kinda makes sense if the default logfile is selected, explicitly setting a logfile in the command line arguments should not get overridden by the adjacent forgrounding (--do-not-daemonize) flag. Similarly, when --queit is used, it should not change the debug level that is going to the logfile, only what is sent to stdout.
This was the source of a lot of frustration because no matter what I did, deluged wouldn't create a log file. Turns out my distro's init script is set to daemonize/fork on it's own since it doesn't work if it lets deluged do it. Working on why now...
Change History (2)
comment:1 by , 14 years ago
| Milestone: | Future → 1.4.0 |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
As it is now, ie, current deluge's master from git, if you pass a logfile and tell deluged not to daemonize, it correctly writes the log messages to the logfile and no output is sent to the console, except for deprecation warnings which use sys.stderr I believe, and those should be seen.