Re: [PATCH setup] Add new option --chown-admin

Jon Turney wrote: On 07/07/2022 15:45, Christian Franke wrote: Jon Turney wrote: On 06/07/2022 17:34, Christian Franke wrote: Jon Turney wrote: On 06/07/2022 08:14, Christian Franke wrote: [...] BTW: 'nt_sec.setDefaultSecurity (isAdmin)' is never called with 'isAdmin==true' as 'root_scope

Re: [PATCH setup] Add new option --chown-admin

On 07/07/2022 15:45, Christian Franke wrote: Jon Turney wrote: On 06/07/2022 17:34, Christian Franke wrote: Jon Turney wrote: On 06/07/2022 08:14, Christian Franke wrote: [...] BTW: 'nt_sec.setDefaultSecurity (isAdmin)' is never called with 'isAdmin==true' as 'root_scope' is always 0. ro

using chown with SMB3 network share

hange permissions * the creation/owner of the file looks ok. There's no 'unknown group' message (typical question on StackExchange) * chown and chmod fail with 'invalid argument'. It doesn't whether I do it by a uid or a name, it fails with invalid argument * icacls can be

Re: chown --recursive [OWNER][:[GROUP]] ... doesn't work

On 06/08/2013 12:50 PM, Corinna Vinschen wrote: > On Jun 8 17:47, Vasiliy wrote: >> chown --recursive *.* doesn't change ownership for all files, > > Wrong pattern. *.* doesn't match files without dot. Try > > chmod -R * .* Umm, that changes .. and its child

Re: Possible issue with chown v8.25

ave in the "Group or user >>> names" popup of the Security property. The has all permissions >>> except special permissions. >>> Summary: When the chown -R command is given, the ownership and group of >>> the directory and contained files are changed but

Re: Possible issue with chown v8.25

Your English is fine - mine is problematical. What are icacls and getfacl listings? My problem is that after a chown the directories are inaccessible and/or I can not look at the Security property without getting a diagnostic. I have assumed that the diagnostic indicates an issue. I get the

Re: Possible issue with chown v8.25

ty property. The > has no assigned permissions. > The contained files in the directory have in the "Group or user > names" popup of the Security property. The has all permissions > except special permissions. > Summary: When the chown -R command is given, the ownership a

Possible issue with chown v8.25

Win7 SP1 chown v8.25 Package 8.25-3 Possible related issue at: https://sourceware.org/ml/cygwin/2016-04/msg00400.html Windows operation: Run as Administrator > chown -R owner:group * Windows operation: Explorer -> Operation -> Security Message "The permi

Re: chown --recursive [OWNER][:[GROUP]] ... doesn't work

On Jun 8 17:47, Vasiliy wrote: > chown --recursive *.* doesn't change ownership for all files, Wrong pattern. *.* doesn't match files without dot. Try chmod -R * .* Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygw

chown --recursive [OWNER][:[GROUP]] ... doesn't work

chown --recursive *.* doesn't change ownership for all files, single files are proceeded ok $ uname -srvm CYGWIN_NT-6.1 1.7.20(0.266/5/3) 2013-06-06 17:36 x86_64 -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: Can't chmod/chown any more on FAT32 after doing cyglsa-config

tributes. Therefore the only possible operation on FAT/FAT32 files supported by chmod is setting or clearing the R/O DOS attribute to fake setting or clearing the 'w' bit. chown doesn't work at all. The owner and group information is always faked to be the current user. If you

Can't chmod/chown any more on FAT32 after doing cyglsa-config

Hello forks, I wanted to setup cron as a service, but after first doing cyglsa-config and reboot, it turned out that I can't do any permission related operation in my home directory any more, just as the title described. I have two question is : Is this a supposed behavior and what should I do if

Re: GNU screen won't run; "chown tty: no such file or directory"

