[brlug-general] [SAGE] df breaks scripts

[Dustin Puryear]

This may be true: "People who shortened device to dev might not think 
that '/dev/mapper/VolGroup00-LogVol00' is a sane device name." However, 
that's a default that Red Hat/CentOS uses when doing LVM so it would be 
nice if the df on Red Hat/CentOS handled it well. :)

The problem with Filesys::DiskSpace is that it doesn't address the core 
issue here: Most existing scripts expect df to act in a certain way..

So far, the only solution we've been able to come up with is a wrapper 
for df that forces -P.

--
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com

Author, "Best Practices for Managing Linux and UNIX Servers"
   http://www.puryear-it.com/pubs/linux-unix-best-practices

Identity Management, LDAP, and Linux Integration


willhill wrote:
> People who shortened device to dev might not think 
> that "/dev/mapper/VolGroup00-LogVol00" is a sane device name.  
> 
> Have you looked at perl's Filesys::DiskSpace?  I ran into it here:
> 
> http://www.cyberciti.biz/tips/howto-write-perl-script-to-monitor-disk-space.html
> 
> A similar dissaster happened to g77, where the print output was automatically 
> line broken to 80 columns.  This broke every loop formated code.  I'm not 
> sure how that one turned out because I've done everything in C since.
> 
> On Monday 04 February 2008 10:43 am, Dustin Puryear wrote:
>> But I think you're missing the point. Since days of yore, people have
>> generally used 'df' with the assumption that it had sane output by
>> default. ;)
> 
> _______________________________________________
> General mailing list
> General at brlug.net
> http://mail.brlug.net/mailman/listinfo/general_brlug.net