werner maes werner.maes at cc.kuleuven.ac.be
Tue Aug 8 07:17:49 GMT 2000

But why does it sometimes work when you do "commit changes".
For example, when you change invalid users from empty to @class and
do "commit changes", you don't have to restart samba. But when you erase
this value, you need to restart samba.
That's not very logic in my opinion.


KYT wrote:

> I am not from the Samba team, however, If I am not wrong, when you "commit
> changes" you have commit to change the configuration files (smb.conf). You
> will still need to restart samba to APPLY the changes, this is where
> restarting of smb daemon comes in. :-)
> Don't think this is classified as a bug. (Normally I will do a
> samba -restart)
> Werner Maes wrote in message <398EE12C.68C66EC5 at cc.kuleuven.ac.be>...
> >Hello,
> >
> >I think (in fact I'm quite sure) I have found the following bug in Swat.
> >
> >In my configuration I use the global option "invalid users=@class".
> >When I set this option using SWAT, all works fine after "commit
> >changes".
> >Users who belong to the "class" group cannot access the server.
> >
> >But when I erase this value using SWAT and do "commit changes",
> >everything
> ---snipped---

More information about the samba mailing list