Re: [Samba] One user getting: Primary group is 0 and contains 0 supplementary groups on standalone server
On 10/11/2013 11:36 AM, Stuart Reedy wrote: Greetings, We are having some rights issues on Samba 3.6.18 running on Slackware64 14.0 (the official Slackware Package). One of our users is having access issues and I believe I have traced the problem to the following entry in the log.smbd: Primary group is 0 and contains 0 supplementary groups Issuing the groups command for this user returns the 8 Linux groups in which the user has membership. In researching this, I found another reference to this log entry for which the solution had to do with Windows groups and their relationship to local groups. Since we are using Samba stand-alone, we do not create any Windows groups and use local Linux groups for privileges. (I'm assuming Samba can still be used this way.) My question is: How does Samba calculate these group memberships? I'll look through the source code and see what I can see, but I am no programming wizard, so I doubt I'll find what I need there. Thanks! Stu... OK, I found where Samba gets the Linux group information created a C program that uses the same function (getgroups). Of course, this returns the correct groups for the user for which Samba claims: Primary group is 0 and contains 0 supplementary groups Also, the id command returns the Linux groups as expected: uid=6032(REDACTED) gid=6000(REDACTED) groups=6000(REDACTED),6001(REDACTED),6007(REDACTED),6009(REDACTED),6010(REDACTED),6011(REDACTED),6012(REDACTED),6013(REDACTED),6014(REDACTED) I'm a a loss as to why this user is not getting the proper rights from Samba. Any ideas? -- Stuart Reedy Working hard for a great university! s...@coe.uky.edu 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] One user getting: Primary group is 0 and contains 0 supplementary groups on standalone server
Greetings, We are having some rights issues on Samba 3.6.18 running on Slackware64 14.0 (the official Slackware Package). One of our users is having access issues and I believe I have traced the problem to the following entry in the log.smbd: Primary group is 0 and contains 0 supplementary groups Issuing the groups command for this user returns the 8 Linux groups in which the user has membership. In researching this, I found another reference to this log entry for which the solution had to do with Windows groups and their relationship to local groups. Since we are using Samba stand-alone, we do not create any Windows groups and use local Linux groups for privileges. (I'm assuming Samba can still be used this way.) My question is: How does Samba calculate these group memberships? I'll look through the source code and see what I can see, but I am no programming wizard, so I doubt I'll find what I need there. Thanks! Stu... -- Stuart Reedy Working hard for a great university! s...@coe.uky.edu 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Rights Issues - one user getting: Primary group is 0 and contains 0 supplementary groups on standalone server
Greetings, We are having some rights issues on Samba 3.6.18 running on Slackware64 14.0 (the official Slackware Package). One of our users is having access issues and I believe I have traced the problem to the following entry in the log.smbd: Primary group is 0 and contains 0 supplementary groups Issuing the groups command for this user returns the 8 Linux groups in which the user has membership. In researching this, I found another reference to this log entry for which the solution had to do with Windows groups and their relationship to local groups. Since we are using Samba stand-alone, we do not create any Windows groups and use local Linux groups for privileges. (I'm assuming Samba can still be used this way.) My question is: How does Samba calculate these group memberships? I'll look through the source code and see what I can see, but I am no programming wizard, so I doubt I'll find what I need there. Thanks! Stu... P.S. My apologies if this gets posted to the list twice: I accidentally tried sending it *before* I subscribed again. Oops! -- Stuart Reedy Working hard for a great university! s...@coe.uky.edu 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Mac OS 10.5 seems to change permissions on files
Greetings, We have an issue using Mac OS 10.5 with our Samba shares connected via cifs://server/Sharename. From what I can tell, when the Mac writes a file the permissions are correct (0660). Then it seems to change the permission to 0644, defeating the whole point of shared files. Has anyone else encountered this and, perhaps, found a work-around? Server Info: Samba 3.0.33 (Slackware package) Slackware 11.0 smb.conf: [global] workgroup = WG server string = Samba Server interfaces = x.x.x.x/16 passwd program = /usr/bin/passwd %u unix password sync = Yes ldap ssl = no hosts allow = x.x., 127.0.0.1 ea support = Yes veto files = /.DS_Store/._.*/DesktopFolderDB/Network Trash Folder/resource.frk/TheFindByContentFolder/TheVolumeSettingsFolder/ delete veto files = true --==SNIP==-- [Sharename] path = /path/ShareName valid users = @somegroup write list = @somegroup read only = No create mask = 0660 directory mask = 0770 force create mode = 0660 force directory mode = 0770 Any assistance is greatly appreciated! Stu... -- Stuart Reedy Working hard for a great university! s...@coe.uky.edu 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Mac OS 10.5 seems to change permissions on files (fixed!)
Brian Gregorcy wrote: Add this to the global section: unix extensions = no Stuart Reedy wrote: Greetings, We have an issue using Mac OS 10.5 with our Samba shares connected via cifs://server/Sharename. From what I can tell, when the Mac writes a file the permissions are correct (0660). Then it seems to change the permission to 0644, defeating the whole point of shared files. Has anyone else encountered this and, perhaps, found a work-around? Server Info: Samba 3.0.33 (Slackware package) Slackware 11.0 smb.conf: [global] workgroup = WG server string = Samba Server interfaces = x.x.x.x/16 passwd program = /usr/bin/passwd %u unix password sync = Yes ldap ssl = no hosts allow = x.x., 127.0.0.1 ea support = Yes veto files = /.DS_Store/._.*/DesktopFolderDB/Network Trash Folder/resource.frk/TheFindByContentFolder/TheVolumeSettingsFolder/ delete veto files = true --==SNIP==-- [Sharename] path = /path/ShareName valid users = @somegroup write list = @somegroup read only = No create mask = 0660 directory mask = 0770 force create mode = 0660 force directory mode = 0770 Any assistance is greatly appreciated! Stu... Setting unix extension = no fixed the permissions problem. Thanks! Stu... -- Stuart Reedy Working hard for a great university! s...@coe.uky.edu 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Still no joy using print command with 3.0.30
The saga continues: I still can't get Samba 3.0.30 to use the print command I did a clean install of Slackware 11, then compiled Samba 3.0.30 from source using: ./configure make make install I set up a printer, replaced lp with a script that writes its command line to a file, and set: print command = lp -H hold -d %p %s Printing from a Windows XP machine using \\hostname\printername prints the job via CUPS, bypassing the print command. When I issue the print command from a shell on the Linux Samba server, the command line is written to the file (as expected). I am completely baffled. Is there any help out there? Happy Friday Eve! Stu... Stuart Reedy wrote: Greetings once again, I am still having trouble with the print command option in 3.0.30. In our computer lab, we force CUPS to print the jobs on hold, using: print command = lp -H hold -d %p %s This worked well with the Slackware packages of Samba 3.0.28 and CUPS 1.1.23. When I upgraded Samba to 3.0.30, the jobs were no longer queued on hold, but printed immediately. To troubleshoot the problem, I wrote a script that copies the command line to a file, then replaced lp with this script. With 3.0.28 the script writes its output to the file and the job never prints. With 3.0.30 there is no output from the script and CUPS prints the job. In an effort be a good citizen, I removed the Slackware distribution of Samba, then compiled it from source, using: ./configure --enable-cups --enable-static=no --enable-shared=yes --with-fhs --with-acl-support=yes --with-automount --prefix=/usr --localstatedir=/var --bindir=/usr/bin --sbindir=/usr/sbin --with-lockdir=/var/cache/samba --sysconfdir=/etc --with-configdir=/etc/samba --with-privatedir=/etc/samba/private --with-swatdir=/usr/share/swat --with-smbmount --with-quotas --with-syslog --with-utmp --with-libsmbclient --with-winbind Still no joy. CUPS immediately prints jobs and the specified print command seems to be ignored. I would greatly appreciate any help that folks may wish to offer. == Here are the details, in case they are important: Slackware 11.0 using Linux kernel 2.4.34.5. CUPS is the Slackware package of 1.1.23. /etc/samba/smb.conf looks like: [global] workgroup = ITC server string = Samba Server passwd program = /usr/bin/passwd %u unix password sync = Yes ldap ssl = no hosts allow = 172.20., 127.0.0.1 ea support = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [test] path = /var/spool/samba read only = No printable = Yes print command = lp -H hold -d %p %s printer name = test oplocks = No share modes = No = -- Stuart Reedy Working hard for a great university! [EMAIL PROTECTED] 859 257-7966 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Still no joy using print command with 3.0.30
Thanks to Volker Lendecke for providing a fix for my issue. The answer is: ./configure --enable-cups=no ... Happy Friday Eve (or whatever the proper day is for your TZ)! Stu... Stuart Reedy wrote: The saga continues: I still can't get Samba 3.0.30 to use the print command I did a clean install of Slackware 11, then compiled Samba 3.0.30 from source using: ./configure make make install I set up a printer, replaced lp with a script that writes its command line to a file, and set: print command = lp -H hold -d %p %s Printing from a Windows XP machine using \\hostname\printername prints the job via CUPS, bypassing the print command. When I issue the print command from a shell on the Linux Samba server, the command line is written to the file (as expected). I am completely baffled. Is there any help out there? Happy Friday Eve! Stu... Stuart Reedy wrote: Greetings once again, I am still having trouble with the print command option in 3.0.30. In our computer lab, we force CUPS to print the jobs on hold, using: print command = lp -H hold -d %p %s This worked well with the Slackware packages of Samba 3.0.28 and CUPS 1.1.23. When I upgraded Samba to 3.0.30, the jobs were no longer queued on hold, but printed immediately. To troubleshoot the problem, I wrote a script that copies the command line to a file, then replaced lp with this script. With 3.0.28 the script writes its output to the file and the job never prints. With 3.0.30 there is no output from the script and CUPS prints the job. In an effort be a good citizen, I removed the Slackware distribution of Samba, then compiled it from source, using: ./configure --enable-cups --enable-static=no --enable-shared=yes --with-fhs --with-acl-support=yes --with-automount --prefix=/usr --localstatedir=/var --bindir=/usr/bin --sbindir=/usr/sbin --with-lockdir=/var/cache/samba --sysconfdir=/etc --with-configdir=/etc/samba --with-privatedir=/etc/samba/private --with-swatdir=/usr/share/swat --with-smbmount --with-quotas --with-syslog --with-utmp --with-libsmbclient --with-winbind Still no joy. CUPS immediately prints jobs and the specified print command seems to be ignored. I would greatly appreciate any help that folks may wish to offer. == Here are the details, in case they are important: Slackware 11.0 using Linux kernel 2.4.34.5. CUPS is the Slackware package of 1.1.23. /etc/samba/smb.conf looks like: [global] workgroup = ITC server string = Samba Server passwd program = /usr/bin/passwd %u unix password sync = Yes ldap ssl = no hosts allow = 172.20., 127.0.0.1 ea support = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [test] path = /var/spool/samba read only = No printable = Yes print command = lp -H hold -d %p %s printer name = test oplocks = No share modes = No = -- Stuart Reedy Working hard for a great university! [EMAIL PROTECTED] 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Still no joy using print command with 3.0.30
Greetings once again, I am still having trouble with the print command option in 3.0.30. In our computer lab, we force CUPS to print the jobs on hold, using: print command = lp -H hold -d %p %s This worked well with the Slackware packages of Samba 3.0.28 and CUPS 1.1.23. When I upgraded Samba to 3.0.30, the jobs were no longer queued on hold, but printed immediately. To troubleshoot the problem, I wrote a script that copies the command line to a file, then replaced lp with this script. With 3.0.28 the script writes its output to the file and the job never prints. With 3.0.30 there is no output from the script and CUPS prints the job. In an effort be a good citizen, I removed the Slackware distribution of Samba, then compiled it from source, using: ./configure --enable-cups --enable-static=no --enable-shared=yes --with-fhs --with-acl-support=yes --with-automount --prefix=/usr --localstatedir=/var --bindir=/usr/bin --sbindir=/usr/sbin --with-lockdir=/var/cache/samba --sysconfdir=/etc --with-configdir=/etc/samba --with-privatedir=/etc/samba/private --with-swatdir=/usr/share/swat --with-smbmount --with-quotas --with-syslog --with-utmp --with-libsmbclient --with-winbind Still no joy. CUPS immediately prints jobs and the specified print command seems to be ignored. I would greatly appreciate any help that folks may wish to offer. == Here are the details, in case they are important: Slackware 11.0 using Linux kernel 2.4.34.5. CUPS is the Slackware package of 1.1.23. /etc/samba/smb.conf looks like: [global] workgroup = ITC server string = Samba Server passwd program = /usr/bin/passwd %u unix password sync = Yes ldap ssl = no hosts allow = 172.20., 127.0.0.1 ea support = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [test] path = /var/spool/samba read only = No printable = Yes print command = lp -H hold -d %p %s printer name = test oplocks = No share modes = No = -- Stuart Reedy Working hard for a great university! [EMAIL PROTECTED] 859 257-7966 http://www.coe.uky.edu/~stu/ -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Print Command not working in 3.0.30
Greetings, I'm having trouble with the print command setting in Samba 3.0.30. From what I can tell, the commands defined in the print command setting are never executed. Jobs sent the printers are process by CUPS, bypassing the defined print command. When the command: lp -H hold -d %p %s did not work, I created a script that copied the command line used to a file and replace lp in the above setting with my script. The script was never executed. (Jobs were sent directly to CUPS.) I've tried this both with the Slackware Packages of 3.0.30 and with Samba compiled from source. Am I missing something or might this be a bug? Thanks! Stu... -- Stuart Reedy Working hard for a great university! [EMAIL PROTECTED] 859 257-7966 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
