Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Rainer Weikusat Newsgroups: comp.os.linux.development.apps Subject: Re: How to automagically run an application when entering runlevel S Date: Wed, 07 Dec 2011 15:37:00 +0000 Lines: 19 Message-ID: <87mxb475r7.fsf@sapphire.mobileactivedefense.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: individual.net Th+lyjWjd+aDLawM1ZO02gHgLy2fZNStEYZByZElY4rytGq+g= Cancel-Lock: sha1:QkzeBob/hPWWOfaN2GES56O+xU8= sha1:e9DZ1y5JPggoIX13wYWcjCbAeaE= User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.development.apps:303 Josef Moellers writes: [...] > The application runs in runlevel S and when runlevel S was entered on > the old image, /.profile was run and that contains a call to our > application. > On the new image, this does not happen! > Unfortunately, the guy who built the old image is no more available. > Does anyone have an idea where to tweak to run /.profile when entering > runlevel S? For sysvinit, a corresponding line could be added to /etc/inittab eg a0:1:wait:/.profile in a suitable place (IOW below the entries executing rc scripts, [untested]).