Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have samba running on RH 7.1.
I have configured one directory called /shared on the samba
server and there are 3 directorys below that. Directories 1 and
3 let me have full access to everything from a win2k client.
However directory 2 will not let me rename files. I can create
delete files and subdirectories. I can even rename subdirectories
I just can't rename files in the 2nd directory. I get a make sure file is not in use/access denied. I can't think of anything that would make this happen. I chown the directory /shared as well as chmod 777 (secerity is no issue). I don't know much more about samba to resolve this. When you LS at a console all rwx are there on the files in the 2nd directory. Any thoughts???
Thank you very much for any help on the subject.
Jamie
Samba.conf
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not many any basic syntactic errors.
#
#======================= Global Settings =====================================
[global]
path = /shared
force directory mode = 777
create mode = 777
printing = lprng
force create mode = 777
dns proxy = no
encrypt passwords = yes
null passwords = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
valid users = jamie
printcap name = /etc/printcap
force user = jamie
max log size = 0
writable = yes
directory mode = 777
security = user
ssl ca certfile = /usr/share/ssl/certs/ca-bundle.crt
server string = Samba Server
workgroup = WORKGROUP
delete readonly = yes
netbios name = lcars
log file = /var/log/samba/%m.log
load printers = yes
guest account = jamie
public = yes
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /home/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# 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
; 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 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 = /usr/pc/%m
; public = no
; writable = 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 = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
try adding "case sensitive = no" to the [shared] section. I had weird errors like that with some files because of that...
When you chown and chmod, make sure to use the -R option to recursively chown and chmod everything inside the /shared directory. Also use the -v option to see what's going on. Check the permissions too, make sure that "jamie" owns the directories and files.
As a test, try creating another (fourth) folder from Windoze in the shared area, and check it's perms/ownership, make sure it's not doing anything weird.
Thanks Sewer_monkey for the help.
I added the case sensitive line to the smb.conf file and restarted the service. I as well put the -R and -v on chown and mod and everything looked error free. It still won't let me rename (modify) files in the 2nd directory. I created a 4th and copied files into it and I could rename them just fine. Jamie is the owner listed on all directories and files.
I have found out a few interesting things about my rename problem. Directory 2 is where all mp3's are stored. When I rename the extention from mp3 to lets say doc I can rename the entire file. If I move a MP3 to directory 1 or 3 I get the same: "Make sure disk isn't full or write protected." when i rename. It appears to be the MP3 extention itself that is causing the error. I don't know what that problem would be, anyone have a clue?
I think I got it figured out. The problem I believe is ...of course win2k. I installed win2k on another machine and mapped the drive to the shared folder and I have full access to anything and everything. It is only from my current machine that I have this problem.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.