Re: sshd: when a daemon forks

Alex Smith wrote: Mildred wrote: Sorry, even if I read the ssh manual page and help output i didn't see the -D flag that keeps sshd in the foreground. But the question is still here, it is possible that some daemons do not provide this kind of feature, then how do you use them with

Re: start misbehaving deamons as another user than root

Philippe De Swert wrote: Hi all, On Thu, 2007-07-12 at 13:05 +0100, Scott James Remnant wrote: On Thu, 2007-07-12 at 13:18 +0200, Philippe De Swert wrote: I wondered if there was a way to get upstart to start daemons with another user than root. This because some daemons don't

Re: [ANNOUNCE] upstart 0.5.0 released

Scott James Remnant wrote: I know you've all been waiting a while, but finally 0.5 is considered stable enough for a release. This supersedes 0.3 as the supported series, while trunk will now begin work on 0.10 Do you know when a 0.5 package (32-bit and 64-bit compiled) will be available

Re: Upstart Licence part 2

Scott James Remnant wrote: Thanks to everybody who commented on the change of Upstart Licence, especially those who responded in private to detail their concerns with version 3 of the GNU General Public Licence. I appreciate the problems highlighted, and that many of you working in the

Override job status

I've been trying to tweak an upstart job script for ASSP - which is a perl script that has an option for forking. Standard operation had no problems - but it was during the fork testing I ran into an issue. I used expect fork along with respawn - and I'm not certain what I did, but I wound

Re: respawn delay

See man 5 init - review the respawn limit count interval option. -- Daniel On 8/12/2010 1:49 AM, Zoran Bosnjak wrote: Hello all, I just want to check if there is any way to insert a delay (a few seconds), between respawn attempts. In case of some strange service crash (for example some

Re: Using upstart on CLFS

On 8/12/2010 5:58 PM, Grail Dane wrote: Ok ... so I worked out that some of the applications in my scripts were not the same as those from Sourcemage and hence did not take the same options (this is partially fixed now) Assuming someone actually is reading any of this (as have had no replies)

Re: 1024 Connection Limit

On 8/12/2010 4:25 PM, Alex Davies wrote: Hi, I apologise if this is not the correct mailing list to ask this question. As a inexperienced user of upstart, I have several times hit what appears to be a limit of 1024 connections for jobs started by upstart. For example, the following

Second instance

I'm trying to start two processes via one job - not having a lot of success. The documentation indicates this should be possible - I assume I'm doing something stupid. My config: # assp - Anti-Spam Service Proxy # # assp description ASSP start on runlevel [2345] stop on runlevel

Disconnected jobs

Is there a method to: 1. Tell Upstart that a given process is an instance and should be supervised? Example: I have a number of VirtualBox headless servers that I start using simple Upstart scripts. I terminate the server process - and I've told Upstart not to restart it in the script