Re: rm prints no errmsg if _unlink fails with errno 32

Pierre A. Humblet schrieb: On Thu, Jun 03, 2004 at 09:08:47PM +0200, Reini Urban wrote: Reini Urban schrieb: (latest cygwin release 1.5.10-3 and fileutils-4.1-2) rm printed no errmsg if _unlink failed with errno 32. Pierre ping? Should I patch it by myself? But I don't know where. The syscall fails

Re: rm prints no errmsg if _unlink fails with errno 32

On Thu, Jun 03, 2004 at 09:08:47PM +0200, Reini Urban wrote: > Reini Urban schrieb: > >(latest cygwin release 1.5.10-3 and fileutils-4.1-2) > >rm printed no errmsg if _unlink failed with errno 32. > > Pierre ping? > > Should I patch it by myself? But I don't know where. > The syscall fails, but i

Re: rm prints no errmsg if _unlink fails with errno 32

Reini Urban schrieb: (latest cygwin release 1.5.10-3 and fileutils-4.1-2) rm printed no errmsg if _unlink failed with errno 32. Pierre ping? Should I patch it by myself? But I don't know where. The syscall fails, but is not responsible for any errormessage to STDERR. And rm gets a wrong status code

rm prints no errmsg if _unlink fails with errno 32

NTFS problems with _unlink (latest cygwin release 1.5.10-3 and fileutils-4.1-2) rm printed no errmsg if _unlink failed with errno 32. The file was still there. $ touch xx $ chmod 400 xx $ rm xx # prints a (localized) warning and prompt without the rm -f parameter. # which seems to be the expected b