Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-10 Thread Andrew McGlashan
All good now: # cat /etc/init.d/archive-system-mail #! /bin/sh ### BEGIN INIT INFO # Provides: mailarchive # Required-Start:$local_fs $remote_fs $syslog # Required-Stop: $local_fs $remote_fs $syslog # X-Start-Before:exim4 dovecot # X-Stop-After: exim4 dovecot #

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-10 Thread Mart van de Wege
Christian Seiler writes: > > No, in the contrary. When I first saw Gentoo's system in the mid 2000s, > which was based exclusively on dependencies (but still used scripts on > top of sysvinit), I thought: wow, this is SO much better than all the > other distros at that time.

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-10 Thread Christian Seiler
On 06/10/2016 07:54 AM, Andrew McGlashan wrote: > I want the script to run once only at bootup, before exim4 and also > before dovecot, it isn't a service; but I've moulded the script to > appear like one in order to achieve the desired result. And there is no > need to run it ever again after

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
Hi, I'm not sure my end solution is the best. TLDR; -- I've now got the script working as desired, but I have more to say below, including a thank you for Christian in particular. And I do have other queries. I want the script to run once only at bootup, before exim4 and also before dovecot,

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Christian Seiler
On 06/09/2016 10:10 PM, Andrew McGlashan wrote: > What I have now is that with some extra "smarts" that stops the original > concept from working as intended. The smarts is meant to allow for > faster startup and to tie in dependancies; to me, it is trying to be too > smart and that is where the

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Christian Seiler
On 06/09/2016 07:46 PM, Andrew McGlashan wrote: > The order of the scripts alone allowed for everything to be very, very > simple and no script relied upon any other; they were self dependent. > If you wanted something to be available before your script, you made > sure your numeric number after

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Mark Neyhart
On 06/09/2016 12:17 PM, Dan Purgert wrote: > Andrew McGlashan wrote: >> On 10/06/2016 5:06 AM, Dan Purgert wrote: >>> Andrew McGlashan wrote: [snip] Now, I want the archiving script to run on system startup, I don't want dovecot or exim4 to be running when the script starts, it

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Nicholas Geovanis
The Jessie Debian Handbook states: "The two-figures number that follows had historically been used to define the order in which services had to be started, but nowadays the default boot system uses insserv , which schedules everything automatically based on the scripts’ dependencies." on pg 188.

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Dan Purgert
Andrew McGlashan wrote: >[snip] > The script does have #! /bin/sh at the top and /bin/sh does point to > /bin/dash as follows: > > # ls -l /bin/sh > lrwxrwxrwx 1 root root 4 Feb 21 17:40 /bin/sh -> dash Try running it as 'sh ' or 'dash ' -- you're probably doing "bashisms" in there somewhere

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
gh, I suppose that you could've just forgotten to > remove that bit. I'm sure it can be removed, I started off with the /etc/init.d/skeleton and tried to work from there when the script didn't run at startup without the extras at the top. >> [snip] >> Weird artifcat of something (pe

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Dan Purgert
Andrew McGlashan wrote: > On 10/06/2016 5:06 AM, Dan Purgert wrote: >> Andrew McGlashan wrote: >>> [snip] >>> Now, I want the archiving script to run on system startup, I don't >>> want dovecot or exim4 to be running when the script starts, it >>> simply needs to have the /backup and /var file

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
On 10/06/2016 6:02 AM, Brian wrote: > Your premable was enough: > > In the Solaris world and most SYSV systems like it, there was a very > simple startup system; it was not systemd, nor is it the "modern day > sysvinit. It was much simpler and worked very, very well and extremely >

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Brian
On Fri 10 Jun 2016 at 05:29:59 +1000, Andrew McGlashan wrote: > > > On 10/06/2016 5:24 AM, Brian wrote: > > Otherwise, hobby-horses probably require a different venue. If you do > > not have a problem please try to find somewhere which does not require > > Debian support). > > As per the

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
On 10/06/2016 5:24 AM, Brian wrote: > Otherwise, hobby-horses probably require a different venue. If you do > not have a problem please try to find somewhere which does not require > Debian support). As per the subject, required script will NOT run and in my message: My script is meant to

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
ing system boot (as part of a planed reboot) and I cannot work >> out why. > > What error messages (if any) are you getting? None, no log is created. The machine runs within a Xen KVM. I can't see any evidence the script is run during startup. >> Now, I want the archiving scri

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Brian
On Fri 10 Jun 2016 at 03:46:18 +1000, Andrew McGlashan wrote: > In the Solaris world and most SYSV systems like it, there was a very > simple startup system; it was not systemd, nor is it the "modern day" > sysvinit. It was much simpler and worked very, very well and extremely > reliably. How

