similar to: Shares within Shares (Digest 2186)

Is it possible to have a share within a share, or to force group on directories within a share? What I am trying to do is set up departmental shares, but find that having them all in the root list of shares looks messy (too many shares :P ) What would be preferable, would be to have a [departments] share, then put a share for each department within that share. Just using directories within

I have run into a problem recently which is driving me crazy. :) Our current setup is as follows: FreeBSD 2.2.8 server running Samba 2.0.5a The Samba server auths against an NT 4.0 Server (SP5). Certain NT machines in our network (NT 4.0 Server SP4), have problems accessing shares on the samba server. After a clean boot, they will be able to successfully access the shares for about 1/2 hour,

I am setting up samba as a print server on a FreeBSD machine. I would like the users to be able to control the print queue by using the Pause option in Windows NT. It seems that I have a permission problem doing this though. -- Portion of smb.conf -- [global] lpq command = /usr/bin/lpq -P%p lprm command = /usr/bin/lprm -P%p %j queuepause command =

I have set up several shares which our staff will have access to. They are central repositories where we will be storing things like documents and drivers, etc. I would like to allow staff to add items into the shares, but to now be able to remove anything (Except maybe what they put in..) I have created a share called drivers: [drivers] comment = General Hardware

> The way I deal with this is to use SetGID. The way this works is that you set the setgid bit on a directory, and any file or directory created under it inherits it's group, rather than the primary group of the process creating it. Directories created under this directory also inherit the SetGID bit. This means that if you have one share, with all the top level directories in it.

Hi! I am experiencing troubles concerning the inheritance of the setgid bit if a new mailbox is created with dovecot-lda. If it is created with dovecot/imap, everything works fine. dovecot-lda is called from postfix like this: ---------- mailbox_command = /usr/local/sbin/postfix-lda.sh ---------- logger -p mail.info -t postfix-lda "H: $HOME, S: $SENDER, R: $RECIPIENT, U: $(umask), id:

Hello, I ran into a problem the other day where our NT PDC and BDCs starting flaking out. They all thought that there was another PDC on the network and so would not promote. After several hours of fighting with the NT servers, we checked a change that had been made to our smb.conf on our fileserver. Namely, the addition of "domain logons = yes". My understanding was that this

On Tue, 24 Jul 2018 14:38:31 +0200 Michal via samba <samba at lists.samba.org> wrote: > Samba DM config below. > Directories with setgid: > > $ll /home4/group > total 32 > drwxrws--- 7 NIS\nisadmin NIS\audio 4096 Jul 24 14:14 audio > drwxrwx--- 2 NIS\nisadmin NIS\dok-sprava 4096 Jul 21 09:23 dok-sprava > drwxrwx--- 2 NIS\nisadmin NIS\poj 4096 Jul 23

Hi, Is it possible with samba to enforce the inheritance of group ownership on a per-directory basis, for files moved without copying? My situation is as follows: directory 'a' has permissions: 2770 (drwxrws---) and has owner = 'root' group = 'a' directory 'b' has permissions: 2770 (drwxrws---) and has owner = 'root' group = 'b' As per

For being honest, in my previous tests this user's (user test1) new files was created with NIS\audio group as extected; but other user's files (user amistest) was created with "NIS\domain users" group (in the same "audio" directory). This lasted a few days. It looked like drwxr-sr-x 2 NIS\amistest NIS\audio 4096 Jul 24 08:17 amistestdir drwxrwsr-x+ 2

Am Dienstag, 24. Juli 2018, 14:38:31 CEST schrieb Michal via samba: > Samba DM config below. > Directories with setgid: > > $ll /home4/group > total 32 > drwxrws--- 7 NIS\nisadmin NIS\audio 4096 Jul 24 14:14 audio > drwxrwx--- 2 NIS\nisadmin NIS\dok-sprava 4096 Jul 21 09:23 dok-sprava > drwxrwx--- 2 NIS\nisadmin NIS\poj 4096 Jul 23 08:38 poj > drwxrwx---

Hello, Is there a parameter in smb.conf that prevent users to use drag and drop within Samba shares? I know this is a Winedow$ function, but some users (hum, hum) use Explorer to open their files and accidentally they drag and drop sometimes a directory in the root of the share to another directory in the root of the share. My samba server is member of a native W2k3 server Active Directory

Hello, Is there a parameter in smb.conf that prevent users to use drag and drop within Samba shares? I know this is a Winedow$ function, but some users (hum, hum) use Explorer to open their files and accidentally they drag and drop sometimes a directory in the root of the share to another directory in the root of the share. My samba server is member of a native W2k3 server Active Directory and

Samba DM config below. Directories with setgid: $ll /home4/group total 32 drwxrws--- 7 NIS\nisadmin NIS\audio 4096 Jul 24 14:14 audio drwxrwx--- 2 NIS\nisadmin NIS\dok-sprava 4096 Jul 21 09:23 dok-sprava drwxrwx--- 2 NIS\nisadmin NIS\poj 4096 Jul 23 08:38 poj drwxrwx--- 2 NIS\nisadmin NIS\projekty 4096 Jul 23 09:14 projekty When user creates file/dir directly on linux, the

On 08/11/15 11:53, Michael Adam wrote: > On 2015-11-08 at 11:14 +0000, Rowland Penny wrote: >> On 08/11/15 10:49, Michael Adam wrote: >>> On 2015-11-08 at 09:29 +0000, Rowland Penny wrote: >>>> On 07/11/15 23:28, Michael Adam wrote: >>>>> rsync will work if not using --numeric-ids. >>>> OK, I know that logins will work on all the samba

I'm seeing behavior that I was hoping somebody could explain. I have a share set up that will be a repository for company-wide data. There are three classes of people who can access it, readers, read/writers, and admins. Readers and read/writers are self explanatory, admins have read/write access, and can change the permissions/ownership of files. Read and write access is controlled by

Hi John, this is my smb.conf-file: # /usr/local/etc/smb.conf # # $Id: smb.conf,v 1.1 2002/11/28 17:53:45 root Exp $ # [global] workgroup = ossa6 netbios name = claire server string = File-services on claire. hosts allow = 192.168.0.0/255.255.255.0 max log size = 0 security = user encrypt passwords = yes smb passwd file = /usr/local/etc/smbpasswd socket options = TCP_NODELAY interfaces =

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 3 Mar 2017, Bernard wrote: > On 01/03/2017 11:27, Bernard wrote: >> Hello, >> >> I am new to the list. /Waving at everyone/ >> >> I got a basic SpamAssassin working on a Debian setup (w/ debian-spamd >> user), running as a Postfix transport. >> >> I am currently trying to switch it to a

Hello! Please, help! I have trouble with Dovecot's Deliver utility. I don't know how to avoid errors. Let me know what additional related information do you need? 1) Its call in Exim's configure: ========================================== local_delivery_spam_transport: driver = pipe command = /usr/local/libexec/dovecot/deliver -c

I have compiled R version 1.3.1 on a Linux system. No errors or warnings are reported. However, "make check" fails thus: ===== make[5]: Leaving directory `/proj/informatics-build/GML/R/R-1.3.1/src/library' running code in base-Ex.R ... ../../bin/R --vanilla < base-Ex.R > base-Ex.Rout make[4]: *** [base-Ex.Rout] Error 139 ===== The base-Ex.Rout being produced at this