similar to: SUMMARY: hiding Unix perms

Hello, Sorry if I missed this in the docs, I haven't seen an option to do this.. I have a Samba server ( Linux 2.20acl kernel ) named "fileserver" set up and working well as a fileserver to Windows clients ( I am using winbind also ). Samba has some awesome capabilities nowadays :) The current issues I am facing aren't exactly showstoppers, but I know they'll be

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

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

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, 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, there is a suitable HowTo on how to create your own CA at: https://checkmk.com/de/blog/how-become-your-own-certificate-authority So long Thom Am 28.05.24 um 09:20 schrieb Matthias K?hne | Ellerhold Aktiengesellschaft via samba: > Hello Thomas, > > we've done the exact same thing: we have a few nextcloud instances bound > to Samba (now 4.20, but 4.19 worked too). >

Hello Thomas, we've done the exact same thing: we have a few nextcloud instances bound to Samba (now 4.20, but 4.19 worked too). You HAVE to use "ldaps://<FQDN>" in the "Host" field and "636" in the "Port" field. For the certificates issues: either you create a CA, create the samba certificates and add this CA to the trusted certificate

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, 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

Now that the list is said to be open again, I'm resending this. I've merged my changes into OpenSSH 2.1.0 as Kris imported it into FreeBSD over the weekend. ---------- Forwarded message ---------- Date: Thu, 4 May 2000 08:40:22 -0500 (CDT) From: Guy Helmer <ghelmer at cs.iastate.edu> To: openssh-unix-dev at mindrot.org Subject: OpenSSH (1.2.3) sshd hanging when using rsync over ssh

On Thu, 2006-03-16 at 01:01 +0000, Guy Helmer <ghelmer@palisadesys.com> wrote: > David Wolfskill wrote: > > I'm running: > > > > localhost(6.1-P)[21] uname -a > > FreeBSD localhost 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #19: > Wed Mar 15 07:15:25 PST 2006 >

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

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 =

Hello, I have a bigger problem in calculating the Maximum Likelihood Estimator regarding the degree of freedom of a multivariate skew-t copula. First of all I would like to describe what this is all about, so that you can understand my problem: I have 2 time series with more than 3000 entries each. I would like to calculate a multivariate skew-t Copula that fits this time series. Notice:

Some attribute x from 17 individuals was recorded repeatedly on 6 time points using a Likert scale with 7 distractors. Which statistical test(s) can I apply to check whether the changes along the 6 time points were significant? set.seed( 123 ) x <- matrix( sample( 1:7, 17*6, repl=T ), nrow = 17, byrow = TRUE, dimnames = list(1:17, paste( 'T', 1:6, sep='' )) ) I found

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