Re: Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Dan Purgert
Andrew McGlashan wrote: > Hi, > > In the Solaris world and most SYSV systems like it, there was a very > simple startup system; it was not systemd, nor is it the "modern day" > sysvinit. It was much simpler and worked very, very well and extremely > reliably. How can we get that back on modern

Linux startup, Wheezy -- a required script won't run on startup, but can run manually without any trouble

2016-06-09 Thread Andrew McGlashan
Hi, In the Solaris world and most SYSV systems like it, there was a very simple startup system; it was not systemd, nor is it the "modern day" sysvinit. It was much simpler and worked very, very well and extremely reliably. How can we get that back on modern Debian? I mean simple, just like

RE: script to run on startup

2005-08-03 Thread Florian Dorpmueller
1. Make a file called /etc/init.d/local with a text editor. This file is a script so it should always start with the following line: #! /bin/sh 2. Add the following command to the file: mysql -u root --password=passwd syslog /tmp/mysql.pipe 3. Make this file executable with: chmod +x

Re: script to run on startup

2005-08-03 Thread javier rojas
hey, that's definetly a better way to do it... thank you

script to run on startup

2005-08-02 Thread javier rojas
hello, i need to run a script on startup, in mandrake i should add it to /etc/locale, but i just installed debian 3.1 and i'm not sure where to put it, this is the script: mysql -u root --password=passwd syslog /tmp/mysql.pipe or even better, it should run each time syslog-ng starts, (assumin

Re: script to run on startup

2005-08-02 Thread James Burke
On Tue, 2 Aug 2005 11:05:30 -0400 javier rojas [EMAIL PROTECTED] wrote: hello, i need to run a script on startup, in mandrake i should add it to /etc/locale, but i just installed debian 3.1 and i'm not sure where to put it, this is the script: mysql -u root --password=passwd syslog

Re: script to run on startup

2005-08-02 Thread javier rojas
I created a file in /etc/rc2.d called S99local and put the command in there.Its probably the wrong way todo it but it works.jejeje, ...Its probably the wrong way todo it but it works. that's what i like 'bout linux... thank you-- Ciao,Javierlinux user #393724

Re: script to run on startup

2005-08-02 Thread Gene Heskett
On Tuesday 02 August 2005 11:12, James Burke wrote: On Tue, 2 Aug 2005 11:05:30 -0400 javier rojas [EMAIL PROTECTED] wrote: hello, i need to run a script on startup, in mandrake i should add it to /etc/locale, but i just installed debian 3.1 and i'm not sure where to put

Re: script to run on startup

2005-08-02 Thread Glenn English
On Tue, 2005-08-02 at 11:21 -0400, Gene Heskett wrote: i need to run a script on startup, in mandrake i should add it to /etc/locale, but i just installed debian 3.1 and i'm not sure I created a file in /etc/rc2.d called S99local and put the command in there. Its probably the wrong way

Re: script to run on startup

2005-08-02 Thread Joe Smith
Yeah, I created /etc/init.d/local and put S99 slinks to it in rc2, 3, 4, and 5.d, copying some of the other startup scripts. Doesn't strike me as particularly elegant, and it's (probably) going to get wiped by Debian sometime in the future. But for the time being I have a /dev/tape without