John,
For the [chemgroup] share try
[chemgroup]
comment = Chemistry Group Share
path = /home/chemgroup
valid users = @chemgroup
write list = @chemgroup
browseable = no
;;writeable = yes
;;printable = no
force group = @chemgroup ;; note your post left out the
John,
Yes, I agree that you should not install from source--I meant to imply
if you could get a deb package for your Ubuntu Server 10.10.
I did not enable ACLs and User Extended Attributes until I installed the
first iteration of the Samba 3.5 branch on my Fedora 13 server (I'm
about to upgrade
Quoting John Maher (john at chem.umass.edu):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I cannot find anything in the documentation or mailing list that
addresses this oddity.
I've installed Samba Version 3.4.7 on Ubuntu Server 10.04, and I'm
utterly confused by samba's
--this might also show the SID
to UID/GID mappings.
Bob
--bs
On 06/03/2011 01:18 PM, Robert W. Smith wrote:
...
John,
To get back to your issue at hand...Can we see the output of your
logs--the entire delete/rename transactions?
Bob, thanks for your continued interest and help.
Here is log
On Mon, 2011-02-21 at 21:08 +1300, Mike Brady wrote:
I have spent the last few days attempting to get a Samba3 PDC/BDC
setup with an LDAP SAM and need some clarification on exactly what
should/can be initialized in the LDAP SAM.
As my main sources of information/inspiration I have been
I have two users on my network, Mary and Bob, who work together in a
shared share. They both belong to the group Accounting. Bob is a savvy
Linux user who accesses the share via NFS4. Mary toils away using
Windows accessing the share via the Samba server. Mary will create a
directory on the share
This might be more inclusive if I said, Linux Permissions vs POSIX ACLs
vs vfs_xattr.
I have recently begun to discover the power and flexibility of using
POSIX ACLs (by mounting my EXT3/4 filesystems with the acl option). This
solved alot of security permissions issues between Samba and Linux
I was not able to get it to reproduce yesterday. I will monitor my logs for
the next several days and perform more testing over the weekend.
Bob
--bs
-Original Message-
From: Volker Lendecke [mailto:volker.lende...@sernet.de]
Sent: August 26, 2010 03:26
To: Robert W. Smith
Cc: samba
step on myself with this one but in the process I
learned alot more about how locking works in Linux and Samba.
Bob
Part-time self-inflicted Linux administrator
--bs
On Tue, 2010-08-24 at 07:04 +0200, Volker Lendecke wrote:
On Mon, Aug 23, 2010 at 11:34:21PM -0400, Robert W. Smith wrote:
OK, so
Volker, yes this trick worked for the current problems but agreed that
it is not a long term solution to the locking problem.
Thanks, Bob
--bs
On Tue, 2010-08-24 at 07:04 +0200, Volker Lendecke wrote:
On Mon, Aug 23, 2010 at 11:34:21PM -0400, Robert W. Smith wrote:
OK, so far I now
Happened to be tail'ing machine.log during a login session from XP
client and notice the PANIC in the output. Login proceeded as usual(?)
so the following snippet of the log is just informational to the
developers. Let me know if you need additional info.
Bob
--bs
[2010/08/25 21:34:21.689597,
(or too
long). Any pointers are greatly appreciated.
--bs
On Sun, 2010-08-22 at 19:55 -0400, Robert W. Smith wrote:
I am running two Fedora 13 servers, one as a Samba PDC and the other as
a BDC. For the past week I have been tracing a series of issues which
may or may not be related to Samba 3.5.4
I am running two Fedora 13 servers, one as a Samba PDC and the other as
a BDC. For the past week I have been tracing a series of issues which
may or may not be related to Samba 3.5.4. Here is one problem that I am
tracking and need help from the list with suggestions.
From a wireshark trace
13 matches
Mail list logo
