Last week, i had been erroneously assuming, the daily reassigned external IP addresses from my provider would kill Tor, as someone suggested in the IRC. So i ran a quick "sudo update-rc.d tor disable".

Only later, when i learned, the IP change doesnt cause too much trouble, i reenabled Tor. Since then, the tor service doesnt come up on computer startup any longer. I tried all kind of things, like:

sudo update-rc.d tor enable sudo update-rc.d tor defaults

i even reinstalled Tor completely, but the service does not start automatically any longer. After finding this to be true, i began to start it manually after each reboot like so:

sudo service tor start # this does in fact cause the service to run as debian-tor user, as it should!

Unfortunately, it is necessary to reboot from time to time, to prevent acceleration in memory fragmentation caused by several programs i use on a daily basis. If not prevented, the latter causes system instabilities and introduces severe risk of data corruption.

So back to the basics: i am just a simple Ubuntu user with a machine, that is connected and running basically 24/7 (except for the daily disconnect, as can be seen from the logs). And i would certainly appreciate any suggestion to check for, why upstart doesnt pick up Tor, as it should. From my own understanding, eveything looks pretty normal, like:

find /etc -name ?20tor | xargs ls -l lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc0.d/K20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc1.d/K20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc2.d/S20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc3.d/S20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc4.d/S20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc5.d/S20tor -> ../init.d/tor lrwxrwxrwx 1 root root 13 Mär 4 04:19 /etc/rc6.d/K20tor -> ../init.d/tor

Sorry for asking such an unadorned question here, i simply ran out of ideas. :-(

NewTorKidOnTheBlock