Displaying 20 results from an estimated 800 matches similar to: "Solaris 7 - utmp"
2000 May 11
0
2nd try - Solaris 7 - utmp
A few days ago I installed OpenSSH-2.1.0 together with zlib-1.1.3 and
OpenSSL-0.9.5a on Solaris 7 on an Ultra box.
There appears to be something odd with the utmp stuff... if I just do a
normal configure, utmp logging works fine, but 'w' will give me this:
10:03pm up 13 day(s), 21:42, 3 users, load average: 0.04, 0.07, 0.10
User tty login@ idle JCPU PCPU what
2001 Oct 23
2
PAM problem - sshd segfault on Solaris
I'm using OpenSSH-2.9.9p2 on Solaris 8 sparc64. 2.9p2 worked fine, but
2.9.9p2+ is giving me trouble with one thing - sshd segfaults if I try to
connect and execute a command, such as "ssh machine ls". Otherwise it
works great. sshd will fork, and the child process segfaults.
CVS snapshot does the same thing.
I've narrowed this down somewhat. It will only happen if you use
2000 May 31
3
Solaris utmp problems
Could all those who were having problems with utmp logging on Solaris
please try the test release at:
http://violet.ibs.com.au/openssh/files/test/openssh-TEST-2000053100.tar.gz
Users on other platforms, particularly HP/UX, AIX and SCO are invited
as well, to test compatibility.
The login code is heaps cleaner now.
-d
--
| "Bombay is 250ms from New York in the new world order" -
2003 Oct 09
2
IPC connections and utmp
Hi,
I am running Samba version 2.2.5 with utmp turned on. I have a problem with
utmp and not displaying who is currently logged in. The basic idea is that
even though a user has logged off the computer (win2k pro) a connection to
IPC$ remains. It gives this.
[root@lifesaver root]# smbstatus -u scott
Samba version 2.2.5
Service uid gid pid machine
2000 Apr 21
0
OpenSSH 1.2.3 on AIX 4.3.3
Hmph. I wish I had checked the list before I wasted a half-day on this.
Yes, the problem exists under AIX (mine's 4.3.1). Here's the patch I
came up with, which may be a little more straightforward than the
original. I confirmed that it works under Solaris 2.[67] too.
Don't forget to run autoconf.
--- bsd-login.c.orig Sat Dec 25 18:21:48 1999
+++ bsd-login.c Thu Apr 20 18:26:41
2001 May 10
0
2.9p1: HP-UX 10.20 utmp/wtmp handling broken?
Hi!
I have updated to OpenSSH 2.9p1 on HP-UX 10.20.
Since this update, I seem to have problems with utmp/wtmp handling,
in that entries are not removed as expected.
ws01 36: w
10:06am up 76 days, 12:52, 12 users, load average: 0.17, 0.25, 0.20
User tty login@ idle JCPU PCPU what
...
root pts/8 5:28pm159:41 -
...
ws01 37: ps -ef | grep pts/8
2002 Nov 05
0
UTMP problem and Samba
Hi,
I have had a few tiny problems now that i have samba with utmp. First of
all, I killed a few stray smb processes by using kill -9 pid. Well, this
messed up my 'who' and 'finger' readings.
Now I have this
[root@lifesaver /]# w
11:20pm up 10 days, 8:47, 4 users, load average: 0.00, 0.00, 0.00
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
pshull
1999 Dec 27
1
More patches to fix NetBSD compiling
Unfortunately, the login.c changes after pre-19 have exposed some more
NetBSD-centric problems concerning the lack of several fields in struct utmp.
Here's another set of patches to fix NetBSD compiling (although they may also
help some other UNIXes as well).
Thanks,
David
--- configure.in.orig Mon Dec 27 09:09:05 1999
+++ configure.in Mon Dec 27 09:13:39 1999
@@ -264,6 +264,16 @@
2000 Jun 28
4
openssh-2.1.1p1 on Debian slink and potato
Just today I compilied openssh-2.1.1p1 on Debian Slink and Potato both to come out with the same problem.
I am compiling them with openssl-0.9.5a.. The configure line I use for openssh is below:
./configure --sysconfdir=/etc/ssh --prefix=/usr --with-ssl-dir=../openssl-0.9.5a
So I compile, do a make install restart the sshd daemon and everything seems fine.
Then when I do a w at the prompt
2000 Jan 27
1
Long awaited round 1 of NeXT patches.
This is about 90% of the core work. I omited a few files from the patch
set since they are basicly small blocks of #ifndef HAVE_NEXT/#endif to
get it to compile.
Daimen, feel free to let me know what you applied and what your
rejecting and why.. so I can work on cleaning things up.
Andre, Only thing of note you may want to look into is NeXT does not
use "ut_user" in it's lastlog.
2000 May 30
0
utmpx bug in openssh-2.1.0p2 using Solaris 8
Hi,
I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd
corrupts utmpx/wtmpx when a client connects to this machine. Observable
error:
$ who
who: Error --- entry has ut_type of 28265
when maximum is 9
It can be repeated and is attributable to the login done by sshd. Now,
Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse
as more logins take place
2001 Aug 21
0
Resend: loginrec.c patch
I'm resending this patch just in case it got lost.
The first hunk of the patch fixes a problem with the LOGIN_NEEDS_UTMPX
support in that the date was not being set in the logininfo structure
(causing wrong timestamps in the "last" log).
The second hunk just omits the USE_WTMPX code in the LOGIN_NEEDS_UTMPX
section if USE_UTMPX is defined. This prevents duplicate events in the
2001 Jun 06
0
Remove duplicate "last" log messages with UseLogin
Using UseLogin on a system that has to twiddle utmpx before calling
login currently also twiddles wtmpx, and this causes problems on Solaris
in the "last" log. Changing the source to avoid modifying wtmpx when
also modifying utmpx fixes things up nicely:
Index: loginrec.c
--- loginrec.c 2001/05/08 20:33:06 1.33
+++ loginrec.c 2001/06/06 17:14:25
@@ -456,9 +456,10 @@
# endif
# ifdef
2001 Jun 20
8
[Lutz.Jaenicke@aet.TU-Cottbus.DE: 2.9p1: HP-UX 10.20 utmp/wtmp handling broken?]
Hi!
I am resending the following message about problems with utmp handling.
* In the meantime I had some request in private mail from people asking
whether I have new information.
* The problem is still persistant in 2.9p2.
* My own new investigations show, that the problem only appears with
protocol 2, not with protocol 1, I therefore only started to note it
when protocol 2 became the
2003 May 12
3
[Bug 560] Privsep child continues to run after monitor killed.
http://bugzilla.mindrot.org/show_bug.cgi?id=560
Summary: Privsep child continues to run after monitor killed.
Product: Portable OpenSSH
Version: -current
Platform: ix86
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=164797
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
2000 May 12
0
SunOS 4.x port
This is based on openssh-2.0.0beta1. There are a few rough spots:
1) SunOS doesn't have ut_type in struct utmp so I just whacked
in the old login() from openssh-1.2.3.
2) There is a SUNOS4 section added to defines.h -- this could probably
be a bit cleaner.
3) sigaction on SunOS is implemented via #defines to sigvec, thus there
is no SA_RESTART (this is the default behavior).
2000 Jun 16
3
login reporting (utmp?) problem on Linux
I have recently compiled and installed openssh-2.1.1p1 on a linux box.
The login reporting does not seem to work properly.
When logging into the box via ssh (protocol 1) utmp shows the user logged
in and the tty properly, but the field for the login date/time and the
field for originating host contain all NULLs.
Is anyone else seeing this same behavior, or have I just done something
really
2009 Mar 20
1
w command about user
Hi
I use w command to get user is "2 users" but I only have connection one
ls any process dead? But I check other centos machine is same
How can I check it?
Thank you
[root at host ~]# w
7:22:26 up 20 days, 23:20, 2 users, load average: 0.00, 0.00, 0.00
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
chloe pts/0
2006 Apr 06
3
w stopped working after upgrading procps
Hi
I have just installed a lot of updates on a CentOS 4 box and w appears
to have stopped working -- this machine has 3 or 4 people connected via
ssh, yet this is all that is outputted:
# w
20:46:32 up 301 days, 3:21, 0 users, load average: 0.02, 0.03, 0.04
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
"rpmverify procps" returns nothing so the package
2008 Oct 10
3
RAID on Email Server
I have an email server running Exim, Dovecot, Spamassassin, Clam, etc.
on Centos 4.x 32bit. On occasion I have disk I/O problems. Its
handling several domains and alot of email. Its currently on a single
SATA drive. I am thinking of moving too 3 drives with RAID 1 for
redundancy. RAID 1 will help me on reads but do nothing on writes as
I understand. I am thinking the majority of my I/O is