On Saturday, February 14, 2004 1:51 PM [EST], Brian Bruns <[EMAIL PROTECTED]> wrote:
> Well, heres the question - is this just a matter of setting the right env > flags? I could have sworn that cygwin works in unix line ending mode by > default. You also have the issue of either binary or ascii mount points > (and cygwin IIRC does binary mount points by default too). I guess I'll go > documentation diving. > > This is what I [EMAIL PROTECTED]@[EMAIL PROTECTED] hate about Windows. It does > literally EVERYTHING > different from the rest of the world such to a point that even cygwin can't > compensate all the time for it. > > The question is, should we force it into DOS LF mode, or UNIX LF mode? I'd > say for compatibility reasons, UNIX LF mode. > Ok, did some reading - cygwin is a big stickler for having the right flags when opening a file. It seems that the O_BINARY patch is gone in the current version? The people who are having problems with clamd/clamdscan, can you try accessing the file that you were using to test in the following ways: C:/path/to/file C:\\path\\to\\file and see if it properly scans this time? -- Brian Bruns The Summit Open Source Development Group Open Solutions For A Closed World / Anti-Spam Resources http://www.sosdg.org The Abusive Hosts Blocking List http://www.ahbl.org ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
