monotone - Bugs: bug #16177, Daemonize Monotone
You are not allowed to post comments on this tracker with your current authentication level.
bug #16177: Daemonize Monotone
Submitter: | Chad C. Walstrom <chewie> | ||
Submitted: | Fri 24 Mar 2006 05:10:56 PM UTC | ||
Votes: | 2 | ||
Category: | networking | Severity: | 3 - Normal |
Item Group: | feature request | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | ||
mtn version --full: | monotone 0.24 (base revision: d59847072bb689e952ab21db7f9fababdb80a19f)
|
Jump to the original submission
Wed 23 Aug 2006 12:49:38 AM UTC, comment #6: |
Anonymous |
Tue 22 Aug 2006 10:13:58 PM UTC, comment #5: Judson, I respectfully disagree with some of your comment. Foreground service shouldn't disappear just because background service is requested. Not all platforms can use runit or daemontools. Mac OS X has its own beast called launchd, which like runit, requires the daemon to stay in the foreground. Windows... well... I don't have a whole lot of experience with Windows to comment. However, as a systems administrator, I don't relish the idea of ripping out my existing sysvinit setup just to run monotone as a "reliable server".
|
Chad C. Walstrom <chewie> |
Tue 22 Aug 2006 07:41:12 PM UTC, comment #4: I'd like to amplify the comment re: runit to mention that I wouldn't want to see foreground service go away. Runit and daemontools both work much better with apps that run in the foreground, and I happen to hold with their philosophy that an app should do one thing and do it well - in monotone's case version control, not secure daemon service. |
Judson Lester <nyarly> |
Mon 17 Jul 2006 03:03:28 AM UTC, comment #3: anyone working on this bug/feature request, should also take a look at
|
Erik MT <codehappy> |
Mon 17 Jul 2006 02:33:36 AM UTC, comment #2: an additional feature is requested in bug #15896
|
Erik MT <codehappy> |
Fri 24 Mar 2006 10:38:37 PM UTC, comment #1: Fair enough! I'll just mention, you can use 'runit' to get most of these features, and more -- it's very nice.
|
Nathaniel Smith <njs> |
Fri 24 Mar 2006 05:10:56 PM UTC, original submission:
It would be really nice to be able to properly daemonize "monotone serve", allowing it to fork to the background, accept SIGHUP signals (to reread monotonerc files), and send logs to syslog. Other possibilities: keep running statistics about number of netsync requests processed, active connections, etc.; a "monotone sctrl" command to query and control the daemon.
|
Chad C. Walstrom <chewie> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 2 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2006-07-17 | codehappy | Carbon-Copy | - | Added codehappy | |
2006-07-06 | chewie | Carbon-Copy | - | Added chewie |
Powered by Savane 3.13-f8d8.
Corresponding source code
Chad, I'm afraid you misunderstood me. I wouldn't propose that monotone should not have a background switch, or suggest that it's not a secure service. But the fact that monotone currently runs in the foreground when serving is a feature I very much like, and wouldn't want replaced.