bad install ?

I can't figure out what I have done or not done to make .sh scripts NOT run in my seemingly ok cygwin install. My script.sh #!/bin/bash PATH=/bin:/usr/bin echo OK # bash -x script.sh + PATH=$'/bin:/usr/bin\r' + $'\r' : command not found + $'\r' : command not found Is it a Unix - DOS thing ? Tha

Re: tail and win file handling

I can't change the application unfortunately, if I could I'd have it only log interesting stuff rather than the garbage it does. Is it worth trying maybe to link the file and tail the link ? or mess with a tee command ?? --- Larry Hall <[EMAIL PROTECTED]> wrote: > re tail and win file handles. >

tail and win file handling

I am sorry if this has been covered before, but I was wondering if there is work around (probably not ;-( In unix you can do the following tail -f /somefile in another session rm -f /somefile echo OK > /somefile of course the tail stops working, but the file is recreated On a cygwin box tail -f

write to remote syslogd

I know you can set syslog.conf to point to a remote syslog daemon, so if you use logger it will get copied to the remote syslogd, however is there a command in cygwin (or linux for that matter) that you can use to send a syslog message directly to a remote syslogd ? logger seems to write to only to

Command line mail w/attachment

What is the simplest way to send email from the command line, so that I can mime attach files (html, binary, etc). I would like to specify everything on the command line, because I don't know how to configure sendmail. I just need to call the email sending mechanism from a cygwin bash script. Ideas

Re: Dueling cygwin DLLs

I knew that solution, but I have inherited 40 scripts clocking in at 5 meg by departed staff. Tell me the hard way. I wish it were easier to run a cmdline util cygwin or other to yield cpu mem stats on win. Thanks > > DLL caused many other scripts to fail. I can't > debug > > the ones it affected

Dueling cygwin DLLs

I needed a new newer cygwin1.dll in order to run the top utility in procps, but its replacement of an older DLL caused many other scripts to fail. I can't debug the ones it affected. Is there a way to have the top executeable call the new cygwin1.dll called cygwin2.dll so it can "find an entry poin