Re: init.d script works well, but won't start at boot

2013-01-26 Thread berenger . morel
thanks for your help, I solved the problem Nice. Just a small reply to notice you that something with your mail client is wrong: I've received most of your messages replies 4 times. Not a real problem for me anyway, but for longer discussions it could be very boring. Have a good day. -- T

Re: init.d script works well, but won't start at boot

2013-01-26 Thread Tom H
On Fri, Jan 25, 2013 at 5:16 PM, Benin Technologies wrote: > > Running Debian 6.0.4 > > Does anybody have an idea why a program wouldn't start at boot, while it's > init.d script works fine ? > > I experience the problem with OpenLDAP 2.4.33, when compiled with back-sql : > > /etc/init.d/slapd sta

Re: init.d script works well, but won't start at boot

2013-01-26 Thread Benin Technologies
hi, thanks for your help, I solved the problem What I did : When I start slapd through "/etc/init.d/slapd start", it looks for the library "/usr/local/lib/libodbc.so.2" That path is in my LD_LIBRARY_PATH environment variable, so the script starts fine. But apparently, when I start slapd thr

Re: init.d script works well, but won't start at boot

2013-01-25 Thread chris
Did you run update-rc.d to update the symlinks in each run level On Jan 25, 2013 8:11 PM, "Benin Technologies" wrote: > hi, > > thanks for your reply > > That's what I thought too, but I don't think it has something to do with > dependencies. Below some commands I run once Debian is up and runnin

Re: init.d script works well, but won't start at boot

2013-01-25 Thread Benin Technologies
yes I did #update-rc.d slapd defaults Basically, the problem seems to be that service slapd startDOESN'T WORK, while /etc/init.d/slapd start WORKS FINE I know exactly WHERE the problem comes from, but I have no idea how to fix it The problem comes from my configuration options

Re: init.d script works well, but won't start at boot

2013-01-25 Thread Benin Technologies
yes I did #update-rc.d slapd defaults Basically, the problem seems to be that service slapd startDOESN'T WORK, while /etc/init.d/slapd start WORKS FINE I know exactly WHERE the problem comes from, but I have no idea how to fix it The problem comes from my configuration options

Re: init.d script works well, but won't start at boot

2013-01-25 Thread Benin Technologies
hi, thanks for your reply That's what I thought too, but I don't think it has something to do with dependencies. Below some commands I run once Debian is up and running, and once I'm already logged in : # /etc/init.d/slapd start Starting OpenLDAP: slapd (just to check t

Re: init.d script works well, but won't start at boot

2013-01-25 Thread Benin Technologies
hi, thanks for your reply That's what I thought too, but it's definitely not that. Below some commands I run once Debian is up and running, and once I'm already logged in : # /etc/init.d/slapd start Starting OpenLDAP: slapd (just to check that my init.d/slapd script wo

Re: init.d script works well, but won't start at boot

2013-01-25 Thread berenger . morel
Le 25.01.2013 23:16, Benin Technologies a écrit : Hi, Running Debian 6.0.4 Does anybody have an idea why a program wouldn't start at boot, while it's init.d script works fine ? I experience the problem with OpenLDAP 2.4.33, when compiled with back-sql : /etc/init.d/slapd start

Re: init.d boot scripts management

2010-02-12 Thread Chris Jones
> > Adam Hardy wrote: > > > I just searched all over the web and didn't find out what programs are > > > available > > > to manage the lenny init.d scripts. $ apt-cache search runlevel CJ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Re: init.d boot scripts management

2010-02-12 Thread green
Celejar wrote at 2010-02-10 14:49 -0600: > On Wed, 10 Feb 2010 13:00:58 + > Adam Hardy wrote: > > I just searched all over the web and didn't find out what programs are > > available > > to manage the lenny init.d scripts. > > I use sysv-rc-conf. +1 signature.asc Description: Digital sig

Re: init.d boot scripts management

2010-02-10 Thread Celejar
On Wed, 10 Feb 2010 13:00:58 + Adam Hardy wrote: > I just searched all over the web and didn't find out what programs are > available > to manage the lenny init.d scripts. I use sysv-rc-conf. Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourcef

Re: init.d boot scripts management

2010-02-10 Thread Adam Hardy
Tom H on 10/02/10 14:03, wrote: I just searched all over the web and didn't find out what programs are available to manage the lenny init.d scripts. I used to use sysvconfig but that's gone presumably as part of a transition to the new boot management framework. Still exists in Lenny http://

Re: init.d boot scripts management

2010-02-10 Thread Tom H
> I just searched all over the web and didn't find out what programs are > available to manage the lenny init.d scripts. > I used to use sysvconfig but that's gone presumably as part of a transition > to the new boot management framework. Still exists in Lenny http://packages.debian.org/lenny/sys

Re: init.d startup script does not exit

