If you log on as a known user, the user gets an entry as an active user via smbstatus and via utmp, if you have it enabled. Users who are mapped to guest via the map to guest = smb.conf parameter do not show up at all in either smbstatus or in utmp logging if configured. Here is what I see when a user who got mapped to guest logs on: sh-2.04# smbstatus creating lame upcase table creating lame lowcase table Samba version 3.0.5 PID Username Group Machine ------------------------------------------------------------------- Service pid machine Connected at ------------------------------------------------------- SHARE1 31054 thunderbird Thu Aug 19 08:49:48 2004 No locked files Notice that an entry shows up in the Service section, but not in the user accounting section. We should be placing the guest user in the user accounting section when a user is mapped to guest. Now here is the normal behaivor when a known user logs on: sh-2.04# smbstatus creating lame upcase table creating lame lowcase table Samba version 3.0.5 PID Username Group Machine ------------------------------------------------------------------- 31354 admin AllLocalUsers thunderbird (10.33.0.215) Service pid machine Connected at ------------------------------------------------------- SHARE1 31354 thunderbird Thu Aug 19 08:52:06 2004 No locked files
originally against 3.0.6rc2
still present in 3.0.11 and 3.0.20pre1...
simple... in sources/smbd/session.c sesion_claim() /* don't register sessions for the guest user - its just too expensive to go through pam session code for browsing etc */ if (vuser->guest) { return True; } I think this should be discussed... I thought that smbstatus was a safe source to find information about processes, shares and locks. But if sessions are not register for guest... this is not a safe source of information...
current behavior is by design. If you would like to discuss changing it, please post to the samba-technical mailing list.