09-28-2001
kill -9 is king of harsh here... I have success using the HUP (signal 1) kill spec. So you're actually sending the Hang Up signal to all of their processes, which let them all exit gracefully. Anything left running after that is usually killable with a regular kill command (I think it defaults to signal 15, SIGTERM).
I have a script that will kill a user by sending the HUP signal, sleep for a few seconds, send a little bit stronger of a signal, sleep, then finally send any hung processes the -9 SIGKILL signal.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi all,
I am using Sun Solaris 9 .In this system normal users unable to create files from the command line.I added these users in bin,adm and even root group i found them unable to create a file. (1 Reply)
Discussion started by: mallesh
1 Replies
2. Shell Programming and Scripting
Hi all,
I am trying to eject the cdrom from a livecd after certain stage...
Now assuming that it is possible to eject,please consider my issue!!!
The OS boots into a regular user by default...so i am unable to use the eject command to push out the drive...
However if i try pfexec eject it... (3 Replies)
Discussion started by: wrapster
3 Replies
3. UNIX for Dummies Questions & Answers
Thanks
AVKlinux (3 Replies)
Discussion started by: avklinux
3 Replies
4. Shell Programming and Scripting
Hi All
I have written one shell script for GPRS route add is given below named GPRSRouteSet.sh
URL="www.google.com"
VBURL="10.5.2.211"
echo "Setting route for $URL for GPRS"
URL_Address=`nslookup $URL|grep Address:|grep -v "#"|awk -F " " '{print $2}'|head -1`
echo "Executing ... (3 Replies)
Discussion started by: mnmonu
3 Replies
5. UNIX for Advanced & Expert Users
Besides doing some shell-script which loops through /etc/passwd, I was wondering if there was some command that would tell me, like an enhanced version of getent.
The Operating system is Solaris 10 (recent-ish revision) using Sun DS for LDAP. (5 Replies)
Discussion started by: ckmehta
5 Replies
6. Shell Programming and Scripting
Hi I need help..........
I have an Sun One Directory server LDIF file with 5000 user entries, I need to change the data to match Test ID's, so I can run a perf test.
I'm way out of my league as I have not done any scripting for 10 years.
There are four entries for each user in the file... (3 Replies)
Discussion started by: Macdaddy99
3 Replies
7. UNIX for Dummies Questions & Answers
Whenever i switch from root to another user, by doing su - user, it takes me to home directory of user. This is very annoying as i want to be in same dir to run different commands as root sometimes and sometimes as normal user.
How to fix this? (1 Reply)
Discussion started by: syncmaster
1 Replies
8. Shell Programming and Scripting
Hi,
I need to switch from local user to root user in a shell script.
I need to make it automated so that it doesn't prompt for the root password.
I heard the su command will do that work but it prompt for the password.
and also can someone tell me whether su command spawns a new shell or... (1 Reply)
Discussion started by: Little
1 Replies
9. UNIX for Advanced & Expert Users
Hello,
i configured rhel linux 6 with AD directory to authorize windows users to connect on the system and it works.
i have accounts with high privileges (oracle for example) if an account is created on the AD server i would to block him.
I looked for how to do, for the moment all the... (3 Replies)
Discussion started by: vincenzo
3 Replies
LEARN ABOUT REDHAT
fingerd
FINGERD(8) BSD System Manager's Manual FINGERD(8)
NAME
fingerd -- remote user information server
SYNOPSIS
fingerd [-wulf] [-pL path] [-t timeout]
DESCRIPTION
Fingerd is a simple daemon based on RFC1196 that provides an interface to the ``finger'' program at most network sites. The program is sup-
posed to return a friendly, human-oriented status report on either the system at the moment or a particular person in depth.
If the -w option is given, remote users will get an additional ``Welcome to ...'' banner which also shows some informations (e.g. uptime,
operating system name and release) about the system the fingerd is running on. Some sites may consider this a security risk as it gives out
information that may be useful to crackers.
If the -u option is given, requests of the form ``finger @host'' are rejected.
If the -l option is given, information about requests made is logged. This option probably violates users' privacy and should not be used on
multiuser boxes.
If the -f option is given, finger forwarding (user@host1@host2) is allowed. Useful behind firewalls, but probably not wise for security and
resource reasons.
The -p option allows specification of an alternate location for fingerd to find the ``finger'' program. The -L option is equivalent.
The -t option specifies the time to wait for a request before closing the connection. A value of 0 waits forever. The default is 60 sec-
onds.
Options to fingerd should be specified in /etc/xinetd.d/finger.
The finger protocol consists mostly of specifying command arguments. The xinetd(8) ``super-server'' runs fingerd for TCP requests received
on port 79. Once connected fingerd reads a single command line terminated by a <CRLF> which is passed to finger(1). It closes its connec-
tions as soon as all output is finished.
If the line is empty (i.e. just a <CRLF> is sent) then finger returns a ``default'' report that lists all people logged into the system at
that moment. This feature is blocked by the -u option.
If a user name is specified (e.g. eric<CRLF>) then the response lists more extended information for only that particular user, whether
logged in or not. Allowable ``names'' in the command line include both ``login names'' and ``user names''. If a name is ambiguous, all pos-
sible derivations are returned.
SEE ALSO
finger(1), xinetd(8)
RESTRICTIONS
Connecting directly to the server from a TIP or an equally narrow-minded TELNET-protocol user program can result in meaningless attempts at
option negotiation being sent to the server, which will foul up the command line interpretation.
HISTORY
The finger daemon appeared in 4.3BSD.
Linux NetKit (0.17) August 29, 1996 Linux NetKit (0.17)