Vickie L. Kidder
2007-Dec-27 20:36 UTC
[Samba] printer admin option replacement on stand alone (not domain) print server running version 3.0.25
I'm trying to upload print drivers to a stand-alone samba server running version 3.0.25. The server is part of a workgroup (not domain). My log files show messages that it cannot update the driver. Before I had the printer admin option set in my smb.conf file to allow a non-root user to do the printer admin and everything worked fine. I have read the Samba How To Notes section on important changes since 3.x, it says the following. "Group mappings are essential only if the Samba server is running as a PDC/BDC. Stand-alone servers do not require these group mappings.". Can anyone help me to understand what I need to do to allow a non-root user to perform printer admin functions on a stand-alone server?
Ryan Novosielski
2007-Dec-27 21:01 UTC
[Samba] printer admin option replacement on stand alone (not domain) print server running version 3.0.25
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Since 3.0.11, privileges have been the way to assign print operator abilities. You need enable privileges = yes in your smb.conf (a funny anecdote -- this one bit me about a week ago and I went searching on Google; I found myself providing this very answer to someone two years ago). At any rate, I don't know that those work on workgroups and domains alike. You could probably find out in the manual, though. Vickie L. Kidder wrote:> I'm trying to upload print drivers to a stand-alone samba server running > version 3.0.25. > The server is part of a workgroup (not domain). > > My log files show messages that it cannot update the driver. > Before I had the printer admin option set in my smb.conf file to allow a > non-root user to do the printer admin and everything worked fine. > > I have read the Samba How To Notes section on important changes since 3.x, > it says the following. > "Group mappings are essential only if the Samba server is running as a > PDC/BDC. Stand-alone servers do not require these group mappings.". > > Can anyone help me to understand what I need to do to allow a non-root > user to perform printer admin functions on a stand-alone server? >- -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$&| |__| | | |__/ | \| _| |novosirj@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHdBJcmb+gadEcsb4RAowyAJ9ZC54wbPgrWtt/+8YF3wM9tH9/iwCfQDxd Pzqgd4by2EdK1zHmvC/aA7I=kUdl -----END PGP SIGNATURE-----
Possibly Parallel Threads
- Fw: printer admin option replacement on stand alone (not domain) print server running version 3.0.25
- 3.0.25 *breaks* stand alone server, 3.0.24 works fine
- Active Record w/ Stand Alone Script (no longer working?)
- module collections - stand alone puppet architecture
- stand alone winbind deamon services via apis