tail with line feed delimination

[cookspyder]

Im trying to tail a file that does not have hard returns but has line feeds after each entry. Is there a way to change the standard file tail settings to look for line feeds when tailing?

[cookspyder]

I know how to do this to the entire file via the unix2dos commands in order for tail to work properly.

Im wondering if I can change the file as it is written? That would be ideal in order to provide a working tail. Otherwise to change the line feed to a hard return right before it gets tailed.

Not sure if this would even be possible but it would save alot of time if I could.

[numberwhun]

So what is writing this file? Is it a program? Is it Perl? Just curious.

Regards,

Jeff

[cookspyder]

Its a program on a unix system and between each write it puts in two line feeds.

The File tail module doesn't understand line feeds as the end of a line and will read through the entire file as one line.

So, since I cant get the app to write the log entries with a hard return I'm stuck trying to find a way to manipulate the file prior to tailing it.

[numberwhun]

As far as you mentioned earlier about changing the way the program writes, that solution would be up to you to research as this is a Perl forum. Otherwise, you could create a script that would translate the single line feed into what you want it to have.

ie:

s/pattern/replacement/g

Something like that, but for each line in the file. Is it the Unix version you want (single line feed) or the dos version (carraige return/line feed)? Either way, if unix2dos works for you, why not write a Perl script that utilizes it and simply feeds each file name through it?

Regards,

Jeff

[KevinADC]

maybe if you redefine the input record seperator before trying to tail the file it will work:

$/ = "\r\r";

or whatever two line feeds is. Might want to wrap that in a block and use "local" so it dos not affect therest of your program if there is any:

{
local $/ = "\r\r";
your tail code here
}

[miller]

According to the Tail::File module docs:

TO BE DONE

Planned for 1.0: Using $/ instead of \n to separate "lines" (which should make it possible to read wtmp type files). Except that I discovered I have no need for that enhancement If you do, feel free to send me the patches and I'll apply them - if I feel they don't add too much processing time.

If I were you, I would therefore download this module, and edit the source in order to work with $/ instead of a hardcoded \n. However, this may be beyond the skill or interest you have for this project.

It's also possible that this module would work as is using the "tie'd" method described in the docs along with $/. I kinda of doubt it though.

That's all I have to suggest.

- Miller