Re: I can start my tracker from command line, but it does not start as a daemon...
"John P. Rouillard" <[email protected]>
| Newsgroups | gmane.comp.bug-tracking.roundup.user |
|---|---|
| Message-ID | <[email protected]> |
Hi Ed: In message <PH7PR12MB56564B0B2AAD987E8FFB6E38843E9@PH7PR12MB5656.namprd12.prod. outlook.com>, Ed Trumbull writes: >Specifying the -l option on the command line appears to have worked, thanks. >I thought that specifying the filename in the [logging] section of >config.ini would suffice, and that specifying -l would be redundant. There are two things logging: 1) the mechanism that makes the tracker available on the network 2) the tracker itself Roundup-server is one way to make the tracker available on the network. Running Roundup as a CGI (with network logging by nginx/apache for example) or wsgi (with logging by nginx/apache and/or gnunicorn or uwsgi) are other supported methods. The tracker (or trackers, as you might have multiple trackers adminstered by different people) logging usually doesn't care about the network part. That logging happens when Roundup is invoked by email, roundup-admin, or a python program. >For now, I have both the filename option in the config.ini and the -l >option on the command line pointing to the same file. Is there an >advantage to having them point to different files? I would suggest using two different files. They log using different mechanisms (roundup-server just writes to the file, the tracker uses Python's logging module). I can't be sure that there isn't some bad interaction there that could jumble the log. Even when using the -L flag (to log using python's logging module with the key roundup.http), I direct the roundup-server to a different file. IIRC the logging from roundup-server can be analyzed by any tool that takes basic or combined log format from a web server. Mixing the tracker and server output makes using these tools trickier. Also I mentioned the man page in my original response. That is probably not on your MANPATH as Python's packaging code has no method to install the man pages and other shared files in normal system locations. Our packing (setup.py) script tries to "do the right thing" to put man pages in the usual man paths (e.g. /usr/share/man, /usr/local/man /usr/local/share/man, ...) but YMMV based on the version of Python you use and how it was packaged. I hope you have more success with Roundup. Have a great rest of your week. -- -- rouilj John Rouillard =========================================================================== My employers don't acknowledge my existence much less my opinions.