Login or Register to Ask a Question and Join Our Community


SCO

User process information and idle times

 
Thread Tools Search this Thread
Operating Systems SCO User process information and idle times
Prev   Next
# 1  
Old 05-15-2013
User process information and idle times
My company uses a proprietary GUI to its business system (Strategix) which runs on Windows clients, whereas the back-end runs on a SCO OpenServer 5.0.6a server.

We're moving to a new business system next year and the business is growing and we're running out of licences on Strategix and making our users frustrated when they can't get in. However, with a new business system looming, I'm reluctant to spend £2,000 per extra licence.

I wanted to use the "idleout" facility of SCO to kick out users who were idling along, but Strategix uses a proprietary software interface that doesn't allow me to use the traditional UNIX facilities like "idleout" or "who" or "finger -i". Instead, it comes with it's own binary executable called "adwho", but all that does is list the user and the module in Strategix they are using.

I can use "ps -ef" or "ps -u" to get some process information, but nothing to help with clearly identifying who has been idle for x minutes.

Has anyone got any brilliant ideas?

Cheers for any help.

Mark
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Idle Process Exhausting CPU

I noticed when having some trouble with code I was testing that the CPU was becoming exhausted and I would have to reboot. After rebooting a couple times I decided to check for other problems before trying my code again. That's when I noticed that the CPU with the idle process was through the roof:... (5 Replies)
Discussion started by: Azrael
5 Replies

2. Shell Programming and Scripting

Kill idle Process using a script

Hi, I need a script that can automatically kill all processes named "webrepn" and "webrebw" if idle for more than 30 minutes. Then I will have a Cron Job to run the script every night or 2-3 times a day depends on how this script helps. Right now, I run "ps -ef | grep webrebn" and "kill -9... (7 Replies)
Discussion started by: MaggieL
7 Replies

3. HP-UX

BOGGLED!! User information incorrect when viewing "ps" Process Status

Hello Anyone: I have run into an issue that I have never seen or heard of. Recently on a specific server I have encountered a random issue that I've not been able to repliate on demand... When I view the processes status of a certain process, the information returned to the screen has a... (2 Replies)
Discussion started by: DEN1022
2 Replies

4. Shell Programming and Scripting

Write a scripts to kill idle user for 60 min. & email user list to admin in text file

Folks, I have written one script for following condition by referring some of online post in this forum. Please correct it if I'm missing something in it. (OS: AIX 5.3) List the idle user. (I used whoidle command to list first 15 user and get username, idle time, pid and login time).... (4 Replies)
Discussion started by: sumit30
4 Replies

5. Shell Programming and Scripting

How to get the information about cpu idle from top command?

I am using Ubuntu 9.04. I want to write a shell script to get the information about cpu idle from top command at the real time when i call it, compare cpu idle with 20 (20%), if cpu idle > 20 exit 1, vice versa exit 0. Anybody can help me to resolve it ? Thanks alot. (7 Replies)
Discussion started by: huyquocnguyen
7 Replies

6. AIX

Kill IDLE Process using script !!!

Dear Friends , I am using DB2 database in AIX 5.3 server . In my server some IDLE process are generated after several times which I need to kill it manually each and every time . The process I query like following : root@bagpuss $ ps auxw|sort -r +3|head -10 USER PID %CPU %MEM ... (3 Replies)
Discussion started by: shipon_97
3 Replies

7. Shell Programming and Scripting

How to run a process when the computer is idle?

Hi there, I wrote a script that scans a folder for new files. I don't want to run it at specific times but only when the computer is NOT busy. I tried to use nice but it doesn't really work. I mean, even if my process has less priority, it still slows down the other processes. I did a test... (3 Replies)
Discussion started by: chebarbudo
3 Replies

8. Shell Programming and Scripting

How to kill process after x idle min?

I need a script to kill those process id whose idle time is more than 30min plz help me (3 Replies)
Discussion started by: salil2012
3 Replies

9. UNIX for Dummies Questions & Answers

How to see if the process is idle

We are running AIX 5.3 and for ICICS Printing we have process called cicstermp runing whcih attaches the print to print queue But is process is triggered when ever a print is to be given Can we find the processes which are idle I mean every time a print is given it creats a new cicstermp... (1 Reply)
Discussion started by: pbsrinivas
1 Replies

10. Shell Programming and Scripting

finding idle time of a process

Matez, I have a list of process id's in a text file. I want to know how to find the idle time of a process which are more than 300secs and kill them accordingly. Could you please help me to get these details. I want to write a shell script with this. Thanks..Krish :) (36 Replies)
Discussion started by: Krrishv
36 Replies
Login or Register to Ask a Question

LEARN ABOUT OSF1

biod

nfsiod(8)						      System Manager's Manual							 nfsiod(8)

NAME

       nfsiod, biod - The local NFS compatible asynchronous I/O daemon

SYNOPSIS

       nfsiod [ numthreads ]

DESCRIPTION

       The  nfsiod  daemon  runs  on  an  NFS  compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
       server.	The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread.   If  none	is
       available, the process itself issues the request to the server and waits for the reply.

       The  optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
       accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for  most
       systems.

       When  reading,  if  the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
       the process is currently requesting.  If the readahead completes before the process asks for that block, then the  subsequent  read  system
       call  for that data completes immediately and does not have to wait for the NFS request to complete.  Read ahead will be triggered again so
       the read may find that next block available as well.

       When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the  process.	If
       the  process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
       has to handle a NFS write itself.  This means the process has to wait until the server finishes the write.  For Tru64 UNIX servers, the NFS
       block  size  is	8Kb and UFS tries to cluster I/O 64Kbs at a time.  If the client is running with 7 I/O threads, 8 write requests can be in
       progress at once.  This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.

       Unlike nfsd, each client thread can use either UDP or TCP.  However, if TCP mounts are active, the nfsiod process will time out, close idle
       TCP connections, and acknowledge any connections closed by the server.

       The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos).  Because I/O
       to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.

       The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process.  The ps axml command  displays
       idle  I/O  threads  under  PID  0.  Idle threads will be waiting on nfsiod_wait.  Therefore, if 7 I/O threads are configured, only 1 nfsiod
       process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.

FILES

       Specifies the command path Specifies the file for logging NFS activity.

RELATED INFORMATION

       Commands: nfsd(8), nfsstat(8)

       Daemons: async_daemon(2) delim off

																	 nfsiod(8)