Sponsored Content
Full Discussion: Slower slower dead
Top Forums UNIX for Dummies Questions & Answers Slower slower dead Post 6896 by Neo on Friday 14th of September 2001 12:11:37 PM
Old 09-14-2001
You may have a process running with a memory leak. So, you need to isolate the leak by finding a way to take periodic snapshots of the process table and write them to a file with a time stamp. Then, when you reboot the machine, you can log in and find the offending process.

ps with right right switches, exeuted from the crontab, and output redirected properly, will do the trick.

On the other hand, you can just login when the system has been running for a while and manually check your processes. You may easily find it that way if you can get in, remotely.
 

8 More Discussions You Might Find Interesting

1. Programming

TCP/IP send getting slower

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower ie, the messages are not send quickly to the client. What i mean to say is since the... (0 Replies)
Discussion started by: rajesh_puru
0 Replies

2. UNIX for Advanced & Expert Users

TCP/IP Connection getting slower...

Hi, We have developed a server program using TCP/IP Communication to communicate with another client program. After running for some days we find the TCP/IP connection from the server program is getting slower. What i mean to say is since the send() function in the server program (it is... (2 Replies)
Discussion started by: rajesh_puru
2 Replies

3. Solaris

Why is restore slower than backup?

After my big disaster, I'm restoring from tape on my Sun box. This is the second time I've used 'ufsrestore' with this DEC TZ88 SCSI DLT drive. The last time was for a migration from one box to another. Both the last time and this time, the restore has taken a hell of a lot longer than the... (4 Replies)
Discussion started by: deckard
4 Replies

4. UNIX for Advanced & Expert Users

Why is cut slower than awk?

Hi all, for test reasons I tried the following two one-liners: time awk '{print $4}' T_64xSC_128RW_K500.dat > /dev/nulland time cut -d" " -f6 T_64xSC_128RW_K500.dat > /dev/nullThe file contains approx. 250k lines. awk does it in 0.15 secs (real), cut in 0.44. The user time has about the... (3 Replies)
Discussion started by: BandGap
3 Replies

5. Linux

GCC compiles a lot slower than it should

Hello everyone, i'm having a problem compiling an application i'm developing. For a month, while developing, i did lots of compilations to test it. While compiling, i noticed gcc did it pretty slow, but gave it no importance. I'm using ubuntu 10.04 32bits, and my pc has: - Dual core intel... (1 Reply)
Discussion started by: adadon
1 Replies

6. What is on Your Mind?

Usenet is dead

On servers i check there seems to be no news at all. (3 Replies)
Discussion started by: Action
3 Replies

7. Shell Programming and Scripting

sed is dead

Hello everybody, I'm new to bash scripting (and scripting in general) but I'm making decent progress in the hands-on solutions I need... I've encountered a problem that seemed very simple to me at first, but had me going on for hours. Maybe you can help me. Say I have an input text file like... (2 Replies)
Discussion started by: origamisven
2 Replies

8. Solaris

Job Run Slower using Autosys than running through terminal

Hi All, We run Many jobs evryday using Autosys. Sometimes due to various reason we got to run the job from terminal as well (using nohup). We observed that the job running through terminal(nohup) takes much less time then the autosys (for same job). What can be the possible reason for such... (1 Reply)
Discussion started by: kg_gaurav
1 Replies
PIDOF(8)						Linux System Administrator's Manual						  PIDOF(8)

NAME
pidof -- find the process ID of a running program. SYNOPSIS
pidof [-s] [-c] [-n] [-x] [-o omitpid[,omitpid..]] [-o omitpid[,omitpid..]..] program [program..] DESCRIPTION
Pidof finds the process id's (pids) of the named programs. It prints those id's on the standard output. This program is on some systems used in run-level change scripts, especially when the system has a System-V like rc structure. In that case these scripts are located in /etc/rc?.d, where ? is the runlevel. If the system has a start-stop-daemon (8) program that should be used instead. OPTIONS
-s Single shot - this instructs the program to only return one pid. -c Only return process ids that are running with the same root directory. This option is ignored for non-root users, as they will be unable to check the current root directory of processes they do not own. -n Avoid stat(2) system function call on all binaries which are located on network based file systems like NFS. Instead of using this option the the variable PIDOF_NETFS may be set and exported. -x Scripts too - this causes the program to also return process id's of shells running the named scripts. -o omitpid Tells pidof to omit processes with that process id. The special pid %PPID can be used to name the parent process of the pidof pro- gram, in other words the calling shell or shell script. EXIT STATUS
0 At least one program was found with the requested name. 1 No program was found with the requested name. NOTES
pidof is actually the same program as killall5; the program behaves according to the name under which it is called. When pidof is invoked with a full pathname to the program it should find the pid of, it is reasonably safe. Otherwise it is possible that it returns pids of running programs that happen to have the same name as the program you're after but are actually other programs. Note that that the executable name of running processes is calculated with readlink(2), so symbolic links to executables will also match. SEE ALSO
shutdown(8), init(8), halt(8), reboot(8), killall5(8) AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl 01 Sep 1998 PIDOF(8)
All times are GMT -4. The time now is 08:17 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy