I'm running a script when i shutdown my pc. I'm running a ubuntu 14.04 and I have my script "save_log.sh" in "/etc/init.d/". This script has execution permission (sudo chmod +x /etc/init.d/save_log.sh). I have also created a link in "/etc/rc0.d/" with target "/etc/init.d/save_log".
I have tested that this script is running when shutdown my laptop (a piece but is running).
I'm trying save a logs file and upload to S3 (Amazon Web Services). For this task I'm making a "tar.gz" with all logs files with a specific file name. This file name depends of IP of server (or laptop).
When I run this script in my console is work successfully and the file is created with a file name that contents IP (of my laptop) and this file is uploaded to S3. When I shutdown my laptop the file is created but the name has not IP and the file is not uploaded.
I have created a log for this script and I added output for ifconfig command:
ifconfig: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:6432 errors:0 dropped:0 overruns:0 frame:0 TX packets:6432 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1159509 (1.1 MB) TX bytes:1159509 (1.1 MB)
This output have not an IP of network. In runlevel0, is network disabled? Is possible activation? Any idea to solve the problem?
UPDATE
Content in my /etc/rc0.d/ (ubuntu 14.04):
eltortuganegra@eltortuganegra:~$ ll /etc/rc0.d/
total 20
drwxr-xr-x 2 root root 4096 jun 11 16:31 ./
drwxr-xr-x 152 root root 12288 jun 12 09:07 ../
lrwxrwxrwx 1 root root 24 jun 11 13:29 K01save_logs -> /etc/init.d/save_logs.sh*
lrwxrwxrwx 1 root root 17 jun 9 10:27 K09apache2 -> ../init.d/apache2*
lrwxrwxrwx 1 root root 29 jun 9 10:14 K10unattended-upgrades -> ../init.d/unattended-upgrades*
lrwxrwxrwx 1 root root 20 jun 9 10:14 K20kerneloops -> ../init.d/kerneloops*
lrwxrwxrwx 1 root root 19 jun 9 11:35 K20memcached -> ../init.d/memcached*
lrwxrwxrwx 1 root root 15 jun 9 10:14 K20rsync -> ../init.d/rsync*
lrwxrwxrwx 1 root root 27 jun 9 10:14 K20speech-dispatcher -> ../init.d/speech-dispatcher*
lrwxrwxrwx 1 root root 22 jun 11 11:07 K21spamassassin -> ../init.d/spamassassin*
-rw-r--r-- 1 root root 353 mar 13 02:33 README
lrwxrwxrwx 1 root root 18 jun 9 10:14 S20sendsigs -> ../init.d/sendsigs*
lrwxrwxrwx 1 root root 17 jun 9 10:14 S30urandom -> ../init.d/urandom*
lrwxrwxrwx 1 root root 22 jun 9 10:14 S31umountnfs.sh -> ../init.d/umountnfs.sh*
lrwxrwxrwx 1 root root 18 jun 9 10:14 S40umountfs -> ../init.d/umountfs*
lrwxrwxrwx 1 root root 20 jun 9 10:14 S60umountroot -> ../init.d/umountroot*
lrwxrwxrwx 1 root root 14 jun 9 10:14 S90halt -> ../init.d/halt*
I revised in a Debian distribution the rc0.d directory and I found:
K06networking -> ../init.d/networking
I suppose that is the link that is executed for stop network but in my Ubuntu this link does not exist. I suppose that if I rename my link with a number under K07 then network would be enable and my script "save_logs.sh" would run normally.
How can I know when network is disabled or how can I execute my script before network is disabled?
Yes network will be disabled. You will want to run your script prior to the network being disabled. It will usually disable itself in the same runlevel you are booting to.
As an example on a SUSE linux system, check this out:
(your directories may vary depending on which linux you are using)
You'll notice the start and stop of the network script is in the same run level. In my case, if I boot up to runlevel 3, the start and stop takes place in run level 3. Start is S05 and stop is K17.
Things are run in numerical order, so if I were to run your logging script on my runlevel 3 machine I would want to put it at K16.
Or to be safe I'd create the logging script for all three run levels
Does this help?