08-16-2013
How to stop the uprintfd daemon?
How to stop the uprintfd daemon? After uncommenting, kill -9 doesn't work on the process either.
EDIT: Nevermind. I've got this now.
Cheers,
DH
Last edited by Devyn; 08-16-2013 at 11:28 AM..
10 More Discussions You Might Find Interesting
1. Programming
I want to write background running program. How to use daemon function. Please send me source code.
Thanks. (1 Reply)
Discussion started by: bat_oyu
1 Replies
2. Programming
how to convert a c program into a Daemon.
thanks in advance
svh (2 Replies)
Discussion started by: svh
2 Replies
3. Solaris
Say I have a daemon that dies for an unknown reason. Is there a way to track its process ID to try to determine when it dies and what causes it to go away? (2 Replies)
Discussion started by: Silver11
2 Replies
4. Linux
how i will write the daemon process,if any body have sample daemon process send me. (1 Reply)
Discussion started by: suresh_rupineni
1 Replies
5. Solaris
Hi there
I get the following message im my messages file 2 or 3 times a second
Dec 4 11:44:18 my-box in.timed: connect from localhost
I would like to stop in.timed from logging to syslog altogether as this message is filling up my disk.
I dont want to stop daemon.info altogether... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
6. UNIX for Advanced & Expert Users
Hi ,
I have one question, suppose i am a normal user and when i use 'w' command , it shows who is logged on and what they are doing .
Now i want to stop others users to know what i am doing accept the root ?
can i do this ?
thanks (5 Replies)
Discussion started by: mobile01
5 Replies
7. Programming
i want to write a daemon service which listens the 8080 port and write down all the details in one file. How can i do this ? (2 Replies)
Discussion started by: santosh123
2 Replies
8. Shell Programming and Scripting
I think I have an issue almost like Sammy_T's. I want to make a piece of code run as a daemon. I have some java, along with it 15 classpath's converted to a shell script that I can "runmyjavap". The script is just what I need to run after compiling it:
#!/bin/sh
java -classpath : ...(from... (3 Replies)
Discussion started by: Miller_K
3 Replies
9. Solaris
I'm setting up a solaris server at home.
At the moment I have to keep running:
/etc/init.d/nfs.server start
To start my NFS server process. Is there anything I can do to make this happen automatically at boot?
Many thanks in anticipation.
Stin. (4 Replies)
Discussion started by: Stin
4 Replies
10. Homework & Coursework Questions
Manually we can stop the daemon by stopsrc command other-than this In which case mountd daemon will crash automatically. (1 Reply)
Discussion started by: t.balamurugan
1 Replies
KILL(1) General Commands Manual KILL(1)
NAME
kill - terminate a process with extreme prejudice
SYNOPSIS
kill [ -sig ] processid ...
kill -l
DESCRIPTION
Kill sends the TERM (terminate, 15) signal to the specified processes. If a signal name or number preceded by `-' is given as first argu-
ment, that signal is sent instead of terminate (see sigvec(2)). The signal names are listed by `kill -l', and are as given in
/usr/include/signal.h, stripped of the common SIG prefix.
The terminate signal will kill processes that do not catch the signal; `kill -9 ...' is a sure kill, as the KILL (9) signal cannot be
caught. By convention, if process number 0 is specified, all members in the process group (i.e. processes resulting from the current
login) are signaled (but beware: this works only if you use sh(1); not if you use csh(1).) Negative process numbers also have special
meanings; see kill(2) for details.
The killed processes must belong to the current user unless he is the super-user.
The process number of an asynchronous process started with `&' is reported by the shell. Process numbers can also be found by using ps(1).
Kill is a built-in to csh(1); it allows job specifiers of the form ``%...'' as arguments so process id's are not as often used as kill
arguments. See csh(1) for details.
SEE ALSO
csh(1), ps(1), kill(2), sigvec(2)
BUGS
A replacement for ``kill 0'' for csh(1) users should be provided.
4th Berkeley Distribution April 20, 1986 KILL(1)