Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-19 Thread Corinna Vinschen
On Dec 18 21:08, Eric Blake wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 According to Igor Peshansky on 12/18/2007 11:58 AM:
  I bet that if you did post one, it would show that your Cygwin is
  installed on either FAT or FAT32, not NTFS.  That, and the DOS Read-only
  bit on the directory is probably set.  Another (less likely) alternative
  is that you've installed on a network drive.
 
 Wasn't there a recent thread on this issue, and wasn't it fixed so that
 cygwin 1.5.25-7 reports directories as writable in spite of the DOS
 read-only attribute bit?

Right, that should be fixed in 1.5.25-7.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-18 Thread Igor Peshansky
On Tue, 18 Dec 2007, Michael Kairys wrote:

 Larry Hall (Cygwin) [EMAIL PROTECTED] wrote in message
 news:[EMAIL PROTECTED]

http://cygwin.com/acronyms/#PCYMTNQREAIYR.  Thanks.

  http://cygwin.com/faq/faq-nochunks.html#faq.using.chmod

 Thanks... I read with partial understanding but could not come up with any
 action items...

 My resolution was to verify that my temp is in fact writeable and then
 comment out the check in rebaseall.
 So far so good: no fork failures.

I'm guessing one can reconstruct your permissions as follows:

$ cd /tmp
$ mkdir nw
$ setfacl -m g:Users:rwx nw
$ chmod a-rwx nw
$ ls -ld nw
d-+ 2 igor root 0 Dec 18 10:08 nw/
$ touch nw/foo
$ ls -l nw/foo
-rw--- 1 igor root 0 Dec 18 10:08 nw/foo
$ if [ -w nw ]; then echo Yes; else echo No; fi
No
$

One solution is, of course, chmod u+rwx /tmp.  The other is to change
rebaseall to try creating a file anyway and checking the result.

There was some talk of changing coreutils to use access for testing
permissions, which would probably solve this as well.  However, even if I
use /bin/test -w nw, I get a No.  Has this change ever happened?  If
it ever does, bash will also need to be rebuilt so that its builtins use
the same interface.  It helps that both have the same maintainer.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

That which is hateful to you, do not do to your neighbor.  That is the whole
Torah; the rest is commentary.  Go and study it. -- Rabbi Hillel

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-18 Thread Michael Kairys


Igor Peshansky [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]



I'm guessing one can reconstruct your permissions as follows:

$ cd /tmp
$ mkdir nw
$ setfacl -m g:Users:rwx nw
$ chmod a-rwx nw
$ ls -ld nw
d-+ 2 igor root 0 Dec 18 10:08 nw/
$ touch nw/foo
$ ls -l nw/foo
-rw--- 1 igor root 0 Dec 18 10:08 nw/foo
$ if [ -w nw ]; then echo Yes; else echo No; fi
No
$


Not sure about the setfacl but I note that if I repeat your sequence I get 
dr-xr-xr-x, which is what all my dirs look like:


1  cd /tmp
2  mkdir nw
3  setfacl -m g:Users:rwx nw
4  chmod a-rwx nw
5  ls -ld nw
dr-xr-xr-x 2 michael None 0 Dec 18 11:46 nw
6  touch nw/foo
7  ls -l nw/foo
-rw-r--r-- 1 michael None 0 Dec 18 11:47 nw/foo
8  if [ -w nw ]; then echo Yes; else echo No; fi
No


One solution is, of course, chmod u+rwx /tmp.


Well, this has no effect for me:

9  ls -ld /tmp
dr-xr-xr-x 9 michael None 245760 Dec 18 11:46 /tmp
10  chmod u+rwx /tmp
11  ls -ld /tmp
dr-xr-xr-x 9 michael None 245760 Dec 18 11:46 /tmp




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-18 Thread Igor Peshansky
On Tue, 18 Dec 2007, Michael Kairys wrote:

 Igor Peshansky [EMAIL PROTECTED] wrote in message
 news:[EMAIL PROTECTED]