On 6/13/2011 9:03 PM, Larry Hall wrote: >On 6/13/2011 1:28 AM, Jeff Schenck wrote: > >>Hello, >> >>When trying to run screen, I get the following errors: >>"chown tty: No such file or directory" in the status bar, >>followed by

Re: GNU screen won't run; "chown tty: no such file or directory"

On 6/13/2011 1:28 AM, Jeff Schenck wrote: Hello, When trying to run screen, I get the following errors: "chown tty: No such file or directory" in the status bar, followed by "Sorry, could not find a PTY". Then it exits. I get the same error in all terminal types I

Re: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor. [SOLVED]

Corina, my problem was solved!! I´ve only added the cyg_server user to "Admins do Dominio" domain group. This group is used by all domain admins and is a domain group, not a local group like "Administradores". Thank you! 2011/3/16 Bruno Galindro da Costa : > Corina, >   Please, can you dump the g

Re: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.

Corina,   Please, can you dump the group policy settings of you test envirioment for compare with my group policy settings? Thanks. 2011/3/7 Corinna Vinschen > > On Mar  6 12:03, Bruno Galindro da Costa wrote: > > Corinna, > > > > The "Administradores" group is a local group used only by the > >

Re: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.

On Mar 6 12:03, Bruno Galindro da Costa wrote: > Corinna, > > The "Administradores" group is a local group used only by the > DomainControllers. suntech-adm is the user that is the "Domain Admin" > -> like "root" account on Unix systems. This information might be > helpful for the analisys... >

Re: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.

OK libstdc++6 4.3.4-3 OK libwrap0 7.6-21 OK login1.10-10 OK man 1.6f-1 OK openssh 5.8p1-1 OK rebase 3.0.1-1 OK rsync3.0

Re: SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.

sshd > service is cyg_server. The service starts normally, BUT, when I try to > logon by ssh, the error bellow was printed in Event Viewer: > > ## > ## The following information is part of the event: sshd: PID 3908: > fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor. > #

SSHD [Windows Domain Controller]: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor.

ssh, the error bellow was printed in Event Viewer: ## ## The following information is part of the event: sshd: PID 3908: fatal: chown(/dev/tty0, 500, 513) failed: Bad file descriptor. ## Bellow are the permissions of the /dev/tty0 file. The "cyg_server" user is a member of "

Re: 1.7.7: Win7 SSHD, chown bad file descriptor

cept I kept the > cyg_server username. > > The service started fine, then I tried to ssh to the system, entered > user/pass, and was immediately disconnected. The windows > application log had the following error: > > sshd: PID 728: fatal: chown(/dev/tty0, 1000, 1002) failed: Bad

1.7.7: Win7 SSHD, chown bad file descriptor

tried to ssh to the system, entered user/pass, and was immediately disconnected. The windows application log had the following error: sshd: PID 728: fatal: chown(/dev/tty0, 1000, 1002) failed: Bad file descriptor $ ls -la /dev/tty0 crw--- 1 SYSTEM Administrators 136, 0 2010-11-12 14

Re: chown in vista not work because of permission denied

Corinna Vinschen wrote: > On May 3 00:26, Matthias Meyer wrote: >> Hello, >> >> I have a cygwin 1.5.25 installation on a vista client. >> I can access the vista client by ssh. For that I use an account >> called "backup". >> >> I want use the ssh account for backup/restore with rsync. >> The Ba

Re: chown in vista not work because of permission denied

On May 3 00:26, Matthias Meyer wrote: > Hello, > > I have a cygwin 1.5.25 installation on a vista client. > I can access the vista client by ssh. For that I use an account > called "backup". > > I want use the ssh account for backup/restore with rsync. > The Backup work well but the restore not

chown in vista not work because of permission denied

by the ssh-account and not by the original user. I get an rsync error: rsync: chown "/Users/matthias/Desktop/.logfile.lnk.Ud0Zgp" (in C) failed: Permission denied (13) I would believe if I can solve the following construction my problem above will be solved too: If I login into this ssh bac..

