similar to: hiding Unix perms

Hello, I figured it out, in short, winbind rocks. For some reason, I did not see the point of specifying nss_winbind in /etc/nsswitch.conf. Now that I did that I can use the UIDs/GIDs mapped for my system by winbindd for perms. Using winbind this way eliminates the need to create local Unix accounts :) Awesome. I'm not sure why I didn't realize this before ( maybe because the other

One work-around would be to create a hidden share that only Domain Admins can access. The use "force user=root" on that share. Then you'll be able to change ACL's and not be root. Josh > -----Original Message----- > From: Tanstaafl [mailto:tanstaafl_bh@netzero.net] > Sent: Thursday, July 25, 2002 1:36 PM > To: 'Samba List' > Subject: Re: [Samba] Changing

Hello, I have winbind set up and working with Linux 2.2.20acl, as far as I can tell everything works except for "Taking Ownership" and modification of permissions by group members. I have a user ( we'll call him "user" ) who is in the DOMAIN+Employees group ( this groups has full control over FILE.doc ). If I try to change permissions from a Windows 2k client, I get an

Please make windows go away. I am enjoying(even the frustrations)learning linux for the first time. So many packages and features, it's crazy. I like crazy but have a request for you guys. Is it possible to provide me with some documentation as to how to configure my server to be a PDC compared to Windows 2000 Advanced Server? I am having a hard time understanding samba because of how easy it

Dear R people, I wonder how to hide tick lines behind other figures in a plot, e.g. in a boxplot. # Sample code: x<- c(rep(4,50),rep(5,20),rep(6,50),rnorm(20,5,1)) boxplot(x) axis(2,tck=1,col.ticks='grey',lty=5 ) # end of sample code The tick lines is put on top of the box-plot, but I would like to put these lines behind the box and whiskers.. Regards Helmer

Hi, I tried again with some other options. After finding http://www.dovecot.org/list/dovecot/2013-November/093793.html I deleted every ACL from the directory Maildir and I also assigned the group "mail" to it, recursively: OmniOS-Xeon:/tank/home/olaf/Maildir/.Generiche $ ls -lV total 903 drwxrwxrwx 2 olaf mail 2 Sep 27 23:47 cur

Hi, I was experimenting with Logstash + elasticsearch on FreeBSD 9 - initially I downloaded it by hand (I forgot to check for a port) and it worked fine. I then tried the port and this forced me to use a different java version (was jdk-16.0.3p4_25 now openjdk6-b27) and it seems that the new one causes a panic. Unfortunately crashdumps aren't working properly, however I did get the panic

I have a shell user who is able to login to his accounts via sshd on FreeBSD 8.2 using any password. The user had a .ssh/id_rsa and .ssh/id_rsa.pub key pair without a password but nullok was not specified, so I think this should be considered a bug. During diagnosis, /etc/pam.d/sshd was configured for authentication using: ------------- auth required pam_ssh.so

Hi, On 2015-09-19 16:17, Olaf Marzocchi wrote: > Dear Dovecot users, hello. > I will merge two issues I have into a single email because they may be > related. > > I used dovecot on a OmniOS server since 2014 (currently OmniOS > r151014) with the following configuration (it shows 2.2.18 because I > recently updated dovecot, skipping only the PostgreSQL plugin): > > #

Hi, Here's the deal; Currently within our NT domain, Network Neighborhood can see our SAMBA server via both the "netbios" name (set with 'netbios name = vegas' from within the smb.conf file), plus the actual UNIX system name. We want our users to browse our SAMBA server only via the "netbios" name and not the actual UNIX system name. How can I configure

Hello, I posted some days ago and after searching more and more i think the problem could be fixed patching the kernel with ACL support, am i right? Here's my problem: I have a samba server running as a domain member in a windows domain controlled by a windows nt4 PDC. Samba has to authenticate users against that nt4 PDC, it works, i also use winbind to map uid and gid to my linux so i can

Hello, Noticed this (bug?) while testing out rsync. For a little background, I need to push files real-time to some front-end servers, and I am thinking of switching from some custom shell scripts that do this job to rsync. I am thinking of running rsync as a daemon on the front-end servers, and doing an upload from the back-end server to push the data out as it comes in. So, here is the deal:

Dear Dovecot users, hello. I will merge two issues I have into a single email because they may be related. I used dovecot on a OmniOS server since 2014 (currently OmniOS r151014) with the following configuration (it shows 2.2.18 because I recently updated dovecot, skipping only the PostgreSQL plugin): # 2.2.18: /etc/dovecot/dovecot.conf # OS: SunOS 5.11 i86pc zfs mail_location =

The subject's a little misleading really, but I was looking for some clarification of my thoughts... In Windows, one can use both share permissions and NTFS permissions to control access to files. I would normally use share permissions to control a connection (allow/deny), and use NTFS to control access. I would never use share permissions to control access whilst NTFS was capable of

Hi, I am struggling with Postfix/SASL/Dovecot-IMAP setup with ~/Maildir/ setup. Receiving the mail works fine, but viewing the mail(+listing) is failing. The setup I use is simple unix users from etc/passwd, (pam thru SASL) as I only host for a few people. The ~/Maildir folder has the ownership of the user, not mail or vmail, as I would have expected from the master.cf from Postfix, the

rsync --perms -M--fake-super src dst For me, this command means that rsync should save the original perms in the xattr, and leave the real file mode to the umask default. Currently it also modifies the real file mode, and there is no way to store something different in the xattr. According to an old bug report that I found, more people would like --fake-super to be a complete attribute

I would expect that the sending rsync would only send the perms provided modified by the --chmod. I wouldn't expect the receiver to even know the other permissions. On 3/12/20 1:23 PM, Dimitrios Apostolou via rsync wrote: > Thank you for the feedback, I'm glad to see that different people see > the issue > differently. As a followup question, what would you expect this to do:

Thank you for the feedback, I'm glad to see that different people see the issue differently. As a followup question, what would you expect this to do: rsync --perms --chmod g+rX -M--fake-super src dst I would expect it to store the original permissions in the xattr, while modifying the real file mode according to the chmod. On Thursday, March 12, 2020 6:06:34 PM CET, Kevin Korb via rsync

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on dovecot launch, 'dovecot.log' is created as: -rw------- 1 root testuser 271 2006-09-11 07:58 dovecot.log which causes an apparent perms prob with exim using dovecot's LDA ... what/how do i define/change the LOG's ownership/perms with? it seems to ignore the dovecot.conf umask setting, etc. thx. richard - -- /"\ \

Using --existing, I would like to transfer files created by root to home dirs, where the files would be updated, but leave the user,group and perms as they were. ie root creates a new file on the sending system, rsyncs it to the home dir of the user, leaving the perms untouched. Seems there is no option for this - the users are not defined on the sending system. I cant do it backwards due to