Andrew, I dug into it a bit and managed to steal the few relevant lines of code
from 2.2.8a status.c and replace the ones in 3.0.5 to make my own smbstatus.
Now it works perfectly for me displaying any forced users and groups just like
it did in Samba 2.x.
I still don't really get why you took t
At 07:54 AM 7/31/04, Andrew Bartlett wrote:
The problem is, that information is not valid, except in
'security=share' and 'force user' cases. In all other cases, the user
that connects to the share is not necessarily connected to the user
actually accessing the share.
Thankyou very much for respon
On Sat, 2004-07-31 at 01:05, Tom Schaefer wrote:
> I use a lot of "force user" and "force group" directives on various
> shares. With smbstatus of Samba 2 I could always verify with a glance
> what uid and gid a particular service is being accessed as, with Samba 3
> you can't. I'd REALLY like to
I use a lot of "force user" and "force group" directives on various
shares. With smbstatus of Samba 2 I could always verify with a glance
what uid and gid a particular service is being accessed as, with Samba 3
you can't. I'd REALLY like to see that come back to smbstatus.
Here's a real world ex