Re: file attributes: cygwin (ls, chmod, chown, chgrp) versus XP

ec.html>. The section labeled 'The mapping leak' gives an explicit example of how a POSIX mode gets mapped to a set of NT ACLs. > I'd also like to know how to set/get them in cygwin and also XP. I'd expect > that to be chmod(1), chown(1), chgrp(1), id(1), ls(1)

Re: file attributes: cygwin (ls, chmod, chown, chgrp) versus XP

Michael R. Wolf wrote: I'm very familiar with the Unix filesystem, and the commands to change and display attributes. I've been using cygwin for years, but have yet to understand the XP permissions and how they correlate to how cygwin and XP tools manipulate attributes. I've noticed that the l

file attributes: cygwin (ls, chmod, chown, chgrp) versus XP

nd current) description of the relationship between Unix file attributes (permissions, user, and group) and how that corresponds to XP file attributes? I'd also like to know how to set/get them in cygwin and also XP. I'd expect that to be chmod(1), chown(1), chgrp(1), id(1), ls(1), passwd(5

Re: chown with not existing user/group

On Mar 4 06:40, Eric Blake wrote: > | I was thinking cygwin goal was to emulate as much as possible posix > | spec. > > Yes, and cygwin's behavior in this case is still POSIX compliant. Right. The error code in question is this: [EINVAL] The owner or group ID supplied is not a value suppo

Re: chown with not existing user/group

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Matthieu CASTET on 3/4/2008 6:28 AM: | Also according to my posix reading [1], chown should be able to change perm to | any uid/gid. You read wrong. POSIX also allows chown implementations to impose additional restrictions. And on

Re: chown with not existing user/group

so according to my posix reading [1], chown should be able to change perm to any uid/gid. I was thinking cygwin goal was to emulate as much as possible posix spec. Matthieu [1] http://www.opengroup.org/onlinepubs/009695399/functions/chown.html -- Unsubscribe info: http://cygwin.com/ml/#un

Re: chown with not existing user/group

On Feb 29 09:16, Matthieu CASTET wrote: > Hi, > > Dave Korn artimi.com> writes: > > > > > Because it has to emulate unix perms by relating uid/gid to windows RIDs, > which are owned, allocated and > > controlled by the system, and not under the arbitrary choice of the user, so > the semantics

Re: chown with not existing user/group

Hi, Dave Korn artimi.com> writes: > > Because it has to emulate unix perms by relating uid/gid to windows RIDs, which are owned, allocated and > controlled by the system, and not under the arbitrary choice of the user, so the semantics wouldn't be the > same even if we did create ACLs with un

Re: chown with not existing user/group

exist out there in a domain (or even on a > local machine), it treats /etc/passwd as a cache to save going out across the > network to the domain controller for lookups every time a UID is needed. > > > For example for root > > > > $ echo "root:*:0:0:,S-1-5-32-

RE: chown with not existing user/group

it treats /etc/passwd as a cache to save going out across the network to the domain controller for lookups every time a UID is needed. > For example for root > > $ echo "root:*:0:0:,S-1-5-32-545::" >> /etc/passwd > $ chown root:root /tmp/toto > $ ls -l /tmp/toto >

Re: chown with not existing user/group

n if we did create ACLs with unrecognised SIDs on them. Ha, I forgot cygwin remaps them on windows perms. But then why does it works if I create dummy user in /etc/passwd. For example for root $ echo "root:*:0:0:,S-1-5-32-545::" >> /etc/passwd $ chown root:root /tmp/toto $ ls -l /tmp/

RE: chown with not existing user/group

On 28 February 2008 13:59, Matthieu CASTET wrote: > Hi, > > I wonder why on cygwin we can't use chown with numeric id that don't exist > in /etc/passwd, /etc/group [1] ? Because it has to emulate unix perms by relating uid/gid to windows RIDs, which are owned, allocated

chown with not existing user/group

Hi, I wonder why on cygwin we can't use chown with numeric id that don't exist in /etc/passwd, /etc/group [1] ? On linux this works perfectly [2] Matthieu [1] $ touch /tmp/toto $ chown 12345:12346 /tmp/toto chown: changing ownership of `/tmp/toto': Invalid argument [2] $

Re: root and chown

"Robert W. Kuhn" wrote: > On my windows computer: > > [EMAIL PROTECTED]:grep root /etc/passwd > root::0:0:root:/root:/bin/bash > operator:*:12:0:operator:/root: > > [EMAIL PROTECTED]:chown root sshd/ > chown: changing ownership of `sshd': Invali

root and chown

Hello, a do have a problem with my cygwin-NFS-Server, root and chown On my windows computer: [EMAIL PROTECTED]:grep root /etc/passwd root::0:0:root:/root:/bin/bash operator:*:12:0:operator:/root: [EMAIL PROTECTED]:chown root sshd/ chown: changing ownership of `sshd': Invalid arg

Re: File permissions screwy (chown - chmod - ssh - rsync - ntsec??)

Larry Hall (Cygwin) wrote: > > ...you need to add 'smbntsec' to your CYGWIN variable. See > ... > i didn't get perms working right in my network drive but it did lead me to the right place: change my home dir to a local one (for default

Re: File permissions screwy (chown - chmod - ssh - rsync - ntsec??)

psyjoniz wrote: status: ssh works but with permissions issues; rsync works but with permissions issues issues: permissions do not seem to be handled properly within my cygwin environment. this causes two issues: 1) ssh cannot be setup with public keys for authentication because perms can'

Re: File permissions screwy (chown - chmod - ssh - rsync - ntsec??)

disregard my insistence that ssh and rsync do not exist in the setup list. i just ran it again and it is there. i may just go home for the day. :/ -- View this message in context: http://www.nabble.com/File-permissions-screwy-%28chown---chmod---ssh---rsync---ntsec--%29-tf2503531.html#a6979857

File permissions screwy (chown - chmod - ssh - rsync - ntsec??)

goal: get rsync hand-in-hand with ssh to perform a sync from an xp box to a sun box and vice versa (development path for approx 20 programmers: XP(DEV) -> SUN(TEST) -> SUN(UAT) -> SUN(PROD)) (please don't ask why we can't have some *x variant as our development machinesi just can't take that

Re: chmod, chown doesn't work with 1.5.21-1 (FAQ alert)

On 8/24/06, Igor Peshansky wrote: FWIW, I was going to suggest that you look at the relevant FAQ entry (), but then I realized that the entry is horribly out of date, and doesn't mention filesystem types at all (the only place they are mention

Re: chmod, chown doesn't work with 1.5.21-1 (FAQ alert)

On Thu, 24 Aug 2006, Auteria Wallace Winzer Jr. wrote: > I just installed 1.5.21-1 on a new system. On my old > system I had installed previous versions and I didn't > have any issues with chown/chmod. Now with a brand new > install it seems after executing chmod when viewing

chmod, chown doesn't work with 1.5.21-1

I just installed 1.5.21-1 on a new system. On my old system I had installed previous versions and I didn't have any issues with chown/chmod. Now with a brand new install it seems after executing chmod when viewing the results it shows the previous setting. For example: [EMAIL PROTECTED] /

Re: chown & chown on /proc/registry/HKEY_PERFORMANCE_DATA

On 01/06/06, Lester Ingber <[EMAIL PROTECTED]> wrote: I was looking over my /proc directory @lester:/% ls -ld proc dr-xr-xr-x 11 ingber None 0 May 31 2006 proc/ and found @lester:/proc/registry% ls -la total 0 dr-xr-xr-x9 ingber None 0 May 31 22:30 ./ dr-xr-xr-x 11 ingber

Re: setup/symlinks/gcc/chown question

On Wed, Dec 21, 2005 at 02:02:05PM -0800, Karl M wrote: >Thanks Corinna...it works now with the latest snapshot. > >Is there any way to get the date and time of a snapshot on the Cygwin >web page, instead of just the date? Because sometimes the snapshots >change more than once per day, perhaps the

Re: setup/symlinks/gcc/chown question

On Dec 21 14:02, Karl M wrote: > Hi All... > > Thanks Corinna...it works now with the latest snapshot. > > Is there any way to get the date and time of a snapshot on the Cygwin web > page, instead of just the date? Because sometimes the snapshots change more > than once per day, perhaps the tim

Re: setup/symlinks/gcc/chown question

well. Thanks for the help. ...Karl From: Corinna Vinschen Subject: Re: setup/symlinks/gcc/chown question Date: Wed, 21 Dec 2005 14:37:32 +0100 On Dec 20 20:28, Karl M wrote: > Hi All... > > Attached is the output of > > strace -o outfile chown -h administrators.none collect2.ex

Re: setup/symlinks/gcc/chown question

On Dec 20 20:28, Karl M wrote: > Hi All... > > Attached is the output of > > strace -o outfile chown -h administrators.none collect2.exe Thanks, that strace was helpful. I've applied a patch. Please test the next snapshot from http://cygwin.com/snapshots/ Corinna

Re: setup/symlinks/gcc/chown question

Hi All... Attached is the output of strace -o outfile chown -h administrators.none collect2.exe executed in /lib/gcc/i686-pc-mingw32/3.4.4 after having reinstalled gcc/mingw tools. I am using Cygwin chown. (I did mention it in my last email, but it is easy to miss.) Thanks, ...Karl

Re: setup/symlinks/gcc/chown question

duce it and I didn't get any hint that somebody else can reproduce this. I tried chmod -R and chown -R on directories containing symlinks created by a former setup.exe call and the symlinks were still symlinks afterwards. Let's restart with my previous mail: > >Are you sure you

Re: setup/symlinks/gcc/chown question

, which is text). So after running setup each time, I run this script (with no services running) #!/bin/bash echo Setting up Cygwin mount points cygwin-mount-points << This works fine echo "Globally changing ownership and permissions (except /dev /home /proc)&

Re: setup/symlinks/gcc/chown question

; read only box in the windows properties is checked. after the chown -h the > windows properties box says not a valid link. After the chmod -R 755, the > windows properties shows it as a valid shortcut, but the read only box is > unchecked. After a chmod -R 555, the read only box is chec

Re: setup/symlinks/gcc/chown question

the chown -h the windows properties box says not a valid link. After the chmod -R 755, the windows properties shows it as a valid shortcut, but the read only box is unchecked. After a chmod -R 555, the read only box is checked and Cygwin thinks it is a symlink again. [EMAIL PROTECTED] /lib/gcc

Re: setup/symlinks/gcc/chown question

Hi All... If I reinstall gcc/mingw (c++ and core four packages total) and then do ls /lib/gcc/i686-pc-mingw32/3.4.4 I see the links correctly interpreted as links (ls shows them with name -> name), but after I do chown -h on one of the links, ls shows it as name.lnk (and this corresponds

Re: setup/symlinks/gcc/chown question

On Dec 18 09:56, Karl M wrote: > Hi All... > > I just installed gcc/mingw with setup. > > If I do > > cd /lib/gcc/i686-pc-mingw32/3.4.4 > chown -R administrators.none * > > it breaks the symlinks in the directory. I can't see any problem. What does that me

RE: setup/symlinks/gcc/chown question

Hi All... A chown -h causes the same problem as a chown -R. So, the second script does not work around the problem...it does avoid damaging the link, but after the install, the ownership on the links are administrator.none and so I can run gcc -mno-cygwin... as a restricted user. So for now I

setup/symlinks/gcc/chown question

Hi All... I just installed gcc/mingw with setup. If I do cd /lib/gcc/i686-pc-mingw32/3.4.4 chown -R administrators.none * it breaks the symlinks in the directory. If I do chown administrators.none * from a clean install, the symlinks are fine. If I recreate the symlinks by hand, then both

Re: bug in chown()

On Jan 14 16:33, Eric Blake wrote: > Corinna Vinschen writes: > > On Jan 13 06:40, Eric Blake wrote: > > > In trying to get the newly released coreutils 5.3.0 tarball working on > > > cygwin, I discovered that cygwin chown() has a bug. Background: > > Do you inte

Re: bug in chown()

Corinna Vinschen writes: > > On Jan 13 06:40, Eric Blake wrote: > > In trying to get the newly released coreutils 5.3.0 tarball working on > > cygwin, I discovered that cygwin chown() has a bug. Background: > Do you intend to take over maintainership of coreutils? I

Re: bug in chown()

On Jan 13 06:40, Eric Blake wrote: > In trying to get the newly released coreutils 5.3.0 tarball working on > cygwin, I discovered that cygwin chown() has a bug. Background: > http://lists.gnu.org/archive/html/bug-coreutils/2005-01/msg00064.html Do you intend to take over maintain

bug in chown()

In trying to get the newly released coreutils 5.3.0 tarball working on cygwin, I discovered that cygwin chown() has a bug. Background: http://lists.gnu.org/archive/html/bug-coreutils/2005-01/msg00064.html POSIX requires that "chown() shall mark for update the st_ctime field of the fil

Re: chown

> $ ls -ln > -rwxrwxrwx1 544 51348 Nov 17 03:59 testfile > > [EMAIL PROTECTED] ~/test > $ chown --from=514:513 1008:513 testfile > > [EMAIL PROTECTED] ~/test > $ ls -ln > -rwxrwxrwx1 544 51348 Nov 17 03:59 testfile > > Thanks. W

Re: chown

ED] ~/test >$ ls -ln >-rwxrwxrwx1 544 51348 Nov 17 03:59 testfile > >[EMAIL PROTECTED] ~/test >$ chown --from=514:513 1008:513 testfile > >[EMAIL PROTECTED] ~/test >$ ls -ln >-rwxrwxrwx1 544 51348 Nov 17 03:59 testfile >

chown

tfile [EMAIL PROTECTED] ~/test $ chown --from=514:513 1008:513 testfile [EMAIL PROTECTED] ~/test $ ls -ln -rwxrwxrwx1 544 51348 Nov 17 03:59 testfile Thanks. -- George -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://c

Re: chown -R expanding / to //bin etc.

On Jul 21 17:39, [EMAIL PROTECTED] wrote: > I've noticed that if I do (*) a > > chown -R administrator.SYSTEM / > > then chown goes out onto the network and tries to access shares called > //bin, //var, //usr etc., and can block for long periods, too. &g

chown -R expanding / to //bin etc.

I've noticed that if I do (*) a chown -R administrator.SYSTEM / then chown goes out onto the network and tries to access shares called //bin, //var, //usr etc., and can block for long periods, too. Now, I do understand that really I should be doing (**) cho

Re: chown, #!command in scripts, auto-execute (.bat), etc

Hallo! I unpacked all to a directory (Temp), where we have write-permissions. What do you mean "unpacked"? Do you mean that you installed, using setup.exe, in your "Temp" directory or did you do something else? With "unpacking" I mean copying the files, otherwise I'd have written installe

Re: chown, #!command in scripts, auto-execute (.bat), etc

At 01:19 PM 4/7/2004, you wrote: >Larry Hall wrote: > >>At 12:51 PM 3/25/2004, you wrote: >> >> >>>Hallo! >>>I'm using CYGWIN_NT-5.1 (cygcheck.out attached) >>>*I installed Cygwin in a Subdir /cygdrive/d/temp/Cyg/, because here we don't have >>>permissions for /. So I want to chroot to that inst

chown, #!command in scripts, auto-execute (.bat), etc

Larry Hall wrote: At 12:51 PM 3/25/2004, you wrote: Hallo! I'm using CYGWIN_NT-5.1 (cygcheck.out attached) *I installed Cygwin in a Subdir /cygdrive/d/temp/Cyg/, because here we don't have permissions for /. So I want to chroot to that installation-directory, for getting the programs working pr

Re: Chown bug, attn fileutils maintainer (Was Re: RE : How can i really uninstall completly cygwin from Windows XP Pro ???)

On Sun, Feb 08, 2004 at 10:12:32PM -0500, Igor Pechtchanski wrote: > > BTW, I have a procedural question regarding this. I have a 1-line patch > to fix this in the current fileutils source. However, fileutils is not > maintained, and the problem (generating filenames with the '//' prefix) > affe

Chown bug, attn fileutils maintainer (Was Re: RE : How can i really uninstall completly cygwin from Windows XP Pro ???)

On Sun, 8 Feb 2004, Igor Pechtchanski wrote: > The first is a bug in the Cygwin version of chown. A temporary workaround > would be to use "chown -R Flo /*; chown Flo /". > [snip] > On Sun, 8 Feb 2004, Flo wrote: > > > Hello Thx for your help but i get and

Re: problem with chown

> Hi,all > I installed cygwin under win2k operation system. > Now I have some problem with using command "chown" to change the ownship of > a directory. > > [EMAIL PROTECTED] ~ > $ chown -R cvsuser1:cvsgroup1 /home/lufang/repo Are these real users? Or just "

problem with chown

Hi,all I installed cygwin under win2k operation system. Now I have some problem with using command "chown" to change the ownship of a directory. [EMAIL PROTECTED] ~ $ chown -R cvsuser1:cvsgroup1 /home/lufang/repo [EMAIL PROTECTED] ~ $ ls -lg /home/lufang total 16 dr-xr-xr-x7 luf

RE: NTSEC & ntwrk drives?; chown/chmod/ls -l only wrkg on local drives

mbntsec. Larry Original Message: - From: [EMAIL PROTECTED] (Tom Rodman) Date: Thu, 19 Dec 2002 13:51:02 -0600 To: [EMAIL PROTECTED] Subject: NTSEC & ntwrk drives?; "chown/chmod/ls -l" only wrkg on local drives chown,chmod and ls -l work just fine on local driv

NTSEC & ntwrk drives?; "chown/chmod/ls -l" only wrkg on local drives

chown,chmod and ls -l work just fine on local drives, but not on network drives. My "/tmp" is on the local c drive, and "/cygdrive/s" is a network drive on our NT4.0 SP6A PDC; all commands below done on a NT6.0 SP6A workstatation in the same domain as the P

Re: postgresql + chown

l" Cygwin PostgreSQL README: /usr/doc/Cygwin/postgresql-7.2.2.README or http://www.tishler.net/jason/software/postgresql/postgresql-7.2.2.README > 6. Change ownership of the PostgreSQL data directory: > # chown postgres /usr/share/postgresql/data > > But nothing happen

postgresql + chown

greSQL data directory: # chown postgres /usr/share/postgresql/data But nothing happens. The owner of the directory ist the Administrator. Then I tried to login as postgres: # login postgres But after I entered the password an error occurs: Login incorrect. Following entry is in the /etc/passw

Re: chown problem

rwxrwx UserA:GroupAB DirOne > > In w2k security tabs, I saw : > Owner of DirOne = UserA > Mode= Everyone rwx > = UserArxw > = GroupAB rwx > > When UserA change owner, > $ chown UserB:GroupAB DirO

chown problem

Mode= Everyone rwx = UserArxw = GroupAB rwx When UserA change owner, $ chown UserB:GroupAB DirOne chown: changing ownership "DirOne": permission denied But in w2k security tabs, I saw Owner of DirOne =