Again, http://cygwin.com/acronyms/#PCYMTNQREAIYR.  Thanks.

  I'm guessing one can reconstruct your permissions as follows:
 
  $ cd /tmp
  $ mkdir nw
  $ setfacl -m g:Users:rwx nw
  $ chmod a-rwx nw
  $ ls -ld nw
  d-+ 2 igor root 0 Dec 18 10:08 nw/
  $ touch nw/foo
  $ ls -l nw/foo
  -rw--- 1 igor root 0 Dec 18 10:08 nw/foo
  $ if [ -w nw ]; then echo Yes; else echo No; fi
  No
  $

 Not sure about the setfacl but I note that if I repeat your sequence I get
 dr-xr-xr-x, which is what all my dirs look like:

 1  cd /tmp
 2  mkdir nw
 3  setfacl -m g:Users:rwx nw
 4  chmod a-rwx nw
 5  ls -ld nw
 dr-xr-xr-x 2 michael None 0 Dec 18 11:46 nw
 6  touch nw/foo
 7  ls -l nw/foo
 -rw-r--r-- 1 michael None 0 Dec 18 11:47 nw/foo
 8  if [ -w nw ]; then echo Yes; else echo No; fi
 No

  One solution is, of course, chmod u+rwx /tmp.

 Well, this has no effect for me:

 9  ls -ld /tmp
 dr-xr-xr-x 9 michael None 245760 Dec 18 11:46 /tmp
 10  chmod u+rwx /tmp
 11  ls -ld /tmp
 dr-xr-xr-x 9 michael None 245760 Dec 18 11:46 /tmp

Heh.  I just looked, and it seems you've never posted the output of
cygcheck -svr on your system as requested in

 Problem reports:   http://cygwin.com/problems.html

I bet that if you did post one, it would show that your Cygwin is
installed on either FAT or FAT32, not NTFS.  That, and the DOS Read-only
bit on the directory is probably set.  Another (less likely) alternative
is that you've installed on a network drive.

If it's FAT32, you're out of luck.  In other cases you would probably
benefit from reviewing http://cygwin.com/cygwin-ug-net/ntsec.html.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED] | [EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_Igor Peshansky, Ph.D. (name changed!)
 |,4-  ) )-,_. ,\ (  `'-'   old name: Igor Pechtchanski
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

That which is hateful to you, do not do to your neighbor.  That is the whole
Torah; the rest is commentary.  Go and study it. -- Rabbi Hillel

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-18 Thread Michael Kairys


Igor Peshansky [EMAIL PROTECTED] wrote in message 
news:[EMAIL PROTECTED]



Heh.  I just looked, and it seems you've never posted the output of
cygcheck -svr on your system ...


Well, I didn't think I was reporting a problem except possibly with my own 
understanding...



I bet ... the DOS Read-only bit on the directory is probably set.


Bingo!

Having changed that, I get:


ls -ld /tmp

drwxr-xr-x 12 michael None 245760 Dec 18 14:26 /tmp

... and...


if [ -w /tmp ]; then echo Yes; else echo No; fi
Yes 




--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/



Re: Intermittent perl crash (Attn: coreutils and bash maintainer)

2007-12-18 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to Igor Peshansky on 12/18/2007 11:58 AM:
 I bet that if you did post one, it would show that your Cygwin is
 installed on either FAT or FAT32, not NTFS.  That, and the DOS Read-only
 bit on the directory is probably set.  Another (less likely) alternative
 is that you've installed on a network drive.

Wasn't there a recent thread on this issue, and wasn't it fixed so that
cygwin 1.5.25-7 reports directories as writable in spite of the DOS
read-only attribute bit?  Without cygcheck output, I can't guarantee which
version of cygwin this problem was against; but I still suspect that it is
with cygwin itself and not coreutils/bash.

- --
Don't work too hard, make some time for fun as well!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin coreutils/bash maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHaJk784KuGfSFAYARAn78AKCAiWlleKWvVPGlIxuLA0V2U6w+CQCfb6WD
MeLqeoxUUkXDz7tOrJRSvzI=
=iXMi
-END PGP SIGNATURE-

--
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple
Problem reports:   http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ:   http://cygwin.com/faq/