similar to: chgrp not consistent on AD groups

Displaying 20 results from an estimated 10000 matches similar to: "chgrp not consistent on AD groups"

2018 Jun 06
2
how to use chgrp command for samba groups
i use chgrp -R "Domain Users" /profiles for example but i receive no such group available in chgrp command what i must do to be able to have the samba groups available in linux environment using the the chgrp and accepting them. thank you
2007 Mar 08
0
chown/chgrp for winbind users doesn`t work
Hello, I have two Samba Domains and each trust each other (PDCs run 3.0.22). Also I have a samba member server (3.0.24) that runs winbind. When I use wbinfo I can see the user and groups of both domains. I also can chown/chgrp files with users of the domain the server is member of. But I can`t chown/chgrp with accounts of the trusted domain. chown doesn`t work at all. chgrp works, but then only
2018 Oct 09
2
how to use for example Domain Users of samba using chown chgrp
i am using chgrp and chown to change ownership from centos command line of paths for example domain users to use it in chgrp bur it is telling me the error that no such group exist. what i must do to be able to use samba users and groups from command line using chown and chgrp thank you
2016 Apr 05
0
chgrp "Domain Admins" on folder return invalid group "Domain Admins"
Hi Jules, > I am trying to deploy Samba4 as a domain controller and a file server and > having some issues.* > > The domain have been well provisioned with option --use-rfc2307 > > I am then trying to create share by following this samba wiki > https://wiki.samba.org/index.php/Shares_with_Windows_ACLs > > The problem is that i cannot succeed to change the group owner of
2017 Nov 06
0
[Bug 11414] rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)
https://bugzilla.samba.org/show_bug.cgi?id=11414 --- Comment #2 from Michal Ruprich <mruprich at redhat.com> --- I stumbled upon this bug and I have a question. I get the chgrp error even when running the daemon as root. #ps -aux | grep rsync root 18486 0.0 0.0 114696 568 ? Ss 09:41 0:00 rsync --daemon I have configured a module in /etc/rsyncd.conf like this: [my_data]
2003 Jul 04
0
Minor probs after upgrade to 3.0.0beta2
Firstly, I am running beta2 as AD member. Auth through Winbind. Upgrading from beta1 to beta2 using RPM on RH 9 I noticed that Winbind will not start and smb will not stop using Init scripts. Seems to me RH9 /etc/init.d/winbind need the "winbind uid" parameter ? Here is the /var/log/samba/log.winbind output. [2003/07/04 13:54:52, 1] nsswitch/winbindd.c:main(811) winbindd version
2016 Apr 05
2
chgrp "Domain Admins" on folder return invalid group "Domain Admins"
Hi Denis, Thank you for your mail. I assigned the GID 10000 to the domain admins group through ADUC, and wbinfo --info-group "domain admins" display the correct output. But i am still not able to execute succesfuly #chgrp "Domain Admins" /home/demo And when i go to ADUC and try to open the Unix Attribute of domain admins group, i have the error "Unable to
2015 Jul 27
8
[Bug 11414] New: rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1)
https://bugzilla.samba.org/show_bug.cgi?id=11414 Bug ID: 11414 Summary: rsync: chgrp "/.filename.5afK5X" (in dirdir) failed: Operation not permitted (1) Product: rsync Version: 3.1.1 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5
2016 Apr 05
2
chgrp "Domain Admins" on folder return invalid group "Domain Admins"
Dear all, thank you for your previous mails. It realy help me. Denis, Following your mail and thanks to the link i configure my /etc/nsswitch.conf file by adding windbind to user and group line and execute winbindd command. As i install samba4 from sernet package, init script are created for starting AD, smbd, nmbd and winbindd. But i read that smbd, nmd and winbindd should be disable to
2007 Aug 15
2
chown and chgrp on 4.5 vs 5.0
I just noticed that on centso 4.5 I have an executable with the +s (chmod +s myexe) doing a chmod root myexe and chown root myexe does NOT affect the +s setting. However, on centos 5 this is not the case. chmod +s myexe chown root myexe or chgrp root myexe will DROP the +s status. How can I get around this? I want to keep the owner, group, world settings. Thanks, Jerry
2007 Aug 30
1
strange chgrp behavior
Greetings, i had a following problem, which on one side i have already solved, but on other side i don't thing it should behave this way and wish somebody to tell if it is feature or bug ;-) [root at machine home]# chown user user/ [root at machine home]# ls -ld /home/user drwxr-xr-x 66 user staff 4096 /home/user [root at machine home]# chgrp -R staff user/ [root at machine home]# ls -ld
2004 Dec 20
1
rsync: chgrp ... Operation not permitted
Hi all, I've installed rsync to synchronize my linux box and my PowerBook. I have a server whose conf file looks like [letters] use chroot = yes uid = www gid = lha.utils path = /var/hdb/letters read only = no list = yes auth users = pascal,lha secrets file = /etc/rsyncd.secret but when the client tries to write I have: rsync: chgrp "/file/path/here" failed: Operation not
2011 Nov 09
1
default Dovecot-LDA CHGRP/CHMOD
I am familiar with this article http://wiki.dovecot.org/LDA#multipleuids I want to disable setuid-root, but I don't know the default group and permissions. sudo chgrp root /usr/libexec/dovecot/dovecot-lda sudo chmod 00750 /usr/libexec/dovecot/dovecot-lda but my delivery is still failing Nov 9 18:22:39 vl42 postfix/pipe[23039]: DEC54700B1: to=<user at domain.com>, orig_to=<user at
2007 Apr 23
1
chgrp problem
I'm using a comand like rsync -av directory /media/usbdisk/ to backup to a usb device (on a Fedora 5 machine). I'm getting 100s of messages like rsync: chgrp "/media/usbdisk/file" failed: Operation not permitted (1) and then at the end rsync error: some files could not be transferred. How do I fix this? Why is rsync trying to change the group? And is the message at
2012 Aug 14
2
chown, chgrp?
Hi all, Is there an R wrapper for chown/chgrp (a la Sys.chmod)? I couldn't find one with a few minutes of searching, but it seems like a curious omission. Thanks, Hadley -- Assistant Professor Department of Statistics / Rice University http://had.co.nz/
2006 Oct 31
0
6362068 zfs chown/chgrp doesn''t always work
Author: marks Repository: /hg/zfs-crypto/gate Revision: daa24505790be2859c3416a615beb97cbe02db68 Log message: 6362068 zfs chown/chgrp doesn''t always work Files: update: usr/src/uts/common/fs/zfs/zfs_vnops.c update: usr/src/uts/common/os/policy.c update: usr/src/uts/common/sys/policy.h
2016 Apr 05
0
chgrp "Domain Admins" on folder return invalid group "Domain Admins"
On 05/04/16 13:46, Jules Houantonon wrote: > Dear all, > > thank you for your previous mails. It realy help me. > > Denis, Following your mail and thanks to the link i configure my > /etc/nsswitch.conf file by adding windbind to user and group line and > execute winbindd command. > > As i install samba4 from sernet package, init script are created for > starting
2016 Apr 04
3
chgrp "Domain Admins" on folder return invalid group "Domain Admins"
Dear Samba users and admins, I am trying to deploy Samba4 as a domain controller and a file server and having some issues.* The domain have been well provisioned with option --use-rfc2307 I am then trying to create share by following this samba wiki https://wiki.samba.org/index.php/Shares_with_Windows_ACLs The problem is that i cannot succeed to change the group owner of the folder I want to
2008 Nov 24
5
[Bug 1541] New: sftp: the do_stat() failure is ignored for chown, chgrp ops. in parse_dispatch_command()
https://bugzilla.mindrot.org/show_bug.cgi?id=1541 Summary: sftp: the do_stat() failure is ignored for chown, chgrp ops. in parse_dispatch_command() Product: Portable OpenSSH Version: -current Platform: All OS/Version: All Status: NEW Severity: trivial Priority: P5 Component: sftp
2010 Oct 14
2
Dovecot chgrp actions on new files/folders
Timo, I did further study of the user/group permissions. Applying the below patch will make no difference to virtually everyone out there. Those that have default uid/gid ownership won't see any change as the gid already matches so the fchown() action won't be attempted. Those that have sgid will still see the normal expected fchown() enforced by the kernel which becomes a duplicated