2008-09-14 Thread Clifford W. Hansen
On Sunday 14 September 2008 09:12:35 rex wrote: > Thank you! It worked! > > So, what does that & mean? > > - Rex > > Clifford W. Hansen wrote: > > On Sunday 14 September 2008 08:35:13 rex wrote: > >> Hello, > >> > >> I have a script that launches a program. If I launch this program > >> manually,

Re: init.d startup script does not exit

2008-09-14 Thread Tzafrir Cohen
On Sun, Sep 14, 2008 at 04:05:41AM -0300, Gabriel Parrondo wrote: > Also, this thread deserves a loud WTF. I mean, the OP seems to know the > basics about unix administration (he was able to write a shell script, > at least) but fails at something as basic as running an app in > background. There

Re: init.d startup script does not exit

2008-09-14 Thread rex
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thank you! It worked! So, what does that & mean? - - Rex Clifford W. Hansen wrote: > On Sunday 14 September 2008 08:35:13 rex wrote: >> Hello, >> >> I have a script that launches a program. If I launch this program >> manually, it keeps on running

Re: init.d startup script does not exit

2008-09-14 Thread Gabriel Parrondo
El dom, 14-09-2008 a las 08:46 +0200, Clifford W. Hansen escribió: > On Sunday 14 September 2008 08:35:13 rex wrote: > > Hello, > > > > I have a script that launches a program. If I launch this program > > manually, it keeps on running in the shell. It is a webserver, so I > > need it running all

Re: init.d startup script does not exit

2008-09-13 Thread Clifford W. Hansen
On Sunday 14 September 2008 08:35:13 rex wrote: > Hello, > > I have a script that launches a program. If I launch this program > manually, it keeps on running in the shell. It is a webserver, so I > need it running all the time. However, if I exit the shell, it kills > the webserver. > > I tried

Re: init.d and tinyproxy

2007-05-31 Thread William Xu
"Mumia W.." <[EMAIL PROTECTED]> writes: It's probably not a bug. Invoke-rc.d checks the current runlevel before deciding to start a process; if the process is not configured to run in the current runlevel, invoke-rc.d probably won't start it. Ah, i see. tinyproxy is configured not to run

Re: init.d and tinyproxy

2007-05-30 Thread Mumia W..
On 05/31/2007 12:27 AM, William Xu wrote: "Mumia W.." <[EMAIL PROTECTED]> writes: The manual page for invoke-rc.d suggests that it's mainly for the use of Debian package maintainers. You are probably a normal user, so "/etc/init.d/tinyproxy start" is the correct method for you. It just

Re: init.d and tinyproxy

2007-05-30 Thread William Xu
"Mumia W.." <[EMAIL PROTECTED]> writes: The manual page for invoke-rc.d suggests that it's mainly for the use of Debian package maintainers. You are probably a normal user, so "/etc/init.d/tinyproxy start" is the correct method for you. It just says maintainers should use that, but doesn

Re: init.d and tinyproxy

2007-05-30 Thread Mumia W..
On 05/30/2007 01:24 AM, William Xu wrote: Hi folks, tinyproxy is a tiny proxy server. The problem is that , | # invoke-rc.d tinyproxy start ` doesn't start tinyproxy. It simply does nothing. While, by , | # /etc/init.d/tinyproxy start ` tinyproxy starts successfully. i

Re: init.d: writing custom init-scripts

2001-12-21 Thread Miquel van Smoorenburg
In article <[EMAIL PROTECTED]>, Brian May <[EMAIL PROTECTED]> wrote: >> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes: > >Colin> In Debian, runlevels 2-5 are identical by default, and >Colin> configuring any differences is left up to the system >Colin> administrator. > >What d

Re: init.d: writing custom init-scripts

2001-12-20 Thread Marc Britten
first off i applogize for sending this by to Sean Perry personally, still learning this new fangled evolution. On Thu, 2001-12-20 at 22:24, Sean 'Shaleh' Perry wrote: > > > it should be :-) Well, it is an x-less station and but to go shure i > > also put the symlinks to runlevels 4,5 and 6 too. >

Re: init.d: writing custom init-scripts

2001-12-20 Thread Sean 'Shaleh' Perry
On 20-Dec-2001 Timo --Blazko-- Boewing wrote: > On Thu, 2001-12-20 at 23:03, Greg Wiley wrote: >> You've probably checked, but is your default runlevel, indeed, 3? > > Hello Greg, > > it should be :-) Well, it is an x-less station and but to go shure i > also put the symlinks to runlevels 4,5 an

Re: init.d: writing custom init-scripts

2001-12-20 Thread Brian May
> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes: Colin> In Debian, runlevels 2-5 are identical by default, and Colin> configuring any differences is left up to the system Colin> administrator. What does single user mode mean? I thought if I typed in "telinit s" it should kil

