mikshaw


Group: Members
Posts: 4856
Joined: July 2004 |
 |
Posted: Sep. 19 2005,19:34 |
 |
Ah, yes...I should have added "back up both files". Also, I should mention that bootlocal should have "#!/bin/sh" as its first line, so the new bootlocal would be:
Code Sample | #!/bin/sh /opt/something_else.sh &>/home/dsl/bootlocal.log |
...and it should be executable, too.
So....maybe a more simple explaination would be: 1) make a copy of /opt/bootlocal.sh 2) edit the original bootlocal so the only command is /opt/new_bootlocal.sh &>/home/dsl/bootlocal.log 3) back up both files
This basically just sends all output from your script to a log file. It's a roundabout way, but I figured it would be simpler than redirecting every individual bootlocal command to a file.
-------------- http://www.tldp.org/LDP/intro-linux/html/index.html
|