[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Ltib] [patch] Better logfile handling
From: |
Tom Moulton |
Subject: |
RE: [Ltib] [patch] Better logfile handling |
Date: |
Mon, 6 Jul 2009 16:03:58 -0400 |
Why not use tail -F host_config.log ?
The -F says to follow the file NAME not the file Handle
See also --retry which will tell tail to keep trying even if the file does
not exist
Tom
-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of Svein
Seldal
Sent: Monday, July 06, 2009 3:55 PM
To: address@hidden
Subject: [Ltib] [patch] Better logfile handling
Hi
I was annoyed by the fact that host_config.log was deleted whenever
--hostcf was run. If you had an ongoing tail running on that file, you'd
have to restart tail to get the new output.
The attached patch doesn't delete the log prior to use. It truncates the
file instead (which apps like tail is capable of detecting).
Please apply if found relevant/interesting.
BTW: I'm missing a similar logfile-feature like host_config.log for
target building, like target_config.log. Because this is only available
in --hostcf, isn't it?
To redirect/pipe ltib's output to file with or without tee will put a
lot of ncurses code into the log, which results in unreadable logs.
What do you think?
- Svein