Re: init.d and tinyproxy
- From: "Mumia W.." <paduille.4061.mumia.w+nospam@xxxxxxxxxxxxx>
- Date: Thu, 31 May 2007 01:29:07 -0500
On 05/31/2007 12:27 AM, William Xu wrote:
"Mumia W.." <paduille.4061.mumia.w+nospam@xxxxxxxxxxxxx> writes:
The manual page for invoke-rc.d suggests that it's mainly for the use of
Debian package maintainers. You are probably a normal user, so
"/etc/init.d/tinyproxy start" is the correct method for you.
It just says maintainers should use that, but doesn't say normal users
shouldn't use it. Anyway, can i call this a bug? probably in tinyproxy.
It's probably not a bug. Invoke-rc.d checks the current runlevel before deciding to start a process; if the process is not configured to run in the current runlevel, invoke-rc.d probably won't start it.
Check the outputs of these commands (as a normal user):
/sbin/runlevel
/usr/sbin/update-rc.d -n -f tinyproxy remove
(The -n prevents anything from happening.)
The first command shows you the current runlevel (the second number), and the second command shows you what runlevels start and stop tinyproxy. Probably, you're in a runlevel where tinyproxy is configured to stop.
Refer to these:
http://www.debian.org/doc/manuals/reference/ch-system.en.html#s-runlevels
http://www.debian.org/doc/manuals/reference/ch-tips.en.html#s-no-x-start
man update-rc.d
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- Follow-Ups:
- Re: init.d and tinyproxy
- From: William Xu
- Re: init.d and tinyproxy
- References:
- init.d and tinyproxy
- From: William Xu
- Re: init.d and tinyproxy
- From: Mumia W..
- Re: init.d and tinyproxy
- From: William Xu
- init.d and tinyproxy
- Prev by Date: Distinguishing Etch(Stable) packages from Sarge(Stable) packages.
- Next by Date: how to config debian CD image
- Previous by thread: Re: init.d and tinyproxy
- Next by thread: Re: init.d and tinyproxy
- Index(es):
Relevant Pages
|
|
