On Tue, 2004-02-24 at 10:07, Daniel Meyer wrote: > Henrik Nordstrom wrote: > > > Also verify that you have given Squid access to the Samba privileged pipe. > > This is normally only accessible by root. You should see some warnings in > > cache.log or the Samba logs if this is the problem. > > Guess i am missing something here. > > on my system the pipe has the following permissions: > > proxy:/var/locks/winbindd_privileged # ls -alp > total 0 > drwxr-x--- 2 root root 72 Feb 24 10:52 ./ > drwxrwxrwx 4 root root 352 Feb 24 10:52 ../ > srwxrwxrwx 1 root root 0 Feb 24 10:52 pipe= > > If i try to change the permissions of the directory itself, so that > the squid user can access it, winbindd fails to start: > > proxy:/var/locks # winbindd -i > winbindd version 3.0.2 started. > Copyright The Samba Team 2000-2004 > Added domain whatever whatever.Lokal S-1-5-21-3284267766-540466896-523501128 > invalid permissions on socket directory /var/locks/winbindd_privileged > open_winbind_socket: No such file or directory > > Doesnt matter if i try to change owner/group, or just the rwx > permissions for owner/group/all... > > Where is my mistake? > > Danny Try
chgrp squid /var/locks/winbindd_privileged chmod 755 /var/locks/winbindd_privileged You're very close now btw... Mark -- "...the number of UNIX installations has grown to 10, with more expected..." - Dennis Ritchie and Ken Thompson, June 1972
