On 1/26/06, Josh Kelley [EMAIL PROTECTED] wrote:
The following (or something like it) was suggested earlier on the list
by Jerry Carter:
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
Thanks, this worked, no more errors!
--
To unsubscribe
I'm running Samba 3.0.21a (blastwave build) on Solaris 9. The Solaris
servers have no printers attached or accessible, just file service. Samba
users authenticate off a Win2003 AD controller and get printing from that.
I got rid of the Unable to connect to CUPS Server errors by adding to
smb.conf
On 1/26/06, Elizabeth Schwartz [EMAIL PROTECTED] wrote:
I got rid of the Unable to connect to CUPS Server errors by adding to
smb.conf the line
printing=bsd
but I am still getting
smbd[4809]: [ID 702911 daemon.error] Unable to open printcap file
/etc/printcap for read!
Is there a way
First, I'm a UNIX administrator with some knowledge of Active Directory. I
have been debating to send this for a while since I probably don't have
the experience. I have purchased and read the Official Samba -3 guide.
I have previously setup Samba 2.2.8a on Solaris with SECURITY = DOMAIN to
Hi,
New to Samba this list, so please forgive if I make a faux pas.
I've got a Redhat 7.3 box with Samba, 2 Win stations, called ws1 ws2.
When either station creates files on the server, all the files get created with
permissions of rw-r--r-- (644). How do I get them created with 777?
ws1
Glen,
Add:
force create mode = 0777
force directory mode = 0777
to the config file. That is a sure
way to accomplish your goal.
You could change the default
umask for bash in /etc/bashrc,
but this may or may not affect
the default umask of Samba
created files. You could try it
On Thu, 2003-02-06 at 16:32, Glen Overman wrote:
Hi,
New to Samba this list, so please forgive if I make a faux pas.
I've got a Redhat 7.3 box with Samba, 2 Win stations, called ws1 ws2.
When either station creates files on the server, all the files get created with
permissions of
