06-16-2005
If you can, force your users to log out. Make the change, then allow them back in.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies
2. Shell Programming and Scripting
I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies
3. AIX
Hello list,
Have a problem that's highlighting gaps in my knowledge; can you assist?
We have a script that's tacked onto our trading application which allows branch managers etc. to kill off the sessions of other users at their branch. A menu option in the application spawns a shell running... (8 Replies)
Discussion started by: alexop
8 Replies
4. HP-UX
Hi,
In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Discussion started by: efrenba
12 Replies
5. Shell Programming and Scripting
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
6. AIX
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
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies
8. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
9. Shell Programming and Scripting
Hello..
I have many sleepy users on my Solaris box and need to kill them if they are idle for more than 45 minutes for example...I know who -u gives and the idle time but unable to make a awk line to get the condition perfect. Please help...:wall: (9 Replies)
Discussion started by: wimaxpole
9 Replies
10. Shell Programming and Scripting
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
LEARN ABOUT DEBIAN
watchgnupg
WATCHGNUPG(1) GNU Privacy Guard WATCHGNUPG(1)
NAME
watchgnupg - Read and print logs from a socket
SYNOPSIS
watchgnupg [--force] [--verbose] socketname
DESCRIPTION
Most of the main utilities are able to write their log files to a Unix Domain socket if configured that way. watchgnupg is a simple lis-
tener for such a socket. It ameliorates the output with a time stamp and makes sure that long lines are not interspersed with log output
from other utilities. This tool is not available for Windows.
watchgnupg is commonly invoked as
watchgnupg --force ~/.gnupg/S.log
OPTIONS
watchgnupg understands these options:
--force
Delete an already existing socket file.
--tcp n
Instead of reading from a local socket, listen for connects on TCP port n.
--verbose
Enable extra informational output.
--version
Print version of the program and exit.
--help Display a brief help page and exit.
EXAMPLES
$ watchgnupg --force /home/foo/.gnupg/S.log
This waits for connections on the local socket '/home/foo/.gnupg/S.log' and shows all log entries. To make this work the option log-file
needs to be used with all modules which logs are to be shown. The value for that option must be given with a special prefix (e.g. in the
conf file):
log-file socket:///home/foo/.gnupg/S.log
For debugging purposes it is also possible to do remote logging. Take care if you use this feature because the information is send in the
clear over the network. Use this syntax in the conf files:
log-file tcp://192.168.1.1:4711
You may use any port and not just 4711 as shown above; only IP addresses are supported (v4 and v6) and no host names. You need to start
watchgnupg with the tcp option. Note that under Windows the registry entry HKCUSoftwareGNUGnuPG:DefaultLogFile can be used to change
the default log output from stderr to whatever is given by that entry. However the only useful entry is a TCP name for remote debugging.
SEE ALSO
gpg(1), gpgsm(1), gpg-agent(1), scdaemon(1)
The full documentation for this tool is maintained as a Texinfo manual. If GnuPG and the info program are properly installed at your site,
the command
info gnupg
should give you access to the complete manual including a menu structure and an index.
GnuPG 2.0.19 2014-06-26 WATCHGNUPG(1)