Startup order in ubuntu

[loonsailor]

My system was not starting successfully most of the time after a power down. Symptom was that the sage client would be running, and when I started a client or placeshifter it could see the server and try to connect, but the connection wasn't successful. I needed to restart the server manually (sudo /etc/init.d/sagetv restart).

I fixed it by changing the init script to be done later in the startup:

> sudo update-rc.d -f sagetv remove
> sudo update-rc.d sagetv defaults 98

It works reliably now. I can yank the power cord and plug it back in, and everything comes back up with sage working nicely. To be honest, I'm not sure why. It was at level 20 before, and I don't see anything that starts after that that sage should need (maybe HAL?). But it now works when it usually didn't before.

Anyway, if you're having trouble at boot time, it might be worth a try.

[Peggysis]

Thanks for the info! Would you mind posting what version you are running?


-Judy

[loonsailor]

Originally Posted by Peggysis

Thanks for the info! Would you mind posting what version you are running?


-Judy

Ubuntu 9.04, Sage 6.6, on an AMD X4 905e with 4GB.

[chip33az]

I just rebuilt my SageTV box (HDD died) using Ubuntu 9.04 and I could not get SageTV to start without corrupting the Wiz.bin. I tried what was listed in the first post of this thread and I still couldn't get it to work. It seemed to work if I manually started SageTV after my Gnome desktop was running so...

After installing Ubuntu (with automatic login for my account) and after installing SageTV I changed it so it wouldn't start on boot.

sudo update-rc.d -f sagetv remove

I then modified the VISUDO so that starting SageTV wouldn't require a root password. Chip is the user account on the computer.

sudo visudo
chip ALL= NOPASSWD: /opt/sagetv/server/startsage

Finally, I added a quick command to System | Preferences | Startup Applications.

Name - Start SageTV
Command - sudo /opt/sagetv/server/startsage
Comment - This starts SageTV

So far I have rebooted the computer a few times and haven't had the corrupt Wiz.bin yet. Hopefully it won't