Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
This may be one of the few cases where awk is the correct solution.
df -P | awk '/^\//{printf("%5s %s\n", $5, $6);}'
df -P | perl -ne 'printf("%5s %s\n", (split(/\s+/, $_))[4, 5])'
If you want to do a lot more formating; then I would write a complete perl program.

use Filesys::Statvfs; open MOUNTED, "</proc/mounts" || die "Could not open /proc/mounted\n"; while (my $mountpoint = <MOUNTED>) { my ($bsize, $blocks, $bfree, $bavail, $files, $ffree, $namelen); my $path = (split(/\s+/, $mountpoint))[1]; if (1) { ($ftype, $bsize, $blocks, $bfree, $files, $ffree, $bavail) = statvfs("/tmp"); } else { # This is not very portable my $buf = "\0"x64; syscall(99, $path, $buf) == 0 or die "Bad mountpoint $path\n"; ($bsize, $blocks, $bfree, $bavail, $files, $ffree, $namelen) = unpack "x4 L6 x8 L", $buf; } next unless $blocks; print <<EOT; path: $path Optimal transfer block size: $bsize Blocks in file system: $blocks Blocks free: $bfree (${\(int $bfree/$blocks*100)} +%) User blocks available: $bavail (${\(int $bavail/$blocks*100 +)}%) Inodes: $files Free inodes: $ffree (${\(int $ffree/$files*100)}% +) EOT }
-- gam3
A picture is worth a thousand words, but takes 200K.

In reply to Re: disk space utilization by gam3
in thread disk space utilization by ministry

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.