Re: [Samba] Access rights from ACLs not honored when setting file attributes?
Finally! Many thanks, that did it. The option 'store dos attributes' was not enabled. After I did enable it everything works as expected. I did just a little research on 3 servers here and this is the result: on samba 3.2.5 the problem dose not show up if 'store dos attributes' is disabled. However on samba 3.5.6 and 3.5.8 this option is definitely required for my setup. I must have missed somewhere between samba version 3.2.5 and 3.5.6 that this option became mandatory for my kind of setup, shame on me. You saved my weekend which starts right now! Felix On 01.06.2011 17:37, TAKAHASHI Motonobu wrote: From: "Felix Brack (Mailinglist)" Date: Wed, 01 Jun 2011 12:31:34 +0200 This is somewhat a reincarnation of a problem I am facing since upgrading to samba 3.5.6 (3.5.8 is identical). (snip) However using the windows function 'SetFileAttributes' fails in case the user who is connected to the samba server and executes the function is not either the owner of the file/directory or member of the owning group of the file/directory. Therefore it looks like samba is ignoring any ACL entry when using the windows function 'SetFileAttributes'. No matter if there is an ACE granting the proper access right, samba fails. Can you set file attributes with GUI and Is "store dos attributes" set? As far as I examined at Samba 3.5.6, I can manually set attributes. I accessed with user monyo to test2.doc whose ACL is set as below: - # getfacl test2.doc # file: test2.doc # owner: tako # group: root user::rw- group::rw- group:aclshare3ro:r-x group:aclshare3rw:rwx mask::rwx other::--- # id ika uid=2018(ika) gid=2030(ika) groups=2030(ika),2005(aclshare3rw) - My smb.conf is : [global] (nothing is defined) [aclshare3] path = /var/lib/samba/shares/aclshare3 writeable = yes force group = root inherit permissions = yes store dos attributes = yes map archive = no map read only = no --- TAKAHASHI Motonobu -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Access rights from ACLs not honored when setting file attributes?
This is somewhat a reincarnation of a problem I am facing since upgrading to samba 3.5.6 (3.5.8 is identical). I use samba on an ext3 ACL enabled file system. Typically a users access rights are determined by his or her membership in different groups. The access right is therefore defined and granted by/to the group, not the user. These groups then appear in the ACL of directories and files whereby the access is granted. This system works perfect when creating, modifying and delete files or directories - no issues at all. However using the windows function 'SetFileAttributes' fails in case the user who is connected to the samba server and executes the function is not either the owner of the file/directory or member of the owning group of the file/directory. Therefore it looks like samba is ignoring any ACL entry when using the windows function 'SetFileAttributes'. No matter if there is an ACE granting the proper access right, samba fails. Is there a principle difference in how samba interprets access rights depending on whom (user, primary group membership or ACL) grants them? Why do file/directory operations such as create/modify/delete work, no matter how the access right was granted (including from ACL)? regards Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't get 'dos filemode' to work as expected
On 24.03.2011 10:09, Felix Brack wrote:
Hello,
After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode'
does not seem to work anymore. If I (as a user) do not own the file I
can't change permissions.
I am user 'felix' and member of supplementary group 'Development'. To
test things I use the following share definition:
[Temp]
path = /srv/samba/file-shares/tmp
browseable = yes
read only = no
invalid users = root administrator
delete readonly = yes
inherit owner = yes
force group = Development
dos filemode = yes
A 'getfacl' on /srv/samba/file-shares/tmp returns:
# file: srv/samba/file-shares/tmp
# owner: root
# group: root
# flags: -s-
user::rwx
group::r-x
group:Development:rwx
mask::rwx
other::---
default:user::rwx
default:group::r-x
default:group:Development:rwx
default:mask::rwx
default:other::---
From the 'smb.conf' man page concerning option 'dos filemode':
...
Enabling this parameter allows a user who has write access to the file
(by whatever means, including an ACL permission) to modify the
permissions (including ACL) on it.
...
My understanding: as a member of group 'Development' I do have write
access to '/srv/samba/file-shares/tmp' by means of the ACL.
Trying to modify permissions on a directory or file I create in that
share does not work and reports access denied, no matter if I use
Windows Explorer or smbclient from an other linux box.
What am I misunderstanding here?
Many thanks, Felix
I finally manged to write some code for my Windows box that shows the error:
#include
#include
#include
// directory name --
// share name |
// server name | |
// | | |
// v v v
const wchar_t strFirName[]= L"JUPITER\\testshare\\test-dir";
int main(void)
{
BOOL bRet;
DWORD dwError;
// create the directory
bRet= CreateDirectory(strFirName, NULL);
if (bRet != TRUE) {
dwError= GetLastError();
return -1;
}
// now set the file attribute of the newly created directory
bRet= SetFileAttributes(strFirName, FILE_ATTRIBUTE_NORMAL);
if (bRet != TRUE) {
// dwError will be 6 (ERROR_INVALID_HANDLE) in case of failure
dwError= GetLastError();
return -1;
}
return 0;
}
That's it! Creating a directory and then manipulating the attributes.
The server path to the share is /srv/samba/file-shares/testshare.
The code above fails while setting the attribute if the user (felix)
connecting to the samba share is _not_ the owner (root) of
/srv/samba/file-shares/testshare.
'getfacl /srv/samba/file-shares/testshare' returns:
# file: srv/samba/file-shares/testshare
# owner: root
# group: root
# flags: -s-
user::rwx
group::rwx
group:Development:rwx
mask::rwx
other::---
default:user::rwx
default:group::rwx
default:group:Development:rwx
default:mask::rwx
default:other::---
If I type 'chown felix:root /srv/samba/file-shares/testshare' on the
samba server and then execute the code above, everything is fine.
'getfacl /srv/samba/file-shares/testshare' returns:
# file: srv/samba/file-shares/testshare
# owner: felix
# group: root
# flags: -s-
user::rwx
group::rwx
group:Development:rwx
mask::rwx
other::---
default:user::rwx
default:group::rwx
default:group:Development:rwx
default:mask::rwx
default:other::---
As already stated 'felix' is member of group 'Development'.
Can somebody confirm that the code above works in case the user
connecting to the share is _not_ owning the share?
Felix
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't get 'dos filemode' to work as expected
On 04.04.2011 18:25, Chris Smith wrote: On Mon, Apr 4, 2011 at 11:41 AM, Felix Brack wrote: # file: test-file # owner: root # group: root user::rwx group::rwx #effective:r-- group:Development:rwx #effective:r-- mask::r-- other::--- That's the same thing you would get if were logged into the system as root and created the file. So it is an ACL issue. # file: test-file # owner: root # group: root user::rwx group::rwx group:Development:rwx mask::rwx other::--- At least now , If I am member of supplementary group 'Development', I should have the same rights in directory 'test-directory' as if this was owned by me (felix), right? I would think so. I don't know entirely what you want to accompplish, but it may be better to: chgrp -R Development test-directory What I am trying to accomplish is pretty simple: assigning access rights to one ore more groups instead user(s). Therefore changing the group with chgrp to 'Development' is most definitely not what I want: what if there is more then one group? This is what ACLs are used for: giving additional groups and users special rights to access files. Moreover changing the group does not work, only changing the owner (I already tried that). This is in fact what the problem is all about. To put it simple: samba only seems to care about the _user_ connecting to the share and ignores any other rights for that user that might be assigned to him or her by means of group membership (normal or defined by ACLs). And eliminate: force group = Development invalid users = root administrator from the share. While adding: valid users = +Development (and any other groups you want have access) Eliminating 'force group' is not a good idea (for now) since it tells smbd that connections should be established using group 'Development'. It has nothing to do with access rights and I use it just as safety precaution to make sure my client does not get connect as member of group 'Domain Users'; if this would really happen I (or samba) could have serious problems accessing the share. The -s- flag will propagate new files and directories with the Development group. Basically a performance issue. See the section "Override controls" in: http://samba.org/samba/docs/man/Samba-Guide/kerberos.html#id2613307 Agreed. As soon as everything is working I will try to remove 'force group' and look if samba accesses the share with access rights defined for group 'Development' instead of group 'Domain Users'. Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't get 'dos filemode' to work as expected
On 04.04.2011 17:09, Chris Smith wrote: On Thu, Mar 24, 2011 at 5:09 AM, Felix Brack wrote: A 'getfacl' on /srv/samba/file-shares/tmp returns: # file: srv/samba/file-shares/tmp # owner: root # group: root # flags: -s- user::rwx group::r-x group:Development:rwx mask::rwx other::--- default:user::rwx default:group::r-x default:group:Development:rwx default:mask::rwx default:other::--- Are you sure this is a Samba issue? What does a 'getfacl' on the files you create in the share look like? I am not sure anymore that it is a samba problem. Perhaps my understand of how ACLs are supposed to work is entirely wrong. Anyway: creating a file 'test-file' and a directory 'test-directory' from a Windows XP client's Explorer creates this: # file: test-directory # owner: root # group: root # flags: -s- user::rwx group::r-x group:Development:rwx mask::rwx other::r-x default:user::rwx default:group::rwx default:group:Development:rwx default:mask::rwx default:other::--- # file: test-file # owner: root # group: root user::rwx group::rwx #effective:r-- group:Development:rwx #effective:r-- mask::r-- other::--- This is not what I wanted so I used the following two options on the share: force create mode = 0660 force directory mode = 0770 With this getfacl returns the following: # file: test-directory # owner: root # group: root # flags: -s- user::rwx group::rwx group:Development:rwx mask::rwx other::r-x default:user::rwx default:group::rwx default:group:Development:rwx default:mask::rwx default:other::--- # file: test-file # owner: root # group: root user::rwx group::rwx group:Development:rwx mask::rwx other::--- At least now , If I am member of supplementary group 'Development', I should have the same rights in directory 'test-directory' as if this was owned by me (felix), right? Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't get 'dos filemode' to work as expected
On 03.04.2011 17:24, TAKAHASHI Motonobu wrote:
From: Felix
Date: Wed, 30 Mar 2011 17:05:53 + (UTC)
On Fri, 25 Mar 2011 22:43:38 +0900, TAKAHASHI Motonobu wrote:
From: Felix Brack
Date: Thu, 24 Mar 2011 10:09:53 +0100
After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode'
does not seem to work anymore. If I (as a user) do not own the file I
can't change permissions.
(snip)
I just double checked but the problem remains: I can do things if the
share is owned by myself ('felix') but not if it is owned by 'root' if me
having access by being a member of supplementary group 'Development'.
Using debug level 3 on the samba server I found this:
(snip)
Please show the minimum set to reproduce for example smb.conf
including [global] section.
As I showed in my previous mail, in order to reproduce, I set the
empty [global] section.
And what is your platform? / The shared file path is located locally?
Sorry, forgot to answer this: yes, the shared file path is local.
Felix
---
TAKAHASHI Motonobu
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't get 'dos filemode' to work as expected
On 03.04.2011 17:24, TAKAHASHI Motonobu wrote:
> From: Felix
> Date: Wed, 30 Mar 2011 17:05:53 + (UTC)
>
>> On Fri, 25 Mar 2011 22:43:38 +0900, TAKAHASHI Motonobu wrote:
>>
>>> From: Felix Brack
>>> Date: Thu, 24 Mar 2011 10:09:53 +0100
>>>
>>>> After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode'
>>>> does not seem to work anymore. If I (as a user) do not own the file I
>>>> can't change permissions.
> (snip)
>> I just double checked but the problem remains: I can do things if the
>> share is owned by myself ('felix') but not if it is owned by 'root'
if me
>> having access by being a member of supplementary group 'Development'.
>>
>> Using debug level 3 on the samba server I found this:
> (snip)
>
> Please show the minimum set to reproduce for example smb.conf
> including [global] section.
>
My minimum set is not really small but all settings related to the role
of the server and to LDAP are irrelevant when it comes to the problem I
am investigating (at least I think they are irrelevant!?). Anyway, here
is my entire global:
[global]
### Naming, domain and browesing ###
workgroup = LTEC
netbios name = Jupiter
server string = TEST Samba %v server
domain master = yes
preferred master = yes
os level = 65
domain logons = yes
logon path = \\%L\Profiles\%U\%m\%a
logon drive = H:
### Interfaces to listen on ###
interfaces = eth0 127.0.0.0/8
bind interfaces only = true
### Logging configuration ###
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
log level = 3
### Authentication ###
passdb backend = ldapsam:ldap://localhost
ldap admin dn = "uid=srv-user,dc=ltec,dc=ch"
ldap delete dn = yes
ldap suffix = dc=ltec,dc=ch
ldap user suffix = ou=users
ldap group suffix = ou=groups
ldap machine suffix = ou=computers
ldap idmap suffix = ou=idmap
ldap ssl = off
ldap passwd sync = yes
obey pam restrictions = yes
### Users, groups and machines administration ###
add user script = /usr/sbin/smbldap-useradd -m "%u"
add group script = /usr/sbin/smbldap-groupadd -p "%g"
add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
add machine script = /usr/sbin/smbldap-useradd -w -i "%u"
delete user from group script = //usr/sbin/smbldap-groupmod -x
"%u" "%g"
delete user script = /usr/sbin/smbldap-userdel "%u"
delete group script = /usr/sbin/smbldap-groupdel "%g"
set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"
passwd program = /usr/sbin/smbldap-passwd -u %u
### Misc global options ###
wins support = yes
time server = yes
remote announce = 172.27.22.1
remote browse sync = 172.27.22.1
dns proxy = no
unix charset = 850
### Printing ###
load printers = no
disable spoolss = yes
printcap name = /dev/null
### Disable user shares
usershare max shares = 0
### Include the file-share definitions ###
include = /etc/samba/smbfs.conf
### !!! TESTING !!!
include = /etc/samba/smbfs-test.conf
The include file 'smbfs.conf' holds the share definitions in use. To
keep it simple for testing I created a new include file defining just
the one share on which I run all tests; this include file is called
'smbfs-test.conf' and contains the following:
[testshare]
comment = Only use this shre for samba testing !
path = /srv/samba/file-shares/testshare
browseable = yes
read only = no
invalid users = root administrator
delete readonly = yes
inherit owner = yes
force group = Development
dos filemode = yes
> As I showed in my previous mail, in order to reproduce, I set the
> empty [global] section.
>
I agree that it is best to have an empty [global] to track down such a
problem but as I am using LDAP that is not really possible. This is why
I posted my entire [global]. Do you see anything there that might
explain my problem?
By the why, 'id felix' returns the following:
uid=1000(felix) gid=513(Domain Users)
groups=1004(Management),1005(Development),1007(EETS),513(Domain Users)
which is exactly what I like it to be.
> And what is your platform? / The shared file path is located locally?
>
The server is a a 64Bit Debian GNU/Linux 6.0 (Sqeeze) with kernel
2.6.32. The entire server is a KVM guest. The KVM host is a multicore
XEON system providing a soft RAID-5 disk system for the guests.
Felix
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
[Samba] Can't get 'dos filemode' to work as expected
Hello, After an upgrade to samba 3.5.8 (from 3.2.5) the option 'dos filemode' does not seem to work anymore. If I (as a user) do not own the file I can't change permissions. I am user 'felix' and member of supplementary group 'Development'. To test things I use the following share definition: [Temp] path = /srv/samba/file-shares/tmp browseable = yes read only = no invalid users = root administrator delete readonly = yes inherit owner = yes force group = Development dos filemode = yes A 'getfacl' on /srv/samba/file-shares/tmp returns: # file: srv/samba/file-shares/tmp # owner: root # group: root # flags: -s- user::rwx group::r-x group:Development:rwx mask::rwx other::--- default:user::rwx default:group::r-x default:group:Development:rwx default:mask::rwx default:other::--- From the 'smb.conf' man page concerning option 'dos filemode': ... Enabling this parameter allows a user who has write access to the file (by whatever means, including an ACL permission) to modify the permissions (including ACL) on it. ... My understanding: as a member of group 'Development' I do have write access to '/srv/samba/file-shares/tmp' by means of the ACL. Trying to modify permissions on a directory or file I create in that share does not work and reports access denied, no matter if I use Windows Explorer or smbclient from an other linux box. What am I misunderstanding here? Many thanks, Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Bug 7892 fixed in Samba 3.5.6
On 05.03.2011 16:19, Volker Lendecke wrote: On Fri, Mar 04, 2011 at 04:33:43PM +0100, Felix Brack wrote: Hello, I use Debian Squeeze with Samba 3.5.6. I do experience problems that might be related to those described in bug 7892 that can be found found here: https://bugzilla.samba.org/show_bug.cgi?id=7892 I could not find any information about this bug being fixed in Samba 3.5.x. In the realease notes of Samba 3.4.10 I found this: '* BUG 7892: Fix stale lock in open_file_fchmod().' As version 3.4.10 is smaller then version 3.5.6 I guess it is fixed. 3.5.6 was released Oct 8, 2010. The patch went into the tree on Dec 31, 2010. 3.5.7 will be a pure security release, so the fix will be in 3.5.8. With best regards, Volker Lendecke Thank you very much for this information. I will then check if that release fixes my problem. reagards, Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Bug 7892 fixed in Samba 3.5.6
Hello, I use Debian Squeeze with Samba 3.5.6. I do experience problems that might be related to those described in bug 7892 that can be found found here: https://bugzilla.samba.org/show_bug.cgi?id=7892 I could not find any information about this bug being fixed in Samba 3.5.x. In the realease notes of Samba 3.4.10 I found this: '* BUG 7892: Fix stale lock in open_file_fchmod().' As version 3.4.10 is smaller then version 3.5.6 I guess it is fixed. Is this guess correct? Many thanks, Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Samba cd-rom share Problem
Perhaps a stupid question: you are sure you DID mount the cdrom on the linux console? If I do not mount it (or umount it) a can confirm the symptom you are describing. - Felix Andreas Bauer wrote: AB> Hello NG, AB> my network consists of AD/2003 as LDAP Server, SuSE 10.0 and xp AB> clients and SuSE 9.3 Samba/NFS-Fileserver for the homes of SuSE clients and AB> Samba AB> shares for the Xp clients. AB> My problem is the cd-rom samba share. All other samba shares except the AB> cd-rom share are working for me. AB> If I open the network environment in the windows explorer of a succeded AB> logon xp client, I can access all shares except the cd-rom share. AB> At accessing the cd-rom share in the windows explorer, I am getting no AB> errormessage, but the directories and files of the shared cd do AB> not appeare in the right side side of the win explorer. The right part of AB> the AB> windows exlorer is empty. AB> The cd-rom section in the smb.conf is: AB> [cdrom] AB>path = /media/cdrom AB>read only = yes AB>browseable = yes AB>locking = no AB> Best regards and many thanks AB> Andreas AB> -- AB> To unsubscribe from this list go to the following URL and read the AB> instructions: https://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re[4]: [Samba] VFS for encryption/decryption
It's true (partially) that the administrator has access to all secrets stored on the server. However the administrator does not _know_ a users password or samba password. He can of course change those passwords. This however would be noticed by the user who's password has been changed and data encrypted with the users former password would still not decrypt (with the new password) to some meaningful data, right? If this is correct my requirements would be fulfilled. I do not know at all how things are running within samba but fact is, that any user authenticates himself when connecting to a server share from his client. Wouldn't this be the method to tell a VFS module to do encryption/decryption with the user's password? As I already stated, I am aware that things are not that simple but the principle should remain. My PDC is setup to present the user a network drive H: that holds his home directory; this is great and very simple to configure with samba. Why not present the user, say network drive Q:, showing the decrypted contents of a file stored on the server that is encrypted with the users password? The user wouldn't 'see' any difference between accessing files on H: or Q:. This would provide a truly transparent access to encrypted data. - Felix Andrew Bartlett wrote: AB> We run into issues such as 'how do you key the crypto'. The AB> administrator has access to any secrets stored on the server, so how AB> would Samba decrypt the data, but the administrator not? AB> Without protocol modifications, or some extra client-side tool, this AB> becomes quite a challenge. And then the administrator could still AB> subvert the whole thing. AB> A slightly easier goal would be to protect files on a stolen hard disk AB> (ie trust the admin, but not always the person with the server), but I AB> still don't see how to do it without protocol modifications. AB> Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re[2]: [Samba] VFS for encryption/decryption
Hello Andrew, In my case, clear over the network would be ok. The problem I am trying to solve is: I can setup Samba PDC perfectly so every user get's some space which is accessible by nobody else. The administrator of the samba server however (at least the user root) has access to all files of all users. The normal user has no LINUX login account on the box running the samba server. I could ask the users to run TrueCrypt (www.truecrypt.org) and create a encrypted file on their home directory on the Samba server. This works perfect but I was just looking for an even more transparent solution which I think could be provided by some sort of VFS module. - Felix Andrew Bartlett wrote: AB> On Mon, 2005-12-19 at 13:39 +0100, Felix Brack wrote: >> Hello, >> >> Does anybody know of an existing VFS module that allows on the fly >> encryption of the contents of a samba file share? AB> Encryption on disk, but clear over the network? AB> (that is the main problem I see with this idea). AB> Andrew Bartlett -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] VFS for encryption/decryption
Hello, Does anybody know of an existing VFS module that allows on the fly encryption of the contents of a samba file share? thanks, Felix -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re[2]: [Samba] CVS checkout problems to Samba 3.0
Everything is fine again with Samba 3.0.1rc1! Many thanks for your help, Felix GJC> -BEGIN PGP SIGNED MESSAGE- GJC> Hash: SHA1 GJC> Felix Brack wrote: GJC> | I normaly checkout starting from dir_1 so dir_2 and the files are GJC> generated GJC> | automatically. Trying to do so, when the target is on Samba 3.0.0 ends GJC> with GJC> | an error message, saying that dir_1 cannot be created. Any directory or GJC> | file below dir_1 is mising after the ceckout. GJC> | When I create the directory structure on the target Samba 3.0.0 server GJC> | BEFORE running the above checkout, the checkout runs fine. GJC> | GJC> | As stated above, doing exactly the same thing (checking out dir_1) to a GJC> | localy attached disk or a Samba 2.2.8 server works fine. GJC> | GJC> | Any idea what went wrong when configuring the samba server? Is there any GJC> | new (relevant to this problem) option I should change or set in smb.conf? GJC> This sounds like a similar bug fixed post 3.0.0. Please test 3.0.1rc1. GJC> Thanks. GJC> cheers, jerry GJC> -BEGIN PGP SIGNATURE- GJC> Version: GnuPG v1.2.1 (GNU/Linux) GJC> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org GJC> iD8DBQE/1IasIR7qMdg1EfYRAo0tAJ9SdxsgRZLBxGfmjf8YRuF9A017iQCgiD0T GJC> KfDlPjMWWccFnex1etIZNd0= GJC> =Kl0V GJC> -END PGP SIGNATURE- - Felix Brack LTEC AG Hauptstrasse 66 CH-4436 Oberdorf SWITZERLAND Internet: www.ltec.ch Tel. +41 61 9631414 Fax. +41 61 9631413 E-Mail: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] CVS checkout problems to Samba 3.0
After upgrading a Samba 2.2.8 to a 3.0.0 I am having problems to checkout data from a CVS repository to a location on the Samba server. Checking out the same data to a local disk or to a location on a Samba 2.2.8 server does work without any problems. Sample structure in CVS repository: dir_1 |dir_2 |__file_1 |__file_2 I normaly checkout starting from dir_1 so dir_2 and the files are generated automatically. Trying to do so, when the target is on Samba 3.0.0 ends with an error message, saying that dir_1 cannot be created. Any directory or file below dir_1 is mising after the ceckout. When I create the directory structure on the target Samba 3.0.0 server BEFORE running the above checkout, the checkout runs fine. As stated above, doing exactly the same thing (checking out dir_1) to a localy attached disk or a Samba 2.2.8 server works fine. Any idea what went wrong when configuring the samba server? Is there any new (relevant to this problem) option I should change or set in smb.conf? Many thanks, Felix - Felix Brack LTEC AG Hauptstrasse 66 CH-4436 Oberdorf SWITZERLAND Internet: www.ltec.ch Tel. +41 61 9631414 Fax. +41 61 9631413 E-Mail: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
