Me wrote:

> [example]
>   comment = access to apache account as mgr.apache
>   path = /APACHE
>   guest ok = no
>   write ok = yes
>   username = mgr.apache
>   only user = yes

This setup (in conjunction with PM to "tell" SMBD to
check against MPE passwords when mapping shares) results
in the SMBD process switching to the validated MPE user
when accessing files in the respective share (MGR.APACHE
in the above example). You should be able to verify this
with smbstatus (showing the share and associated logon).

The resulting file ownership and access rights will be
similar to what you have when logging on as MGR.APACHE
in a regular session and performing similar file access.

You should also not see the issue of "non SM user cannot
create files in an MPE group outside of his or her logon
account" with this type of setup.


> Oh, as far as I recall, you need to ALTUSER MGR.SAMBA;CAP=+PM to
> "tell" the SMBD job to actually attempt MPE password validation.

As others already mentioned... when using a Samba server
with plain text passwords (no encryption)... you need to
"tell" your PC client(s) to not refuse "talking" to that
server... by applying the respective RegEdit setting (and
rebooting the PC to activate it).

Regards, Lars.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *