Sponsored Content
Full Discussion: Processes
Top Forums UNIX for Dummies Questions & Answers Processes Post 302356317 by jlliagre on Friday 25th of September 2009 06:51:22 AM
Old 09-25-2009
They are obviously at least performing both of these actions but quite several more.

Looks like homework, doesn't it ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

co-processes

Is it possible to have a main script (i will call it main.ksh) that executes say, 4 other scripts (sub_prog_1.ksh, sub_prog_2.ksh etc..) from within this main.ksh (simultaneously/in parallel), have them run in the background and communicate back to main.ksh when complete? My guess is to use... (1 Reply)
Discussion started by: google
1 Replies

2. UNIX for Dummies Questions & Answers

processes

What command string will locate ONLY the PID of a process and ouput only the number of PID of the process? (1 Reply)
Discussion started by: mma_buc_98
1 Replies

3. Shell Programming and Scripting

I need some example of Co-Processes

I want to know how to work the Co-Processes in kornshell scripts. So, I very need some script about Co-Processes! thanks ...:) (3 Replies)
Discussion started by: javalee
3 Replies

4. Filesystems, Disks and Memory

processes

write a program create two processes to run a for loop which adds numbers 1 to n , say one process adds odd numbers and other adds even numbers (1 Reply)
Discussion started by: jayaram_miryabb
1 Replies

5. UNIX for Dummies Questions & Answers

Processes

Can someone tell how to find out how long a process has been running? I want to find something that is usually there that the paging system can check on. Thanks (4 Replies)
Discussion started by: Beetlejuice
4 Replies

6. Shell Programming and Scripting

Processes

I have a file like this. No. State Query Times User Processed Syslog 1 ready idle 973s 0 /Application/ugsvols/bldata01/logs/imanscript1562.syslog 2 ready idle 803s 83997 13 /Application/ugsvols/bldata01/logs/imanscript1542.syslog 3 ready idle 2954s 106641... (17 Replies)
Discussion started by: Krrishv
17 Replies

7. UNIX for Advanced & Expert Users

Monitoring Processes - Killing hung processes

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

8. Solaris

Identifying and grouping OS processes and APP processes

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

9. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

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

10. UNIX for Dummies Questions & Answers

processes

may i know a command to find processes not attached to a terminal?? (1 Reply)
Discussion started by: riya9
1 Replies
ruptime(1c)															       ruptime(1c)

Name
       ruptime - show host status of local machines

Syntax
       ruptime [ options ] [ machinename ]

Description
       The  command  gives  a  status  line  like  for each machine on the local network.  If a machinename is given, the status of only the named
       machine is given.  These status lines are formed from packets broadcast by each host on the network once a minute.

       Machines for which no status report has been received for 5 minutes are shown as being down.

Options
       -a   Users idle an hour or more are not counted unless this option is specified.

       -d   Display only those hosts that are considered down.

       -l   Sort the status list by load average.  If more than one sort option is given, uses the last one.

       -r   Show only hosts that are up and running.

       -t   Sort the status list by uptime.  If more than one sort option is given, uses the last one.

       -u   Sort the status list by number of users.  If more than one sort option is given, uses the last one.

       -nn  Show only those hosts with nn or more users.

Restrictions
       Because the daemon sends its information in broadcast packets it generates a large amount of network traffic.  On large networks the  extra
       traffic	may  be  objectionable.   Therefore,  the  daemon is disabled by default.  To make use of the daemon for both the local and remote
       hosts, remove the comment symbols (#) from in front of the lines specifying in the file.

       If the daemon is not running on a remote machine, the machine may incorrectly appear to be down when you use the command to  determine  its
       status.	See the reference page for more information.

       If  a  system  has  more  than 40 users logged in at once, the number of users displayed by the command is incorrect.  Users who login to a
       machine after that point fail to increment the user count that appears in the output of the command.  This is due to the maximum size limit
       of an Ethernet packet, which is 1500 bytes, and the fact that the daemon must broadcast its information in a single packet.

Files
       /usr/spool/rwho/whod.*	Information about other machines

See Also
       rwho(1c), rwhod(8c)

																       ruptime(1c)
All times are GMT -4. The time now is 12:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy