[please keep the list in the loop]
On 10/04/2010 08:54 AM, Alain Knaff wrote:
One thing that might be possible, however, is to improve df output to
adjust column alignment if $COLUMNS
Rather than using $COLUMNS (which is not set by all shells...), it might
be preferable to do an ioctl(1, TIOCG
On 10/04/2010 03:44 AM, Alain Knaff wrote:
There is an option to prevent this behavior (-P), but apparently the
logwatch authors were not aware of it. Understandably, I might say,
because if their test cases happen to only have disks with short names,
they'll never stumble upon this.
Thanks for
Hello,
We just had a case where an overfull disk went unnoticed by logwatch.
The reason turned out to be its long device name (/dev/mapper
/VolGroup00-LogVol00), which caused df to break the line, messing up
the column count. Indeed, logwatch looks for the use% in the fifth
field, but due to this
