10-16-2003
Good Question!
To understand processes you have to pick up a Operating System book.
In general terms, a process is a job or time-shared program. Processes can also have subprocesses and so on.
A daemon is a server process that waits for communication.
Handeling processes is another story.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am new to the world of Unix, I need some help in doing a small project at work.
Can anyone point out any good references for the below functions?
Objective
---------
To write a daemon that will run in the central server to
1) access our process(I will find this out), log down... (1 Reply)
Discussion started by: seongyin
1 Replies
2. UNIX for Advanced & Expert Users
Is there a way to monitor certain processes and if they hang too long to kill them, but certain scripts which are expected to take a long time to let them go?
Thank you
Richard (4 Replies)
Discussion started by: ukndoit
4 Replies
3. AIX
Hi,
As part of our maintenance schedule, we reboot our systems every few months to test HACMP and etc... etc....
It looked like everything was normal but when we tried to bring up HACMP, we didn't see anything in the /etc/hacmp.out and we didn't see any processes associated with HACMP running.... (0 Replies)
Discussion started by: xender69
0 Replies
4. Solaris
Hi
Is there an easy way to identify and group currently running processes into OS processes and APP processes. Not all applications are installed as packages.
Any free tools or scripts to do this?
Many thanks. (2 Replies)
Discussion started by: wilsonee
2 Replies
5. Ubuntu
Hello,
I am debugging a program which works as daemon. It sigfaults, unfortunately I'm unable to generate core dump file. Here is what I am doing:
tsurko@bastila:~$ ulimit -c unlimited
tsurko@bastila:~$ ulimit -c
unlimited
tsurko@bastila:~$ cat /etc/sysctl.conf | grep 'core_pattern'... (1 Reply)
Discussion started by: tsurko
1 Replies
6. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
7. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
8. Solaris
I normally use "chkconfig" to configure start up services in a particular run level.....
But i don't know how to do it in solaris 10.... please help me !!! (2 Replies)
Discussion started by: vamshigvk475
2 Replies
9. Shell Programming and Scripting
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies
10. Linux
Hi,
Is there any way to run chkconfig --list and to display all daemon processes in PRIORITY order, not in alphabetic order?
Thank you. (4 Replies)
Discussion started by: hce
4 Replies
RENICE(8) System Manager's Manual RENICE(8)
NAME
renice - alter priority of running processes
SYNOPSIS
renice priority [ [ -p ] pid ... ] [ [ -g ] pgrp ... ] [ [ -u ] user ... ]
DESCRIPTION
Renice alters the scheduling priority of one or more running processes. The who parameters are interpreted as process ID's, process group
ID's, or user names. Renice'ing a process group causes all processes in the process group to have their scheduling priority altered.
Renice'ing a user causes all processes owned by the user to have their scheduling priority altered. By default, the processes to be
affected are specified by their process ID's. To force who parameters to be interpreted as process group ID's, a -g may be specified. To
force the who parameters to be interpreted as user names, a -u may be given. Supplying -p will reset who interpretation to be (the
default) process ID's. For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root.
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
within the range 0 to PRIO_MAX (20). (This prevents overriding administrative fiats.) The super-user may alter the priority of any
process and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20 (the affected processes will
run only when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO
getpriority(2), setpriority(2)
BUGS
Non super-users can not increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in
the first place.
4th Berkeley Distribution November 17, 1996 RENICE(8)