Re: init.d: writing custom init-scripts

2001-12-20 Thread Colin Watson
On Fri, Dec 21, 2001 at 01:05:08AM +0100, Timo --Blazko-- Boewing wrote: > In former years i used SuSE Linux, there have been these runlevels: > > 0:halt > 1:maintenance mode > 2:single user mode > 3:multiusermode, console only > 4:n/a > 5:multiuser w/ X > 6:reboot > >

Re: init.d: writing custom init-scripts

2001-12-20 Thread Timo --Blazko-- Boewing
On Thu, 2001-12-20 at 23:06, Timo --Blazko-- Boewing wrote: Hello, thank you all for your replies! Yes, it was due to runlevel 2!!! I used update-rs.d wich reinstalled the correct symlinks, thanx to MH. In former years i used SuSE Linux, there have been these runlevels: 0: halt 1: mai

Re: init.d: writing custom init-scripts

2001-12-20 Thread Noah Meyerhans
On Thu, Dec 20, 2001 at 11:06:14PM +0100, Timo --Blazko-- Boewing wrote: > > Then, i placed a symlink called S99myscript pointing to the script under > /etc/rc3.d, however, it does not get stalled. The symlink and the script > got the same rights and user/group as all the other ones from sid and m

Re: init.d: writing custom init-scripts

2001-12-20 Thread Greg Wiley
On Thursday, December 20, 2001 2:19 PM, [EMAIL PROTECTED] > it should be :-) Well, it is an x-less station and but to go shure i > also put the symlinks to runlevels 4,5 and 6 too. I just checked a Potato and it defaults to RL 2 . -g

Re: init.d: writing custom init-scripts

2001-12-20 Thread MH
> "Timo" == Timo --Blazko-- Boewing <[EMAIL PROTECTED]> writes: Timo> Hello everyone, i got a simple problem but cannot fint the Timo> cause: i have written a custom bash script (a very simple Timo> one) that should be run on machine startup. I put it under Timo> the common pla

Re: init.d: writing custom init-scripts

2001-12-20 Thread Blake Barnett
Running "runlevel" as root will tell you where you are. I believe 99% of debian boxes are set to 2 by default. On Thu, 2001-12-20 at 15:19, Timo --Blazko-- Boewing wrote: > On Thu, 2001-12-20 at 23:03, Greg Wiley wrote: > > You've probably checked, but is your default runlevel, indeed, 3? > > H

Re: init.d: writing custom init-scripts

2001-12-20 Thread Timo --Blazko-- Boewing
On Thu, 2001-12-20 at 23:03, Greg Wiley wrote: > You've probably checked, but is your default runlevel, indeed, 3? Hello Greg, it should be :-) Well, it is an x-less station and but to go shure i also put the symlinks to runlevels 4,5 and 6 too. Timo

Re: init.d: writing custom init-scripts

2001-12-20 Thread Greg Wiley
On Thursday, December 20, 2001 2:06 PM, [EMAIL PROTECTED] wrote: > Then, i placed a symlink called S99myscript pointing to the script under > /etc/rc3.d, however, it does not get stalled. The symlink and the script > [...] > When running the script manually as user root, it succeedes, but it is >

Re: init.d/junkbuster not loading as $DAEMON

2001-08-27 Thread Sven Gaerner
Hi, maybe you have to fix the permissions of the files because junkbuster is run under the user junkbust on woody (and nobody on potato). Otherwise enable the logfile and try starting junkbuster. This helped me to find out that some files under /etc/junkbuster could not be accessed as programmed

Re: init.d/junkbuster not loading as $DAEMON

2001-08-02 Thread Karsten M. Self
on Thu, Aug 02, 2001 at 11:57:41AM -0400, Steve Taylor ([EMAIL PROTECTED]) wrote: > The /etc/init.d/junkbuster call fails unless it's stripped to little > more than the command-line call. What permissions are needed, what > syntax (/etc/junkbuster/config, others)? > > Not working.. (nor as chuid

Re: init.d shell script can't stop daemon (python script)

2001-05-15 Thread Alexander Steinert
> > I wrote a (python) script that is acting like a daemon (doing something, > > sleeping for 10 seconds, doing ..., sleeping ...) and would like to > > launch and kill it from a shell script in /etc/init.d. > > > > Using start-stop-daemon seemed appropriate, but the problems is that > > no /var/r

Re: init.d shell script can't stop daemon (python script)

2001-05-10 Thread David Wright
Quoting Alexander Steinert ([EMAIL PROTECTED]): > this might be a little OT, Not at all. > I wrote a (python) script that is acting like a daemon (doing something, > sleeping for 10 seconds, doing ..., sleeping ...) and would like to > launch and kill it from a shell script in /etc/init.d. > > U

Re: init.d

