on Sat, Dec 20, 2003 at 10:30:20AM -0800, Doug Hunting ([EMAIL PROTECTED]) wrote:
I was hoping there would be a simple command to restart a daemon. Namely
lprng. I know about killall
killall isn't the recommended way to kill a specific daemon. Instead,
you want:
/etc/init.d/daemon stop
I was hoping there would be a simple command to restart a daemon. Namely
lprng. I know about killall but what signal do you pass it to have it
restart??
-Doug
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, 20 Dec 2003 10:30:20 -0800
Doug Hunting [EMAIL PROTECTED] wrote:
I was hoping there would be a simple command to restart a daemon.
Namely lprng. I know about killall but what signal do you pass it to
have it restart??
-Doug
Try kill -HUP pid of lprng. Better yet, daemons usually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Dec 20, 2003 at 10:30:20AM -0800, Doug Hunting wrote:
I was hoping there would be a simple command to restart a daemon. Namely
lprng. I know about killall but what signal do you pass it to have it
restart??
Type /etc/init.d/daemonname to
I'm sure this is a dumb question.
But i just installed the new wu-ftp (2.6.0-6) from proposed-updates via
apt-get update ; apt-get upgrade
Just ftp'd to localhost, and checked that it was immune or not. Surprise,
the ~{ kills it.. Hmm.. Look up a few lines, and it's still the old date
string.
Greg Stark wrote:
On Fri, Dec 24, 1999 at 10:07:38AM +0100, Christian Kurz wrote:
Well this works for people that use the old init-style with links in
/etc/rc* and won't work for people like me that use file-rc. Please
provide first a solution for both cases. Then we can send out
On Thu, 23 Dec 1999, Wichert Akkerman wrote:
Do we have a generic way to test whether a daemon is enabled for
a given runlevel? That is -- one that works with filerc as well
as sysvinit?
Not yet. At some point debconf will provide that information.
I don't see, how debconf can
On Fri, Dec 24, 1999 at 03:59:46PM -0500, Greg Stark wrote:
Hamish Moffatt [EMAIL PROTECTED] writes:
On Fri, Dec 24, 1999 at 10:07:38AM +0100, Christian Kurz wrote:
Well this works for people that use the old init-style with links in
/etc/rc* and won't work for people like me that use
On Fri, Dec 24, 1999 at 03:59:46PM -0500, Greg Stark wrote:
Hamish Moffatt [EMAIL PROTECTED] writes:
I sometimes wish we could settle on some of these key technologies,
like the two rc schemes, and inetd versus xinetd. It would make a lot
of things similar. Imagine if we had two menu
Lev,
This is the way I generally do it, although there are some other
ways. First, I run less or more on /var/run/httpd.pid (I am currently
running a Red Hat distro here, but you should look for the same file in
the Debian box which perhaps will be locate somewehere else). This will
I believe if you:
$ kill -HUP `cat /var/run/apache.pid`
apache will reload it's configuration without interruption.
--
++
| Eric G. Milleregm2@jps.net |
| GnuPG public key: http://www.jps.net/egm2/egm2.gpg |
Hello,
could someone please let me know how to restart all of the apache www
daemons that are running so that it'll read the changes made in the
httpd.conf file?
'apache restart' doesn't do anything
is there a generally accepted way of doing this for all 'net daemons?
also, i'm sruprised
On Fri, Oct 08, 1999 at 02:16:36AM -0700, Lev Lvovsky wrote:
Hello,
could someone please let me know how to restart all of the apache www
daemons that are running so that it'll read the changes made in the
httpd.conf file?
'apache restart' doesn't do anything
is there a generally
you can restart via
/etc/init.d/apache restart
or
/etc/init.d/apache reload
you can also use
start-stop-daemon
if it pleases you. =) good luck.
Herbert Ho
On Fri, 8 Oct 1999, Lev Lvovsky wrote:
Hello,
could someone please let me know how to restart all of the apache www
Hi,
To turn off the sunrpc/portmap daemon (or whatever it's called) in potato you
can
just do an 'update-rc.d -f portmap remove', and '/etc/init.d/portmap stop'.
Then it
will be off and won't restart. If you ever want it to start up automatically
again
you'll have know it's priority in the
Gonzalo A. Diethelm [EMAIL PROTECTED] writes:
Just to make things clear, kill doesn't stop anything; it's purpose
in life is to send a given signal to a given process. When you do a
killall -HUP inetd
you are sending a SIGHUP signal to all processes whose name matches
inetd. The inetd
On Aug 15, 1997, at 21:25, George Bonser wrote:
On Wed, 13 Aug 1997, Gonzalo A. Diethelm wrote:
Just to make things clear, kill doesn't stop anything; it's purpose in
life is to send a given signal to a given process. When you do a
killall -HUP inetd
you are sending a
On Aug 12, 1997, at 23:33, George Bonser wrote:
A quick and dirty that I sometimes use:
killall -HUP inetd
Which stops and restarts inetd causing it to re-read the inetd.conf file.
Just to make things clear, kill doesn't stop anything; it's purpose in
life is to send a given signal to
Currently everytime something is changed I reboot... I know there is a
better way, because Linux only needs to reboot after compiling a new
kernel. I want to know how to reload a program in the /etc/inetd.conf
file.
-Paul
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
George Bonser [EMAIL PROTECTED] writes:
killall -HUP inetd
While this will work, killall is a little evil, because it can
sometimes accidentially kill some other things you weren't expecting.
A more precise way to do this would be:
kill -HUP `cat /var/run/inetd.pid`
Either one will get the
20 matches
Mail list logo
