On Thu, Feb 2, 2012 at 9:18 AM, Diogo Resende <[email protected]>wrote:
> On Thu, 2 Feb 2012 09:04:04 -0500, Matt wrote: > >> Yeah, ReadStream can't do it without re-opening the file, because you >> need seek() to be able to get rid of the EOF flag, and Node doesn't >> implement seek() (partly because of the integer problem with getting >> up to 64 bits, but that's a bit of a cop-out since createReadStream >> can take start/end params, so why was it ok there?). The "tail" module >> on npm just re-opens the file if the size changes using >> fs.watchFile(). >> >> Probably easier (and faster) to open a childprocess to tail -f, since >> opening and closing a file all those times has an overhead. >> >> Matt. >> > > Yeah.. I was thinking about tail.. :) just 2 "questions". > > - Does Windows have any tail-like tool ? > There's one in the Windows Resource Kit. But nothing shipped with Windows. > - Are binary files a problem to tail in any way? > There's no concept of "binary files" on Unix systems (so basically, no problem). I have no idea about the Windows version. Matt. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
