Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Wed, 23 Jul 2003 16:11:00 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Samuel Thibault cc: cygwin AT cygwin DOT com, Subject: Re: bash: cat << EOF In-Reply-To: <20030719063849.GC7108@bouh.unh.edu> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Content-Disposition: INLINE On Sat, 19 Jul 2003, Samuel Thibault wrote: > Le sam 19 jui 2003 00:39:13 GMT, Christopher Faylor a tapot sur son clavier : > > On Fri, Jul 18, 2003 at 09:38:46PM -0400, Samuel Thibault wrote: > > >Hi, > > > > > >We have installed cygwin on w2k (5.00.2195 service pack 3), but the > > >files are actually hosted by a samba server, connected on S:\, and we > > >login to the box via rsh x11. > > > > > >The problem we're having is > > > > > >$ cat << EOF > > >> foo > > >> EOF > > >cat: -: Permission denied > > > > > >this is the same with dd, ... so the problem must be with bash. > > >I tried by copying bin/ on the local drive, relaunching bash.exe and > > >cat.exe from there, same problem, so it might not be because of the > > >networking thing. > > > > > >Is this a known limitation ? I couldn't find anything in the documentation > > >or the FaQ > > > > http://cygwin.com/problems.html > > Oops, sorry I missed cygcheck, here it is. Well, quoting your cygcheck output: > s:\arch\windows-i386\cygwin\bin\id.exe output (nontsec) > UID: 400(sthibaul) GID: 401(mkpasswd) > 401(mkpasswd) > > s:\arch\windows-i386\cygwin\bin\id.exe output (ntsec) > UID: 400(sthibaul) GID: 401(mkpasswd) > 545(Utilisateurs) 10513(mkgroup_l_d) > 401(mkpasswd) Basically, this means that your /etc/passwd and /etc/group files aren't up to date. Try updating them and re-running your command. Also, your strace output isn't useful, primarily because you weren't tracing the relevant parts of the command. You should have run strace -o trace bash -c "cat <