11-22-2002
I think that's great - who cares if you know what buttons to push if you don't understand why it works? What happens when that button doesn't work for some reason?
Kudos to Perderabo for his always-elightening posts!
And to yls177, don't kill -9 logins... In fact, don't kill -9 anything unless you're unable to kill -1, kill -15, kill -2, etc first!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Is it possible to install unix on a system which already runs windows 98? (2 Replies)
Discussion started by: ms73eb
2 Replies
2. Solaris
Hi,
I'm new to solaris/ Unix and would like to know how to check in the system what
was the last login user were doing. Is there any way to check this? Thanks in advanced. (1 Reply)
Discussion started by: raziayub
1 Replies
3. Cybersecurity
Hy everyone!
I'm trying to lock out system accounts on my Tru64 UNIX machines.
Wherever I look, it says only to put Nologin or *Nologin in password field of desired account in /etc/passwd.
But it doesn't work. I still can su to that accounts. There are some accounts that already have Nologin... (1 Reply)
Discussion started by: veccinho
1 Replies
4. HP-UX
Hello,
I'm new to HP-UX. I have a system running B.11.23 on ia64. The system gets its user passwords via active directory. Everytime a new account is added to AD a script pushes out the account info to all the systems and this system is updated too. However, on this machine, users are unable to... (2 Replies)
Discussion started by: BFLO
2 Replies
5. UNIX for Advanced & Expert Users
Hi,
I was add my shell script in /etc/rc.d/rc.local file
Eg.
sh /root/KernelModule.sh
my KernelModule.sh contain
insmod xxxxx.ko
insmod yyyy.ko
I have insmod 22 kernelmodule in this script , all the modules are my own driver modules.
now problem is my system is booting but... (2 Replies)
Discussion started by: rajamohan
2 Replies
6. Solaris
Hello
I have a question that may sound stupid after and maybe it is.
We are syncing our sytem time via ntp from a reference time server. all works quite well
but due to a mall applikation which not accepts timestamps from our servers that in the future,
and if it even was 1 ms, we have to... (1 Reply)
Discussion started by: demwz
1 Replies
7. AIX
Guy's
I have AIX 6.1 has some slowness when I login to the system ..
When I login by user screen hangs for some time 20 seconds then it's give me the command prompt .. !
system is fine is working fine only this issue I faced can you please help me in this .. what's the expected reason... (2 Replies)
Discussion started by: ITHelper
2 Replies
8. Shell Programming and Scripting
Want to find the stdout for the partiuclar user login for past 12 hrs.
Say for eg : user login id is teladm
And the host name is sys22prod
I want to see the stdout for that user id in that host for past 12 hrs (1 Reply)
Discussion started by: mail2sant
1 Replies
9. Programming
I'm new to C++.
I have a text file named idpw.txt which is storing id and password
e.g
admin password
account1 abc
john hello
Here's my code so far:
bool login()
{
string user,password, user1, password1;
ifstream myfile("idpw.txt");
cout << "Please enter your username" <<... (3 Replies)
Discussion started by: andylbh
3 Replies
10. Solaris
Hi,
Am writing a script where I want to find uptime of certain servers. Is there any command where we can find uptime without login to the server, since the server list is big logging to the server will time consuming.
Thanks in advance (7 Replies)
Discussion started by: rogerben
7 Replies
KILL(1) BSD General Commands Manual KILL(1)
NAME
kill -- terminate or signal a process
SYNOPSIS
kill [-s signal_name] pid ...
kill -l [exit_status]
kill -signal_name pid ...
kill -signal_number pid ...
DESCRIPTION
The kill utility sends a signal to the processes specified by the pid operands.
Only the super-user may send signals to other users' processes.
The options are as follows:
-s signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-l [exit_status]
If no operand is given, list the signal names; otherwise, write the signal name corresponding to exit_status.
-signal_name
A symbolic signal name specifying the signal to be sent instead of the default TERM.
-signal_number
A non-negative decimal integer, specifying the signal to be sent instead of the default TERM.
The following PIDs have special meanings:
-1 If superuser, broadcast the signal to all processes; otherwise broadcast to all processes belonging to the user.
Some of the more commonly used signals:
1 HUP (hang up)
2 INT (interrupt)
3 QUIT (quit)
6 ABRT (abort)
9 KILL (non-catchable, non-ignorable kill)
14 ALRM (alarm clock)
15 TERM (software termination signal)
Some shells may provide a builtin kill command which is similar or identical to this utility. Consult the builtin(1) manual page.
EXIT STATUS
The kill utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
Terminate the processes with PIDs 142 and 157:
kill 142 157
Send the hangup signal (SIGHUP) to the process with PID 507:
kill -s HUP 507
SEE ALSO
builtin(1), csh(1), killall(1), ps(1), sh(1), kill(2), sigaction(2)
STANDARDS
The kill utility is expected to be IEEE Std 1003.2 (``POSIX.2'') compatible.
HISTORY
A kill command appeared in Version 3 AT&T UNIX.
BUGS
A replacement for the command ``kill 0'' for csh(1) users should be provided.
BSD
April 28, 1995 BSD