Re: taskkill - error while loading shared libraries - LD_LIBRARY_PATH?

On Mar 5 09:05, Robert Mark wrote: > Turns out it was my cygdrive mount was not being set properly. I was > changing the cygdrive mount in my own .bash_profile (via "mount > --change-cygdrive-prefix /") because at the time I was not admin of > the computer and couldn't edit /etc/profile or /etc/fs

Re: taskkill - error while loading shared libraries - LD_LIBRARY_PATH?

On Mar 5 10:08, Corinna Vinschen wrote: > On Mar 5 09:05, Robert Mark wrote: > > I fixed up the rights on Windows so I am admin now, /etc/fstab like so: > > none / cygdrive binary,posix=0,user 0 0 > > You don't have to run under an admin account. If the cygdrive prefix > is marked as "user" /e

Re: terminals getting killed on parent's termination

On 04.03.2010 08:49, Andy Koppe wrote: Thomas Wolff: Andy Koppe: Mintty has default handling for SIGHUP, i.e. it exits. Actually (another topic but related) mintty has a great feature here: it passed the SIGHUP to its client application and if that application catches and han

User Guide Suggestion

On , a link from the discussion of CYGWIN to would be convenient. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/pro

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Eric Blake wrote: According to Edward Lam on 1/21/2010 7:12 AM: DOS file paths and dash seems to NOT support them Huh? Give an example. dash supports DOS paths the same as bash. That is, if the : doesn't already cause other problems (as in tar), then the DOS path is handed on to native wind

symlinks: converting Windows shortcuts to cygwin style

Does someone have a script that converts symbolic links from "Windows shortcuts with a special header and the R/O attribute set" to "plain files with a magic number, a path and the system attribute set". (See "(no)winsymlinks" in .) Would i

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

On Mar 5 09:08, Edward Lam wrote: > Eric Blake wrote: > >According to Edward Lam on 1/21/2010 7:12 AM: > >>DOS file paths and dash seems to NOT support them > > > >Huh? Give an example. dash supports DOS paths the same as bash. That > >is, if the : doesn't already cause other problems (as in ta

Re: symlinks: converting Windows shortcuts to cygwin style

