Alvaro,

'df -P' makes the output of 'df' conform to POSIX standards, where devices with 
long (>20 chars) names are printed on one line. It also changes the column 
lables. See 'info df' for details.

John Hebert

----- Original Message ----
From: Alvaro Zuniga <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, February 4, 2008 4:01:53 PM
Subject: Re: [brlug-general] [SAGE] df breaks scripts


Now 
I 
am 
really 
confused 
here, 
-P 
deals 
with 
the 
512-byte 
block 
right?
so 
what 
happened 
to 
the 
formatting 
problem? 
So 
I 
am 
really, 
really 
confused 
now. 
Must 
be 
some 
kind 
of 
sysadmin 
talk. 


On 
Mon, 
Feb 
04, 
2008 
at 
02:59:02PM 
-0600, 
Dustin 
Puryear 
wrote:
> 
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
> 
> 
[email protected]
> 
> 
http://mail.brlug.net/mailman/listinfo/general_brlug.net
> 
> 
_______________________________________________
> 
General 
mailing 
list
> 
[email protected]
> 
http://mail.brlug.net/mailman/listinfo/general_brlug.net

_______________________________________________
General 
mailing 
list
[email protected]
http://mail.brlug.net/mailman/listinfo/general_brlug.net





      
____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

_______________________________________________
General mailing list
[email protected]
http://mail.brlug.net/mailman/listinfo/general_brlug.net

Reply via email to