Re: [Samba] Novice question - How to completely disable printing and /etc/printcap errors ?

2006-01-31 Thread Elizabeth Schwartz
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 from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Novice question - How to completely disable printing and /etc/printcap errors ?

2006-01-26 Thread Elizabeth Schwartz
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 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 to get rid of this error short of recompiling?  (it is nice
to be using the

thanks Betsy
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


Re: [Samba] Novice question - How to completely disable printing and /etc/printcap errors ?

2006-01-26 Thread Josh Kelley
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 to get rid of this error short of recompiling?  (it is nice
 to be using the

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

Josh Kelley
--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


[Samba] Novice Question

2004-03-09 Thread nuffers
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 
a NT style domain.  This works very well for us.  No password prompting 
and only allows UNIX users to get to the share.

We are know going to Active Directory in the near future. 

Do I need to upgrade to Samba 3 to keep this? 

To join the AD domain as a member, to I need to compile with AD added and 
set SECURITY=ADS ?  or can I still use SECURITY=DOMAIN without compiling 
with AD support? 

I have also had problems compiling with AD support.  Is there a 
precompiled version that I can grab?


Steve Nuffer
[EMAIL PROTECTED]
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba


[Samba] Novice question

2003-02-06 Thread Glen Overman
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  ws2 are both set up as entries in the /etc/passwd file  in the
samba password file, with umask 000 in their respective .bash_profile's.
root user also has umask 000.  The smb.conf attempts are shown below:

[homes]
   comment = Home Directories
   browseable = yes
   public = yes
   writable = yes
   create mode = 0777
;   valid users = %S
   directory mode = 0777
   read only = no
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user

Thanks for any help,  I'll go ahead  say Duh! right now.
Glen 
--
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



Re: [Samba] Novice question

2003-02-06 Thread Troy.A Johnson
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 
though. :-/

Troy

 Glen Overman [EMAIL PROTECTED] 02/06/03 03:32PM 
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  ws2 are both set up as entries in the /etc/passwd file  in the
samba password file, with umask 000 in their respective
.bash_profile's.
root user also has umask 000.  The smb.conf attempts are shown below:

[homes]
   comment = Home Directories
   browseable = yes
   public = yes
   writable = yes
   create mode = 0777
;   valid users = %S
   directory mode = 0777
   read only = no
# If you want users samba doesn't recognize to be mapped to a guest user
; map to guest = bad user

Thanks for any help,  I'll go ahead  say Duh! right now.
Glen 
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba
-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba



Re: [Samba] Novice question

2003-02-06 Thread Bradley W. Langhorst
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  rw-r--r-- (644).  How do I get them created with 777?
 ws1  ws2 are both set up as entries in the /etc/passwd file  in the
 samba password file, with umask 000 in their respective .bash_profile's.
 root user also has umask 000.  The smb.conf attempts are shown below:

are you looking for

force create mode (S)

This parameter specifies a set of UNIX mode bit permissions that
will always be set on a file created by Samba. This is done by
bitwise 'OR'ing these bits onto the mode bits of a file that is
being created or having its permissions changed. The default for
this parameter is (in octal) 000. The modes in this parameter
are bitwise 'OR'ed onto the file mode after the mask set in the
create mask parameter is applied.

See also the parameter create mask for details on masking mode
bits on files.

See also the inherit permissions parameter.

Default: force create mode = 000

Example: force create mode = 0755

would force all created files to have read and execute
permissions set for 'group' and 'other' as well as the
read/write/execute bits set for the 'user'.


-- 
Bradley W. Langhorst [EMAIL PROTECTED]

-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba