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
On 10/06/2016 6:17 AM, Dan Purgert wrote: >> Perhaps, but why? I'm not asking it to log anything to syslog; just to >> create it's own log file in the /var/log directory. > > Just going off the comments at the top -- states "required-start: > $syslog". Although, I suppose that you could've

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
Hi, Thanks for your reply. On 10/06/2016 5:06 AM, Dan Purgert wrote: > 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

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