2000-07-25 Thread John Pearson
On Tue, Jul 25, 2000 at 04:38:58PM +0900, keke abe wrote > John Pearson wrote: > > > Scripts in the Debian init.d directories are run using > > run-parts. > > I believe run-parts is used to run scripts in rc.boot, not those > in init.d. > Oops, right you are. John P. -- [EMAIL PROTECTED] [

Re: init.d

2000-07-25 Thread Sven Burgener
On Tue, Jul 25, 2000 at 10:03:09AM +0930, John Pearson wrote: > Scripts in the Debian init.d directories are run using > run-parts. Run-parts ignores scripts that don't conform to > certain naming conventions: > > DESCRIPTION >run-parts runs a number of scripts or programs found in a >

Re: init.d

2000-07-25 Thread keke abe
John Pearson wrote: > Scripts in the Debian init.d directories are run using > run-parts. I believe run-parts is used to run scripts in rc.boot, not those in init.d. abe

Re: init.d

2000-07-24 Thread John Pearson
On Mon, Jul 24, 2000 at 12:03:17AM +, R K wrote > I've been having some problems getting startup scripts to work. > Particularly with MySQL (latest binary release). From what I know, you're > supposed to put the script in /etc/init.d and make a sym-link to /etc/rcX.d > right? In any case,

Re: init.d

2000-07-24 Thread Krzys Majewski
Check in /etc/inittab to see if your default runlevel is indeed 3. -chris On Mon, 24 Jul 2000, R K wrote: > I've been having some problems getting startup scripts to work. > Particularly with MySQL (latest binary release). From what I know, you're > supposed to put the script in /etc/init.d

Re: init.d

2000-07-24 Thread Moritz Schulte
On Mon, Jul 24, 2000 at 12:03:17AM +, R K wrote: > I've been having some problems getting startup scripts to work. > Particularly with MySQL (latest binary release). From what I know, you're > supposed to put the script in /etc/init.d and make a sym-link to /etc/rcX.d > right? correct.

Re: init.d

2000-07-24 Thread Thomas Guettler
I read in the debian-policy that you shouldn't change the links yourself. Try "man update-rc.d", too. On Mon, Jul 24, 2000 at 12:03:17AM +, R K wrote: > I've been having some problems getting startup scripts to work. > Particularly with MySQL (latest binary release). From what I know, you'

Re: init.d stuff

2000-07-17 Thread Michael Soulier
On Mon, 17 Jul 2000, Bob Nielsen wrote: > You could create a script in /etc/init.d/local and run 'update-rc.d > local defaults' to create the necessary symlinks. /etc/init.d/skeleton > is a good place to start. This kind of thing is often put into the S runlevel too, /etc/rcS.d.

Re: init.d stuff

2000-07-17 Thread Bob Nielsen
On Mon, Jul 17, 2000 at 09:21:22PM -0500, Ethan Pierce wrote: > Hi, Im hoping to set off oss at boot. when I used mandrake I just edited > /etc/rc.d/rc.local . The structure seems a bit diff in debian. I booting to > runlevel2 so do I make some kind of link in /etc/rc2.d? > > The program to exe

Re: init.d, rc0.d, ... rc6.d

1998-01-13 Thread Miquel van Smoorenburg
In article <[EMAIL PROTECTED]>, Sen Nagata <[EMAIL PROTECTED]> wrote: >is there already some administrative command one can use to easily >enable/disable a service? i know it is possible to write scripts to do >this for various services...but perhaps there is already some existing >method? update

Re: init.d, rc0.d, ... rc6.d

1998-01-13 Thread Sen Nagata
at some point around 12 Jan 1998 07:57:06 -0600 [EMAIL PROTECTED] mentioned: > Sen Nagata writes: > > what kind of advantages does this kind of approach have compared to > > having a single file for each run level (or even one file for all > > runlevels) describing which scripts to run (as well

Re: init.d, rc0.d, ... rc6.d

1998-01-12 Thread Joel Klecker
-BEGIN PGP SIGNED MESSAGE- Regarding "Re: init.d, rc0.d, ... rc6.d" of 9:04 PM -0800 1/11/98, Joey Hess wrote: >Sen Nagata wrote: >> what kind of advantages does this kind of approach have compared to >> having a single file for each run level (or even one

Re: init.d, rc0.d, ... rc6.d

1998-01-12 Thread john
Sen Nagata writes: > what kind of advantages does this kind of approach have compared to > having a single file for each run level (or even one file for all > runlevels) describing which scripts to run (as well as the order to run > them in)? The present system is safer and easier to automate.

Re: init.d, rc0.d, ... rc6.d

1998-01-12 Thread Joey Hess
Sen Nagata wrote: > what kind of advantages does this kind of approach have compared to > having a single file for each run level (or even one file for all > runlevels) describing which scripts to run (as well as the order to run > them in)? There's not much difference, really, though the curren