Thanks a lot,
utmp = no successfully kill the logout users.
J. Bakshi wrote:
Ryan Novosielski wrote:
J. Bakshi wrote:
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at
J. Bakshi wrote:
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at all. Authentication works with no hitch. But
samba users stay at the system. I have just checked with who and found
there are 250
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at all. Authentication works with no hitch. But
samba users stay at the system. I have just checked with who and found
there are 250 samba users from 1st of
On Mon, 2009-03-02 at 13:52 +0530, J. Bakshi wrote:
Here is a very strange problem !!!
This is normal, there is no logoff operation. Disable utmp support by
setting utmp = no in the global section of your smb.conf
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
J. Bakshi wrote:
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at all. Authentication works with no hitch. But
samba users stay at the system. I have
Ryan Novosielski wrote:
J. Bakshi wrote:
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at all. Authentication works with no hitch. But
samba users stay at the system. I have just checked with
Dear list,
Here is a very strange problem !!!
I am using samba-3.0.25b-1.1.cc in clarkconnect server. No problem to
use the samba shares at all. Authentication works with no hitch. But
samba users stay at the system. I have just checked with who and found
there are 250 samba users from 1st of
