Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sometimes when I boot my PC, privoxy starts up, and sometimes it doesn't. Not a big problem. It is easy to start manually. But it's damn annoying. I am using Ubuntu 9.10. It didn't happen in earlier versions of Ubuntu. Anyone know how to make it start every time I boot?
If you can start it by hand without error, it's difficult to say why it does not start on boot without any additional info.
Did you try to activate all logging levels and did you activate the logfile?
Did you look into the error file?
Both files usually reside in /var/log/privoxy/ and the configuration is in /etc/privoxy/config
If you get an error message from there, come back here and post it.
I suddenly noticed that this problem does not only affect privoxy. My mediaserver (MediaTomb) had the same problem today.
It may be that networking sometimes takes so long to set up that it is not finished by the time the Privoxy and MediaTomb startup scripts run. You could try deleting the /etc/rc3.d/S20privoxy symlink and recreating it as S98privoxy -- not much later in elaspsed time during boot but maybe enough given that you do not always get the problem. If it improves the situation but does not completely fix it please ask again.
Caveat: the technique would mean that Privoxy itself is not set up until later in the boot process; that may have undesirable effects (but probably only if you log on to the desktop and browse to a dodgy web page at the speed of lightning).
Hm. Didn't fix it, but it seems to start more often though. Not sure if I did it right either. I just renamed /etc/rc3.d/S20privoxy to S98privoxy.
If the name of the link starts with SXX (S98 in this case) and points to the right script in init.d (which should both be the case if you just renamed it), you did it right.
Perhaps you should rename the links (where present) in all the rcX.d-directories in such a case, to have consistent behaviour across all run levels and in case run level 3 (rc3.d) should not be your default run level (it normally is on most standard distributions, though).
Did you try looking into the various system log files in /var/log/ after you encountered this problem on startup?
Perhaps you are able get information on some networking problem earlier in the boot sequence.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.