Displaying 20 results from an estimated 2000 matches similar to: "UTMP problem and Samba"
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
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
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
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
2000 May 10
0
Solaris 7 - utmp
Today 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
wyodlows
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 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
2007 May 08
1
Wield CPU load problem??
Recently we installed CENTOS 4.4 on DELL 2650 server.
We found CPU load always on 3 and up if we run "top"
or "w" to check. There is NO application run on this
server why CPU load so heavy?
======= messages from check up ===
%w
11:31:56 up 20:02, 3 users, load average: 3.06,
3.03, 3.00
USER TTY FROM LOGIN@ IDLE
JCPU PCPU WHAT
oracle pts/1
2013 Jan 17
2
Centos 6.3: load average strangeness
Hi, on my c6.3 server (guest of a vmware host) I have a strange load
average value:
w command:
> [root at s-doc ~]# w
> 11:19:23 up 41 days, 23:15, 1 user, load average: 4,03, 4,03, 4,00
> USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
> root pts/2 dodo:S.0 11:15 0.00s 0.02s 0.00s w
top command:
> top - 12:13:31 up 42 days, 9 min, 1
2000 Dec 15
0
sshd demons
Hi there, I'm having a problem with sshd demons not shuting down after
connection is closed.
The strange thing is that this is happening on both my Redhat 6.2 server and
Redhat 7.0, both running
OpenSSH_2.3.0p1. I'm positive that KeepAlive is set to yes !
Is this a common problem ? I'm suspecting that is has something to do with
the client as well. Think we're all using
2002 Jun 19
0
Winbind problem, can resolve NT machine names to IP, but not IP t o name
Hi,
Ive got samba 2.2.3a-6 setup on my Redhat 7.3 box, winbind is also
configured, wbinfo can resolve NT machine names to IP's, and IP's to NT
machine names:
wbinfo -h core
192.168.179.250 core
wbinfo -i 192.168.179.250
192.168.179.250 CORE @CORE
In /etc/nsswitch.conf I have:
hosts: files nisplus wins dns
I can ping core :
ping core
PING core (192.168.179.250) from
2000 May 11
3
OpenSSH-2.1: FROM in 'w' empty?
Hello all,
I wonder if this is an oversight/bug/feature, but here it goes.
It seems that in OpenSSH 2.1, 'w' (or who) command may print out something
like this:
----
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
pekkas ttyp1 - 3:10am 0.00s 0.08s 0.03s w
----
2.0beta1 was the one I used before, and that printed FROM field properly.
Now,
2016 May 26
5
[Bug 2572] New: dead sessions aren't closed despite ClientAlive enabled
https://bugzilla.mindrot.org/show_bug.cgi?id=2572
Bug ID: 2572
Summary: dead sessions aren't closed despite ClientAlive
enabled
Product: Portable OpenSSH
Version: 3.7.1p2
Hardware: All
OS: Linux
Status: NEW
Severity: major
Priority: P5
Component: sshd
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
2002 Jul 24
1
Win2k, Samba 2.2.5 and LDAP
I can't get a Win2k computer to execute a login script. Also, on both the XP
computer and the w2k computer I get this message in their log file
[2002/07/24 13:27:17, 0] rpc_server/srv_netlog_nt.c:get_md4pw(188)
get_md4pw: Workstation sales1$: no account in domain
sales1 is the XP computer, but I get the exact same error for win2k. Both
computers (appear) to log on to the domain (as in, I
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
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
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
2005 Mar 24
2
Samba 3.0.12 (gid of user [joe] doesn't exist) Weird error when Client logs on.
Hi,
I just recently purchased a new server and took this opportunity to
upgrade to the latest version of samba (3.0.12). Unfortunatly, I have
some weird occurances. I have a user called "joe" who is my admin
user.
In /etc/passwd I have this:
joe:x:500:500:Joe:/home/joe:/bin/bash
In /etc/group I have this:
admin:x:500:joe
id returns correctly:
uid=500(joe) gid=500(admin)
2004 Jul 10
0
Root users shell
> Message: 1
> Date: Fri, 9 Jul 2004 09:55:40 -0700 (PDT)
> From: Roger Marquis <marquis@roble.com>
> Subject: Re: Root users shell == no existant shell /bin/bash
> To: freebsd-security@freebsd.org
> Message-ID: <20040709165540.2799D2C1CC@mx5.roble.com>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> "Peter C. Lai" wrote:
> > as a rule of thumb,