SAMBA for OpenVMS
Tony Naidoo
tony.naidoo at colesmyer.com.au
Wed Feb 16 01:24:28 GMT 2005
Folks
I would appreciate your help...
I need to configure the SMB.CONF file to allow some PC's to look at
some directories on our VMS system
The PC's use DHCP for IP address(s), therefore its not static
The VMS Server is a name ( ie: HOCD07 )
I have installed SAMBA and want to allow some PC users access to
the following directorie
DISK$RISPAK001:[RIS.MAR.DG1.IN] and
DISK$RISPAK001:[RIS.MAR.DG1.OUT].
I am having difficulties understanding the configuration file...
This the contents of the LOG.SMB
[2005/02/15 09:53:47, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.VMS]VMS_SUP.C;134:(561)
vms_mkdir: /samba_root/private/, mode: 0000700
[2005/02/15 09:53:50, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(155)
Failed to set socket option SO_KEEPALIVE
[2005/02/15 09:53:50, 0]
DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]UTIL_SOCK.C;6:(155)
Failed to set socket option TCP_NODELAY
[2005/02/15 09:53:51, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:53:59, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:06, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:12, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:18, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:24, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:29, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:54:35, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
WARNING: no chroot!
[2005/02/15 09:55:53, 1] DSA1:[KITS.SAMBA-2_0_3.SOURCE.LIB]SYSTEM.C;1:(362)
This is the contents of the SMB.CONF File
; Configuration file for smbd.
; Template for VMS
;
============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.
;
; Things you need to check:
; --------------------------
;
; 1: Check the path to your printcap file. If you are using a system that
does
; not use printcap (eg., Solaris), create a file containing lines of the
; form
;
; printername|printername|printername|
;
; where each "printername" is the name of a printer you want to provide
; access to. Then alter the "printcap =" entry to point to the new file.
;
; If using Solaris, the following command will generate a suitable
printcap
; Configuration file for smbd.
; Template for VMS
;
============================================================================
; For the format of this file and comprehensive descriptions of all the
; configuration option, please refer to the man page for smb.conf(5).
;
; The following configuration should suit most systems for basic usage and
; initial testing. It gives all clients access to their home directories and
; allows access to all printers specified in /etc/printcap.
;
; Things you need to check:
; --------------------------
;
; 1: Check the path to your printcap file. If you are using a system that
does
; not use printcap (eg., Solaris), create a file containing lines of the
; form
;
; printername|printername|printername|
;
; where each "printername" is the name of a printer you want to provide
; access to. Then alter the "printcap =" entry to point to the new file.
;
; If using Solaris, the following command will generate a suitable
printcap
; file:
;
; lpc status | grep ":" | sed s/:/\|/ > myprintcap
;
; 2: Make sure the "print command" entry is correct for your system. This
; command should submit a file (represented by %s) to a printer
; (represented by %p) for printing and should REMOVE the file after
; printing.
;
; One most systems the default will be OK, as long as you get "printing
="
; right.
;
; It is also a good idea to use an absolute path in the print command
; as there is no guarantee the search path will be set correctly.
;
; 3: Make sure the "printing =" option is set correctly for your system.
; Possible values are "sysv", "bsd" or "aix".
;
; 4: Make sure the "lpq command" entry is correct for your system. The
default
; may not work for you.
;
; 5: Make sure that the user specified in "guest account" exists. Typically
; this will be a user that cannot log in and has minimal privileges.
; Often the "nobody" account doesn't work (very system dependant).
;
; 6: You should consider the "security =" option. See a full description
; in the main documentation and the smb.conf(5) manual page
;
; 7: Look at the "hosts allow" option, unless you want everyone on the
internet
; to be able to access your files.
;
[global]
workgroup = VMS_SAMBA_SERVICES
dead time = 10
map archive = no
printing = bsd
printcap name = /sys$manager/ucx$printcap.dat
load printers = yes
status = yes
print command = print %f/queue=%p/delete/passall/name="""""%s"""""
lprm command = delete/entry=%j
security = user
default service = default
create mode = 0777
guest account = PCFS$ACCOUNT
; This next option sets a separate log file for each client. Remove
; it if you want a combined log file.
log file = /samba_log/log.%m
; read raw = no
read prediction = yes
socket options = TCP_NODELAY
; socket options = SO_REUSEADDR
; You will need a world readable lock directory and "share modes=yes"
; if you want to support the file sharing modes for multiple users
; of the same files
; lock directory = /usr/local/samba/var/locks
share modes = no
[homes]
[homes]
comment = Homes
path = %H
username = %S
valid users = %S
only user = Yes
wide links = No
follow symlinks = No
invalid users = root
;
; comment = Home Directories
; browseable = no
; read only = no
; create mode = 0750
;
[printers]
comment = All Printers
path = /dsa1/pcfs_spool/default
browseable = no
printable = yes
; public = no
public = yes
writable = no
create mode = 0700
; you might also want this one
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
;
; Other examples.
;
; A private printer, usable only by fred. Spool data will be placed in
fred's
; home directory. Note that fred must have write access to the spool
directory,
; wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
;
; A private directory, usable only by fred. Note that fred requires write
; access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
;
; A publicly accessible directory, but read only, except for people in
; the staff group
;[public]
; comment = Public Stuff
path = drb1/ris/mar/dg1/in
public = yes
writable = no
printable = no
write list = @staff
;
; a service which has a different directory for each machine that connects
; this allows you to tailor configurations to incoming machines. You could
; also use the %u option to tailor it by user name.
; The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
path = drb1/ris/mar/dg1/out/%m
public = yes
writeable = yes
;
;
; A publicly accessible directory, read/write to all users. Note that all
files
; created in the directory by users will be owned by the default user, so
; any user with access can delete any other user's files. Obviously this
; directory must be writable by the default user. Another user could of
course
; be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
;
;
; The following two entries demonstrate how to share a directory so that two
; users can place files there that will be owned by the specific users. In
this
; setup, the directory should be writable by both users and should have the
; sticky bit set on it to prevent abuse. Obviously this could be extended to
; as many users as required.
;[myshare]
comment = RIS EAI files
path = dr1b/ris/mar/dg1/out
valid users = %s
public = yes
writable = yes
printable = no
create mask = 0765
Hocd
Tony Naidoo
VMS Systems , Infrastructure Services and Operations
Level 4 236 Bourke Street (Target Center), Melbourne CBD
Phone: (03) 9635-1069
Mobile: 0417 540 385
Tony Naidoo
VMS Systems , Infrastructure Services and Operations
Level 4 236 Bourke Street (Target Center), Melbourne CBD
Phone: (03) 9635-1069
Mobile: 0417 540 385
This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify the sender and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses. No warranty is made that this material is free from computer virus or any other defect or error. Any loss/damage incurred by using this material is not the sender's responsibility. The sender's entire liability will be limited to resupplying the material.
More information about the samba-vms
mailing list