Pourquoi Samba ne me laisse-t-il pas supprimer un fichier

10

Je ne suis pas un expert de Linux - je dirais 6 sur une échelle de 1-10

Je viens de configurer Samba sur mon serveur Linux Ubuntu (pas d'interface graphique, cli uniquement). J'ai créé le compte smb et connecté à partir de mon mac et monté mon répertoire personnel pour la plupart, cela fonctionne bien.

J'ai fait le test normal, touchez un fichier puis supprimez-le. Étrangement, j'ai pu créer le fichier correctement mais je n'ai pas pu le supprimer.

J'ai parcouru le Web et j'ai vu ce problème beaucoup - la plupart des réponses étaient liées aux paramètres d'autorisation dans le fichier smb.conf. J'ai joué avec ça mais je ne pense pas que ce soit le problème. Depuis mon Mac, je peux même chmoder les paramètres à 777 (et j'ai vérifié sur le serveur Linux pour voir que le chmod a pris, il l'a fait), et je peux modifier le fichier que j'ai créé, mais je ne peux pas le supprimer.

Je suis assez confus, je me demande si cela pourrait avoir quelque chose à voir avec la samba elle-même n'ayant pas d'autorisations, mais c'est au-delà de ce que je sais comment vérifier.

Éditer:

Je suis toujours curieux à ce sujet - pour la plupart, je viens de passer à sshfs, ce qui est assez génial et m'a pris 3 minutes et aucune pensée alors que je travaillais des heures avec smb & nfs.


[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP
netbios name = hp

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan  for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

Bill K
la source

Réponses:

2

Your samba service obviously has write access to the root directory you're creating, otherwise it wouldn't be able to create files either.

It's more likely that your samba config is set to not allow deleting/unlinking.

Can you test to see if you can create and delete a file in a sub folder?

Martin Owens -doctormo-
la source
I did try this when initially setting up the server--deleting a directory did not work either. Editing using vi worked but it complained a lot--I think this had something to do with the inability to delete temp files.
Bill K
1
Are you using the tmp directory? that has the sticky bit set which would give you the results your experiencing.
Martin Owens -doctormo-
Don't forget to update your question with the new information you've posted to me here. So others when they find your question will have more to work with.
Martin Owens -doctormo-
@MartinOwens-doctormo- Thanks for the tip about the sticky bit! This was causing my problems as well. Removing the sticky bit fixed this problem for me.
Nathan Wallace