[06:11] <SpamapS> jY: sudo is not advisable for this as it may end up starting a pam session.
[06:12] <SpamapS> jY: also the double fork is only for when they fork *and exit*
[06:13] <SpamapS> jY: what you probably want is no expect line at all, since the rvm bash will stay running until killed
[10:06] <tzafrir_laptop> stupid question: why does dh_installinit need to avoid installing the init.d script if it installs the upstart init file?
[10:06] <tzafrir_laptop> Can't upstart just ignore the init.d script in this case?
[10:55] <soren> tzafrir_laptop: That won't stop people from running it.
[11:00] <tzafrir_laptop> I suppose making start-stop-daemon detect this and warn or whatever has been suggested before, right?
[12:27] <macnix> is there a way to create & control upstart jobs as a regular system user?
[12:28] <macnix> I keep getting the dbus error message whenever I use start/stop as anyone else but root
[12:31] <macnix> ideally, each app has will have its own regular user, it will create upstart jobs as that user and it will be able to start/stop them, no admin privileges required
[12:38] <tzafrir_laptop> macnix, (nobody else answers, so I'll pick this up) I recall this has been a wishlist item for quite some time,
[12:39] <tzafrir_laptop> but I'm not familiar with upstart
[13:23] <macnix> tzafrir_laptop thanks, got an answer in #ubuntu-server
[21:21] <rlaager> I have this recurring problem where trying to stop services results in "Unknown instance". It happened across several releases of Ubuntu, with multiple different services (SSH, upstart jobs for daemons I've written myself).
[21:21] <rlaager> With SSH, it's virtually guaranteed to happen every time I want to stop it (since I do so infrequently), but I can't reproduce this on demand. In other words, I can start...stop...start...stop services right in a row to my heart's content and it's fine. What should I be doing to debug this?