in reply to Re: Re: How do I make two users have the same privileges?
in thread How do I make two users have the same privileges?

I don't believe a killall -HUP init will do anything at all to Samba. All that does is tell init to re-read /etc/inittab and make the appropriate adjustments. You probably want to HUP smbd.

In addition, make sure that the files are writable by the group. Actually, if you're forcing Samba and Apache to run as the same user, I can't imagine any reason why it would be a permissions issue at that point. Verify they are indeed running as that user (via 'ps' output for example). If that isn't it, it's gotta be some additional Samba configuration item or something.

  • Comment on Re: Re: Re: How do I make two users have the same privileges?

Replies are listed 'Best First'.
Re: Re: Re: Re: How do I make two users have the same privileges?
by Reaped: Answer: Vroom testing some more (Initiate) on Dec 15, 2000 at 21:42 UTC
    You're right---it apparently wasn't doing anything. But Samba is supposed to re-initialize from smb.conf every 60 seconds, or so I thought ...

    Anyway, I did a HUP on smbd and all of a sudden my changes showed up. I retained two of the changes to the smb.conf file, I'm not sure which ultimately worked or whether it was a combination thereof:

    • I added smbusers and a username map line to smb.conf as described earlier.
    • I added guest account = apache, and guest ok = yes to the share definition.

    Also, I had earlier set the umask at wardk's and your suggestion for both apache and the Samba user as well as setgid on the apache document root where the share is located.

    Thanks to all for your help!

      ACK! This may make those files available to anyone! Somehow I don't think you want to do that. Check out the read users and write users options for smb.conf. ('man 5 smb.conf' should turn up a bunch of information on what all the options are and what they do).

      If you are still having problems, email me and I'll show you my smb.conf and how it works.

        Yeah, I know, but only to anyone on the network here. Access to the network this server is on is restricted. Turns out, the only people on the network are people I want to be allowed to behave like apache, so it should be ok, right? But I agree that this wouldn't be the best solution if there were Win network users you didn't want snooping around as apache. Maybe just changing the umask and establishing an smbusers file would work better for that, without adding guest priviledges.