Mail Archives: cygwin/2000/05/08/22:40:05
Subject: Re: perl scripts, file permissions, and external apps
> > Hi I have what is probably a pretty stupid question but
> > I've read the manuals, searched the archives etc and couldn't find
> > an answer. I'm updating perl scripts using gvim 5.6 for Win32 and
> > after saving my changes the permissions on the file change so
> > that I have to do a 'chmod 777 *.pl' to be able to execute them
> > again.
>
> I would like to get some more information. I wonder why you
> have no execute permission afterwards. This is uncommon when
> playing with permissions in plain NT.
>
> - Which version of the dll are you using?
I am using the new "net" release... There doesn't seem to be
one central cygwin.dll anymore.
09/13/1999 09:03p 118,254 cygitcl30.dll
09/13/1999 09:03p 64,116 cygitk30.dll
09/13/1999 09:03p 484,904 cygtcl80.dll
09/13/1999 09:03p 19,134 cygtclpip80.dll
09/13/1999 09:03p 24,570 cygtclreg80.dll
09/13/1999 09:19p 786,312 cygtk80.dll
03/01/2000 12:23a 600,576 cygwin1.dll
03/01/2000 12:23a 4,096 mingwc10.dll
09/13/1999 09:24p 279,570 tix4180.dll
> - What are the permissions of the parent directory of the files?
drwx------ 3 administ Administ 4096 May 4 00:15 scripts/
> - What are the permissions of the files before editing?
-rwxrwxrwx 1 administ Administ 1291 Apr 30 23:58 cc.pl*
-rwxrwxrwx 1 administ Administ 7202 May 4 00:15 crash_func.pl*
-rwxrwxrwx 1 administ Administ 1695 Mar 27 1999 mag.pl*
-rwxrwxrwx 1 administ Administ 934 Apr 30 23:50 rs.pl*
> - And after editing?
I edited crash_func.pl and saved it within vim:
-rwxrwxrwx 1 administ Administ 1291 Apr 30 23:58 cc.pl*
-rwx------ 1 administ Administ 7202 May 8 23:35 crash_func.pl*
-rwxrwxrwx 1 administ Administ 1695 Mar 27 1999 mag.pl*
-rwxrwxrwx 1 administ Administ 934 Apr 30 23:50 rs.pl*
I try to execute $perl crash_func.pl
and I get
Can't execute /cygdrive/d/util/scripts/crash_func.pl.
I do a chmod 777 and then I can execute...
Like I said in my previous post this could be complete
"pilot error".
>
> If you are using the net release 1.1, it would be best if
> you send the output of `getfacl' of the directory and an
> example file.
$ getfacl scripts/
# file: scripts/
# owner: 544
# group: 513
user::rwx
user:500:rwx
group::---
group:18:rwx
mask::---
other::---
default:user::---
default:user:500:---
default:group:18:---
default:mask::---
////////////////
$ getfacl crash_func.pl
# file: crash_func.pl
# owner: 544
# group: 513
user::rwx
user:500:rwx
group::---
group:18:rwx
mask::---
other::---
> No. vim for windows has no relation to the settings which
> are made in cygwin. Typically the permissions are _not_
> set. This has the result that the permissions which are
> set in the parent directory's ACL are used for new files.
> Unfortunately, vim erases the original file and writes the
> changes as a new file. No problem on U*Xish systems (like
> cygwin) but on plain NT.
I read that in their online docs and that's why I tried the different
"fileformat" settings hoping that would fix it.
>
> Why not trying vim for cygwin? It works as well as the win32
> version, hmm, ok, without mouse support, but who cares?
I don't use the mouse ( why use vi and a mouse??? :) ) but I
compile in some ATL code to drive Visual Studio from vim.
Thanks for answering...
--
B r i a n S t u r k E.E. / Software Eng.
http://www.nh.ultranet.com/~bsturk
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -