07-07-2009
Did you search specific for your OS? What kind of Unix or Linux is it? Are you up-to-date with patches etc?
Had something like this on 2 old AIX 5.1 boxes. They were already on the latest level and since they were running ok I did not dig any further since AIX 5.1 is somewhat old.
Just for curiousity you could check your wtmp with last or something like that.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm looking for some help, please!
I'm trying to kill any idle user processes over 40 Minutes.
I have tried putting TMOUT=2400
within the users .profile
However this does not seem to be working.
We run aix 4.3.3
with ORACLE 7.3
The above works o.k. when the user is only within the... (3 Replies)
Discussion started by: annette
3 Replies
2. UNIX for Advanced & Expert Users
Hi All,
I heared that each user in UNIX have max. number of processes that can be running at one time. Is this correct? If yes, how can I know this number and how can I change it.
N.B.: I am using Sun 5.6
Regards (4 Replies)
Discussion started by: omran
4 Replies
3. Solaris
how can I kill all the processes belonging to an user.
I need it because I can't see a process initiated by a user and thus unable to kill it. (2 Replies)
Discussion started by: krishan
2 Replies
4. Shell Programming and Scripting
Hi All
I am being trained in unix and am tryin to write a script for listing the user Processes by user's names exactly the following manner WITHOUT USING A TEMPORARY FILE or SED OR AWK! The format of the output I want is:
James Hallan
PID TTY TIME CMD
31799 pts/3 00:00:00 vim
31866... (1 Reply)
Discussion started by: kartikkumar84@g
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All
I am being trained in unix and am tryin to write a script for listing the user Processes by user's names exactly the following manner WITHOUT USING A TEMPORARY FILE or SED OR AWK! The format of the output I want is:
Code:
James Hallan
PID TTY TIME CMD
31799 pts/3 00:00:00 vim ... (2 Replies)
Discussion started by: kartikkumar84@g
2 Replies
6. Shell Programming and Scripting
Hi there, i've been searching all over and i thought i had understood the way i should go to kill all the processes related to a user. But i'm getting more confused then i was.
By lunch time i have to make a database backup, and for that all the users shoul logout. The problem is that many users... (4 Replies)
Discussion started by: vascobrito
4 Replies
7. Shell Programming and Scripting
Hi,
Please can some one advise how can we get all the processes corresponding to a particular user.
Cheers,
Shazin (4 Replies)
Discussion started by: Shazin
4 Replies
8. Shell Programming and Scripting
Hello guys,
what i want to do is to print a table with two columns (user :: #procs) on the stdout.
The first column should show the users and the second one the number of processes the respective user runs.
I think I need something like the count() - function in sql, don't i?
Shell: Bash
... (2 Replies)
Discussion started by: tiptop
2 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
I have to write a program which can tell me how many processes is running by some user, from the /etc/passwd file... (3 Replies)
Discussion started by: petel1
3 Replies
10. AIX
Morning,
Somebody can tell me in AIX 6.1 what is the different between the maxuproc (lsattr -El sys0 | grep max) and the for a user.
Example:
Oracle is limited by :
#ulimit -u
processes(per user) unlimited
But lsattr -El sys0| grep maxuproc show me :
maxuproc 16384
So... (1 Reply)
Discussion started by: bacup540
1 Replies
fuser(1M) fuser(1M)
NAME
fuser - list processes using a file or file structure
SYNOPSIS
file ... file ...] ...
DESCRIPTION
The command lists the process IDs of processes that have each specified file open. For block special devices, all processes using any file
on that device are listed. The process ID may be followed by a letter, identifying how the file is being used, as follows:
file is current directory of the process.
file is the root directory of the process, as set up by the command (see chroot(1M)).
The process has
file open.
The process has
file memory mapped.
file is the text file of the process.
The process IDs associated with each file are printed to standard output as a single line separated by spaces and terminated with a single
newline. All other output -- the file name, the letter, and the user name -- is written to standard error.
Options
has the following options:
Display the use of a mount point and any file beneath that
mount point. Each file must be a file system mount point.
Display the use of the named file only,
not the files beneath it if it is a mounted file system. This is the default.
Display the login user name in parentheses following each process ID.
Send the
signal to each process using each file. You must have appropriate privileges to kill processes that you do not own.
You can respecify options between groups of files. The new set of options replaces the old set. A dash by itself cancels all options cur-
rently in force.
Operands
has the following operand:
file One of the following values:
o With the option, the name of a file.
o With the option, the name of a mounted file system or special file.
o With the option, the name of a file system mount point.
NETWORKING FEATURES
You can use with NFS file systems or files. If the file name is in the format used in to identify an NFS file system, treats the NFS file
system as a block special device and identifies any process using that file system.
If contact with an NFS file system is lost, fails, since contact is required to obtain the file system identification. Once the NFS file
system is recontacted, stale file handles from the previous contact can be identified, provided that the NFS file system has the same file
system identification.
EXAMPLES
Terminate all processes that are preventing disk drive 1 from being unmounted, listing the process ID and login name of each process being
killed.
List process IDs and login names of processes that have the password file open.
Combine both the above examples into a single command line.
If the device is mounted on directory list the process IDs and login names of processes using the device. Alternately, if is the mount
point for an NFS file system, list process IDs and login names of processes using that NFS file system.
If is an NFS file system, list all processes using any file on that file system. If it is not an NFS file system, treat it as a regular
file.
SEE ALSO
ps(1), mount(1M), kill(2), signal(2).
STANDARDS CONFORMANCE
fuser(1M)