11-28-2005
You can also do a kill -1 on the process. You'll find the pid listed in a file in a directory like /etc/ssh.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i just downloaded and installed succesfully openssh server, and am running it on netbsd 1.5, i can not login with anyuser, i enabled root login just to see what happens and i can login as root, but no other user, i checked my config and most things are default, whats going on? has any one else had... (2 Replies)
Discussion started by: norsk hedensk
2 Replies
2. AIX
Friends,
I made the installation of the ssh in the it conspires,
I configured in the ssh_config the following
parameters..
SyslogFacility AUTH
LogLevel INFO
that should generate sshd.log in the /var/log.... more no this generating.
Somebody could help myself in... (0 Replies)
Discussion started by: sandba
0 Replies
3. UNIX for Dummies Questions & Answers
Can someone tell me the difference between the (2) listed below:
oracle pts/1 ip1 May1 7:11 9:11
oracle sshd ip1 May1 7:11 8:22
How do I read the above information, the fact that the row for pts/1 has a longer time duration than the row for sshd. Why is the... (2 Replies)
Discussion started by: banyan
2 Replies
4. AIX
I installed OpenSSH on AIX 5.1 but when I try to start it, it says:
bash-2.05a# /usr/sbin/sshd
bash-2.05a#
bash-2.05a# tail /var/adm/syslog.out
Jan 8 11:52:22 xyz sshd: fatal: Cannot bind any address.
:confused: (31 Replies)
Discussion started by: untamed
31 Replies
5. Solaris
My ssh log appear to the screen which i want it to be log to /var/log/sshd.log
how to log the sshd to /var/log? (5 Replies)
Discussion started by: hezry79
5 Replies
6. Solaris
Hello,
On Linux the /etc/ssh/sshd_config has the "AcceptEnv" parameter which allows to "push" environment setting to a ssh session. For example, when I set in sshd_conf
AcceptEnv BLAHI can then ssh to the server using:
user@client~$ export BLAH=hello
user@client~$ ssh server -o SendEnv=BLAH
... (2 Replies)
Discussion started by: RobertFord
2 Replies
7. Solaris
Hi Everyone,
I am just curious, if sshd service is restarted on these OS Solaris 8,9,10 remotely will the session expires?? . I knew we can restart sshd in solaris 10 that will no effect any current session please suggest for 8,9
Thanks, (2 Replies)
Discussion started by: bobby320
2 Replies
8. Solaris
Hi,
I was able to putty a few server (Solaris 10) of mine using hostname, but when i change to ip address, it shows
login as: root
Using keyboard-interactive authentication.
Password:
Access denied
I change PermitRootLogin to yes. I tried to do a sshd restart, however
... (6 Replies)
Discussion started by: beginningDBA
6 Replies
9. Solaris
I have shamelessly tried all the possible ways to see if my /var/adm/loginlog logs user access entries for ssh but nothing has worked for me so far..:confused:
for telnet login its working fine.
Adding auth.info in syslog.conf works but i dont want that output.
Is there any way to edit... (2 Replies)
Discussion started by: ningy
2 Replies
10. Red Hat
Hi,
Do you know what cause the error message ?
Nov 19 13:42:19 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in /etc/environment', ignoring
Nov 19 13:42:20 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in... (0 Replies)
Discussion started by: xitrum
0 Replies
KILL(2) BSD System Calls Manual KILL(2)
NAME
kill -- send signal to a process
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <signal.h>
int
kill(pid_t pid, int sig);
DESCRIPTION
The kill() function sends the signal given by sig to pid, a process or a group of processes. sig may be one of the signals specified in
sigaction(2) or it may be 0, in which case error checking is performed but no signal is actually sent. This can be used to check the valid-
ity of pid.
For a process to have permission to send a signal to a process designated by pid, the real or effective user ID of the receiving process must
match that of the sending process or the user must have appropriate privileges (such as given by a set-user-ID program or the user is the
super-user). A single exception is the signal SIGCONT, which may always be sent to any descendant of the current process.
If pid is greater than zero:
sig is sent to the process whose ID is equal to pid.
If pid is zero:
sig is sent to all processes whose process group ID is equal to the process group ID of the sender, and for which the process has
permission; this is a variant of killpg(3).
If pid is -1:
If the user has super-user privileges, the signal is sent to all processes excluding system processes and the process sending the
signal. If the user is not the super user, the signal is sent to all processes with the same uid as the user excluding the process
sending the signal. No error is returned if any process could be signaled.
For compatibility with System V, if the process number is negative but not -1, the signal is sent to all processes whose process group ID is
equal to the absolute value of the process number. This is a variant of killpg(3).
RETURN VALUES
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
kill() will fail and no signal will be sent if:
[EINVAL] sig is not a valid signal number.
[ESRCH] No process can be found corresponding to that specified by pid.
[ESRCH] The process id was given as 0 but the sending process does not have a process group.
[EPERM] The sending process is not the super-user and its effective user id does not match the effective user-id of the receiving
process. When signaling a process group, this error is returned if any members of the group could not be signaled.
SEE ALSO
getpgrp(2), getpid(2), sigaction(2), killpg(3), signal(7)
STANDARDS
The kill() function is expected to conform to ISO/IEC 9945-1:1990 (``POSIX.1'').
BSD
April 19, 1994 BSD