Other Help Topics :: log-file of bootproces

bookmark

Quote (mikshaw @ Sep. 19 2005,10:36)

One thing you could do, if you are concerned only with what is happening from bootlocal.sh:
Rename bootlocal.sh to something_else.sh
Create a new empty bootlocal.sh
Add the command "something_else.sh &>/home/dsl/bootlocal.log"

Just tried, but the opt folder isn't backed up so goodbye old bootlocal.sh So I am writing new bootlocal now, wil rename it and back it up this time and give it an other shot.

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.

ok the logfile is working and simple commands give a output, but not the command I want to perform.
I'm using screen in my command and I think that is the reason.
Anyway it seems I just made a simple type error somewhere, because it is autoplaying in a screen at the moment.
Waiting for the computer to reboot everytime takes a long time

For the people who a interrested this is the command I was debugging.
screen -S mp3 mp3blaster -a /home/dsl/3voor12.lst
Thanx for the help

Since screen is a whole other system of shells, it's possible that the output is being controlled by screen rather than being sent to stdout/stderr. Just guessing as usual =o)

Just out of curiosity...if it's just a headless jukebox, why use screen?

Next Page...
original here.