On Mar 5 09:11, Buchbinder, Barry (NIH/NIAID) [E] wrote: > Does someone have a script that converts symbolic links from "Windows > shortcuts with a special header and the R/O attribute set" to "plain files > with a magic number, a path and the system attribute set". (See > "(no)winsymlinks" in

Re: User Guide Suggestion

On Mar 5 09:00, Buchbinder, Barry (NIH/NIAID) [E] wrote: > On , a link from the > discussion of CYGWIN to > would be convenient. Done. Corinna -- Corinna Vinschen Please,

sshd starts but won't accept connections?

I recently installed sshd (using ssh-host-config and cygrunsrv) on an up-to-date cygwin on which the ssh client works. sshd starts, but when I try to access the cygwin sshd from other boxes on the LAN, their known-good ssh clients hang. How to fix? Details: The cygwin box runs winxp sp3 and is re

Re: sshd starts but won't accept connections?

On 3/5/2010 11:10 AM, Tom Roche wrote: So how to to make sshd on the cygwin box accept connections? Sounds like a firewall is getting in the way. Have you configured the firewall on your Windows machine to allow 'sshd' to use the port you've configured? -- Larry Hall

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Corinna Vinschen wrote: Is that a case-sensitivity issue, perhaps? See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive I don't see how it is: $ dash $ cd /c $ ls -d W* WINDOWS $ cd c:/WINDOWS cd: 3: can't cd to c:/WINDOWS $ cd C:/WINDOWS cd: 4: can't cd to C:/W

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Edward Lam wrote: Corinna Vinschen wrote: Is that a case-sensitivity issue, perhaps? See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive I don't see how it is: $ dash $ cd /c $ ls -d W* WINDOWS $ cd c:/WINDOWS cd: 3: can't cd to c:/WINDOWS $ cd C:/WINDOWS cd

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Edward Lam wrote: Edward Lam wrote: Corinna Vinschen wrote: Is that a case-sensitivity issue, perhaps? See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive I don't see how it is: $ dash $ cd /c $ ls -d W* WINDOWS $ cd c:/WINDOWS cd: 3: can't cd to c:/WINDOWS

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Corinna Vinschen wrote: Is that a case-sensitivity issue, perhaps? See http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive And in case you missed this the first time, it works fine in bash $ bash $ cd c:/ $ pwd /c $ export FOO=c:/windows $ cd $FOO $ pwd /c/windows

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

According to Edward Lam on 3/5/2010 9:55 AM: > Corinna Vinschen wrote: >> Is that a case-sensitivity issue, perhaps? See >> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive >> > > I don't see how it is: > > $ dash > $ cd /c > $ ls -d W* > WINDOWS > $ cd c:/WINDOWS

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

On Mar 5 10:10, Eric Blake wrote: > According to Edward Lam on 3/5/2010 9:55 AM: > > Corinna Vinschen wrote: > >> Is that a case-sensitivity issue, perhaps? See > >> http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive > >> > > > > I don't see how it is: > > > > $ das

Re: [ANNOUNCEMENT] [1.7] Updated: dash-0.5.5.1-2; Obsolete: ash

Corinna Vinschen wrote: On Mar 5 10:10, Eric Blake wrote: Let's rule out bash vs. dash complexities, and first focus on whether cygwin1.dll might be at fault. Untested code: #include #include #include #include int main(int argc, char**argv) { int e = chdir(argv[1]); char *cwd = getcwd

Re: sshd starts but won't accept connections?

Larry Hall (Cygwin cygwin.com> writes: > > So how to to make sshd on the cygwin box accept connections? > > Sounds like a firewall is getting in the way. Agreed. ssh -v or ssh -vv on the client may give you more information. On the server, try 'netstat -nabo | grep -A1 :22' to see if your ssh

Re: terminals getting killed on parent's termination

Thomas Wolff: >>> In general, a GUI application started in the background, like a terminal, >>> should detach itself from its parent process so that it survives if the >>> parent is terminated. >> >> Says who? > > Common practice in Unix/Linux/X environments. I've finally got round to trying to co

Re: terminals getting killed on parent's termination

Thomas Wolff: > Termination of a terminal's parent. This should not abort the terminal > session, whether or not the notification mechanism is HUP. (In the case > console -> xterm you said it's due to console attachment, whatever that > means in detail.) Well, in practical terms it means that xter

"cp: skipping file 'file.txt', as it was replaced while being copied"

I am getting the (apparently) classic error:  "cp: skipping file 'file.txt', as it was replaced while being copied" It only occurs on a  network drive (netapp, nfs), but not on another network drive (mac server, samba shares) I have search extensively and have found several references to this i

Re: "cp: skipping file 'file.txt', as it was replaced while being copied"

According to Roe, Kevin L. on 3/5/2010 2:48 PM: > I am getting the (apparently) classic error: "cp: skipping file 'file.txt', > as it was replaced while being copied" > > It only occurs on a network drive (netapp, nfs), but not on another network > drive (mac server, samba shares) More detail

RE: symlinks: converting Windows shortcuts to cygwin style

Corinna Vinschen sent the following at Friday, March 05, 2010 10:33 AM >On Mar 5 09:11, Buchbinder, Barry (NIH/NIAID) [E] wrote: >> Does someone have a script that converts symbolic links from "Windows >> shortcuts with a special header and the R/O attribute set" to "plain files >> with a magic n

Re: either nothing or cygheap base mismatch error

On Fri, Mar 5, 2010 at 11:01 PM, Eugen Zalinescu wrote: > On Fri, Mar 5, 2010 at 2:43 AM, Eugen Zalinescu > wrote: >> Hello, >> >> My problem is that I cannot start cygwin (with Cygwin.bat). Actually >> any cygwin application finishes as soon as I invoke it (or in about >> 1sec), with no output,

RE: "cp: skipping file 'file.txt', as it was replaced while being copied"

The system in question is disconnected from the internet and has no write to cd etc capability. That said, here is the output of the command you suggested: For the drive that works: Device Type: 7 Characteristics: 10 Max Filenamelength : 255 Filesystemname : Flags

Re: "cp: skipping file 'file.txt', as it was replaced while being copied"

Please keep the list in the loop: http://cygwin.com/acronyms/#PPIOSPE On 03/05/2010 03:10 PM, Roe, Kevin L. wrote: > The system in question is disconnected from the internet and has no write to > cd etc capability. > > That said, here is the output of the command you suggested: > > For the driv

RE: "cp: skipping file 'file.txt', as it was replaced while being copied"

Oops, sorry about the PPIOSPE mistake. Thanks for the suggestion. I'll try it out and let you know the result. -Kevin -Original Message- From: Eric Blake [mailto:ebl...@redhat.com] Sent: Friday, March 05, 2010 3:26 PM To: Roe, Kevin L.; cygwin Subject: Re: "cp: skipping file 'file.txt'

Re: either nothing or cygheap base mismatch error

On 3/5/2010 5:18 PM, Eugen Zalinescu wrote: My problem is that I cannot start cygwin (with Cygwin.bat). Actually any cygwin application finishes as soon as I invoke it (or in about 1sec), with no output, as in D:\cygwin\bin> bash D:\cygwin\bin> However, sometimes (I cannot reproduce the be

Re: sshd starts but won't accept connections?

Tom Roche 3/5/2010 11:10 AM >>> how to to make sshd on the cygwin box accept connections? Larry Hall (Cygwin) Fri, 05 Mar 2010 11:36:43 -0500 >> Have you configured the firewall on your Windows machine to allow >> 'sshd' to use the port you've configured? Andrew Schulman Fri, 5 Mar 2010 20:11:1

Re: terminals getting killed on parent's termination

Andy Koppe: > Thomas Wolff wrote: >> In general, a GUI application started in the background, like a terminal, >> should detach itself from its parent process so that it survives if the >> parent is terminated. > > Says who? You can always invoke it with setsid or some such to detach it. > >> I've

Fw: AddAccessAllowedAce(, owner) failed: 1337

- Original Message - From: "Stephen Grant Brown" To: "Stephen Grant Brown" Sent: Saturday, March 06, 2010 7:19 AM Subject: Re: AddAccessAllowedAce(, owner) failed: 1337 Hi Larry, - Original Message - From: "Stephen Grant Brown" Sent: Monday, February 22, 2010 11:14 PM Sub