Hey Folks,

 

I've been playing with suspend to S3, and one thing I noticed was that my copy of bm-ng kept forgetting to launch when I reboot my server.

 

Upon further examination, the path in the auto-installer that is generated (bwm-ng-0.6-i486-2bj.tgz.auto_install) when you tell it to re-install at reboot (in unMenu Package Manager) is /boot/unmenu as opposed to /boot/packages... A bug, or am I missing something?

 

 

 

 

When you request that a package is re-installed on reboot a file is created named after the package, but with an "auto_install" suffix.

 

In the case of the bandwidth monitor the file will be named bwm-ng-0.6-i486-2bj.tgz.auto_instal

root@Tower:/boot/packages# ls -l /boot/packages/bwm*

-rwxrwxrwx 1 root root 36020 Sep 22 10:02 /boot/packages/bwm-ng-0.6-i486-2bj.tgz

-rwxrwxrwx 1 root root    72 Sep 22 21:12 /boot/packages/bwm-ng-0.6-i486-2bj.tgz.auto_install

-rwxrwxrwx 1 root root    35 Sep 22 10:04 /boot/packages/bwm-ng-0.6-i486-2bj.tgz.manual_install

-rwxrwxrwx 1 root root  965 Sep 22 09:34 /boot/packages/bwm-ng-unmenu-package.conf

 

The contents of the .auto_install package is taken from the PACKAGE_INSTALLATION lines in the bwm-ng-unmenu-package.conf file.

root@Tower:/boot/packages# cat /boot/packages/bwm-ng-0.6-i486-2bj.tgz.auto_install

SCRIPT_DIRECTORY=/boot/unmenu

installpkg bwm-ng-0.6-i486-2bj.tgz

 

The first line sets an environment variable. I don't even think I've ever needed to use it in installation commands.  Consider it as unused.

The second line performs the actual installation.

 

When you request that "Auto-Install on reboot" occurs a line is added to the end of your "go" script that looks like this:

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

If unMENU detected you had a /boot/custom/etc/rc.d directory, instead of a line being appended to the "go" script, a file named S10-install_custom_packages

is created there instead, and a line added to it instead.  That line is exactly the same as would have been appended to the "go" script.

 

I have a /boot/custom/etc/rc.d directory, so on my server, the file was created there

cat /boot/custom/etc/rc.d/S10-install_custom_packages

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

Now if you have a /boot/custom/etc/rc.d folder in place, unMENU assumes you already have in place a line in the "go" script to invoke startup scripts placed there.  In my case, the line in my go script for that is

fromdos < /boot/custom/etc/rc.d/rc.local_startup | sh

 

So... it sounds as if the line in your go script is missing, or you previously edited the "go" script and it did not contain a newline at the end of the last line, and instead of the line added by unMENU being on its own line, it ended up appended to the previous line.

 

What does your "config/go" script look like?  It is what is invoked when you reboot, and it is what will "cd /boot/packages" and run each of the .auto_install files it finds there.

 

As I said, most people will just get that line appended to the ended of their "go" script.

 

Joe L.

 

Hi Joe,

 

Thanks for the indepth answer! I looked at my go script, and I seem to have that line, but it is not the very last line, since I added the 2  lines to help with network resolving. Should the auto install line be last?

 

Thanks!

 

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
# Launch new UnMenu
/boot/unmenu/uu
# Execute s3.sh sleep script
fromdos < /boot/custom/bin/s3.sh | at now + 1 minutecd 
/boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 
echo nameserver 192.168.1.1 >/etc/resolv.conf
echo 192.168.1.149 Tower >>/etc/hosts

Hi Joe,

 

Thanks for the indepth answer! I looked at my go script, and I seem to have that line, but it is not the very last line, since I added the 2  lines to help with network resolving. Should the auto install line be last?

 

Thanks!

 

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
# Launch new UnMenu
/boot/unmenu/uu
# Execute s3.sh sleep script
fromdos < /boot/custom/bin/s3.sh | at now + 1 minutecd 
/boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c 
echo nameserver 192.168.1.1 >/etc/resolv.conf
echo 192.168.1.149 Tower >>/etc/hosts

It is fine where it is.

However, you apparently did not have a newline on the end of the prior line.

 

It should read

fromdos < /boot/custom/bin/s3.sh | at now + 1 minute

 

and the next line should read

cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c

 

From what I could see, the "cd" was tacked onto the end of the word "minute" because there was not a newline at the end of the line.

 

Whenever you add a line to the "go" script it must end with a newline character.  (Just like pressing "enter" executes it if typed on the command line)

 

Fix those two lines and I think you'll see things working.

Doh! So embarrassing! 

 

Thanks Joe! That fixed it! (And, hopefully my problem with sleep not working!!!)

 

You and this community truly Rock!!!

 

Since I have the "cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c" in the /boot/custom/etc/rc.d/S10-install_custom_packages  directory i can remove it from my go script right?

 

thanks

Since I have the "cd /boot/packages && find . -name '*.auto_install' -type f -print | sort | xargs -n1 sh -c" in the /boot/custom/etc/rc.d/S10-install_custom_packages   directory i can remove it from my go script right?

 

thanks

Only if you have a line in your "go" script invoking a script in /boot/custom/etc that in turn executes the packages it finds there.

 

Easy way to find out. comment out the line in the go script (put a "#" character at the beginning of the line) and reboot.