Sponsored Content
Full Discussion: Problem with a BDF script...
Top Forums Shell Programming and Scripting Problem with a BDF script... Post 302513914 by zixzix01 on Thursday 14th of April 2011 10:15:43 AM
Old 04-14-2011
Problem with a BDF script...

Hi,

I'm trying to use an old script I found of the internet a while back, I forget where its from. Its supposed to convert the bdf function and display filesystem size in MB's and line it up however it never worked...

Here is the error:

Quote:
./bdf.sh
Filesystem Mbytes used avail %used Mounted on
syntax error The source line is 2.
The error context is
{ printf("%s %10d %10d %10d %4s %s\n",$1,$2/1 >>>
<<<
awk: The statement cannot be correctly parsed.
The source line is 2.
And here is the code:

Code:
#!/usr/bin/sh

echo "Filesystem          Mbytes       used      avail %used Mounted on"

bdf $1 | grep -v Filesystem | awk '{ printf("%s %10d %10d %10d %4s  %s\n",$1,$2/1
024,$3/1024,$4/1024,$5,$6)}'

Can someone help me make sense of this?

Thanks
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

BDF test for > 90%

I am trying to write a script that will allow me to do a bdf then do a test for a percentage that is 90% or greater. If the test is true then i want to send a message to myself and one other person. Any suggestions ? ? ? Thanks. ....svp (6 Replies)
Discussion started by: svp4444
6 Replies

2. Shell Programming and Scripting

bdf script not working !!

Hi, I have written a funtion which taken bdf output and put's in a file. The idea is to grep a areas which greater then 80% and echo the same on the system. However the script I have written fails with the error :- + awk $0 !~ /^F/ + awk {print $5"\t" $6} + sed s/%// + 1> /tmp/bdflist}... (3 Replies)
Discussion started by: kpatel786
3 Replies

3. UNIX for Advanced & Expert Users

bdf question

Hi all i am working on script which uses "bdf" output to create excel sheet now when i check "Total" "Used" & "Available" i found that except root everywhere used + available != total here is example : part from bdf output : filesystem-total-used-available-%used-Mounted on ... (4 Replies)
Discussion started by: zedex
4 Replies

4. Shell Programming and Scripting

bdf error

I have this line in a sh script: bdf | grep /var/opt/vgdb | tr -s " " | cut -f4,6 -d" " | awk '{print $2" "$1}' > vgdb_free_space.txt if I run that line in the shell it works fine but when I ran the script got this error: add_database_files.sh: line 83: bdf: command not found also I tried... (4 Replies)
Discussion started by: C|KiLLeR|S
4 Replies

5. Shell Programming and Scripting

Bdf output

Here is my bdf output #bdf Filesystem kbytes used avail %used Mounted on /dev/vg00/lvol3 2097152 217112 1865424 10% / /dev/vg00/lvol1 1835008 329040 1494288 18% /stand /dev/vg00/lvol7 10485760 7864080 2601240 75% /var /dev/vg00/lvol8 8454144 486597 7469647 ... (5 Replies)
Discussion started by: indrajit_renu
5 Replies

6. Shell Programming and Scripting

BDF Panic script...

I have another script which I found also on the net. I keep getting an error:confused:: Here is the script for it: {/usr/bin/bdf -l |awk '$0 !~ /^F/' |awk '{print $5"\t" $6}'| sed 's/'%'//' >/tmp/b dflist} panic () {while read percent dir; do if ] then ... (16 Replies)
Discussion started by: zixzix01
16 Replies

7. UNIX for Advanced & Expert Users

HP-UX: Problem viewing directory with BDF...

Hi all, When I use BDF command on this particular server, it outputs mostly normal stuff. However, there is one directory it can't read at all. Also, it doesn't seem to exist. When I BDF my file system with a small panic script (it happens even if you use just the bdf command): As you... (17 Replies)
Discussion started by: zixzix01
17 Replies

8. HP-UX

bdf hangs

hi, bdf command hangs but before it, it lists all the fstab content, so i cannot find the reason... could anybody give me any clue?? thanks a lot for your attention. regards Pablo i attach syslog Jan 14 16:30:00 sv23 vmunix: hp_dlpi_wput:Received an unrecognized primitive: 101d... (7 Replies)
Discussion started by: pabloli150
7 Replies

9. Shell Programming and Scripting

Using the output of bdf in script

Hello all, First I have an old HP-UX box(11.21) for which I need to implement file-system utilization monitoring. I choosed to use bdf and a simple for loop. However sometimes the output of bdf is as this one(this is actually form linux but the idea is the same) Filesystem ... (4 Replies)
Discussion started by: click
4 Replies

10. HP-UX

Bdf in HP-UX

Hi guys, I have to make an output of several databases we've got running on our system with the command bdf. This has to be done every 3 months. I want to put it in an scriptfile and trigger it in crontab. In the output it must display the differences in diskspace between these three monts. Any... (3 Replies)
Discussion started by: djmental
3 Replies
TMPFILES.D(5)							    tmpfiles.d							     TMPFILES.D(5)

NAME
tmpfiles.d - Configuration for creation, deletion and cleaning of volatile and temporary files SYNOPSIS
/etc/tmpfiles.d/*.conf /run/tmpfiles.d/*.conf /usr/lib/tmpfiles.d/*.conf DESCRIPTION
systemd-tmpfiles uses the configuration files from the above directories to describe the creation, cleaning and removal of volatile and temporary files and directories which usually reside in directories such as /run or /tmp. CONFIGURATION FORMAT
Each configuration file shall be named in the style of package.conf or package-part.conf. The second variant should be used when it is desirable to make it easy to override just this part of configuration. Files in /etc/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d and /run/tmpfiles.d. Files in /run/tmpfiles.d override files with the same name in /usr/lib/tmpfiles.d. Packages should install their configuration files in /usr/lib/tmpfiles.d. Files in /etc/tmpfiles.d are reserved for the local administrator, who may use this logic to override the configuration files installed by vendor packages. All configuration files are sorted by their filename in lexicographic order, regardless of which of the directories they reside in. If multiple files specify the same path, the entry in the file with the lexicographically earliest name will be applied, all all other conflicting entries logged as errors. If the administrator wants to disable a configuration file supplied by the vendor, the recommended way is to place a symlink to /dev/null in /etc/tmpfiles.d/ bearing the same filename. The configuration format is one line per path containing type, path, mode, ownership, age, and argument fields: #Type Path Mode UID GID Age Argument d /run/user 0755 root root 10d - L /tmp/foobar - - - - /dev/null Type The type consists of a single letter and optionally an exclamation mark. The following line types are understood: f Create a file if it does not exist yet. If the argument parameter is given, it will be written to the file. F Create or truncate a file. If the argument parameter is given, it will be written to the file. w Write the argument parameter to a file, if the file exists. Lines of this type accept shell-style globs in place of normal path names. The argument parameter will be written without a trailing newline. C-style backslash escapes are interpreted. d Create a directory if it does not exist yet. D Create or empty a directory. p Create a named pipe (FIFO) if it does not exist yet. L Create a symlink if it does not exist yet. c Create a character device node if it does not exist yet. b Create a block device node if it does not exist yet. m If the specified file path exists adjust its access mode, group and user to the specified values and reset the SELinux label. If it doesn't exist do nothing. x Ignore a path during cleaning. Use this type to exclude paths from clean-up as controlled with the Age parameter. Note that lines of this type do not influence the effect of r or R lines. Lines of this type accept shell-style globs in place of normal path names. X Ignore a path during cleaning. Use this type to exclude paths from clean-up as controlled with the Age parameter. Unlike x, this parameter will not exclude the content if path is a directory, but only directory itself. Note that lines of this type do not influence the effect of r or R lines. Lines of this type accept shell-style globs in place of normal path names. r Remove a file or directory if it exists. This may not be used to remove non-empty directories, use R for that. Lines of this type accept shell-style globs in place of normal path names. R Recursively remove a path and all its subdirectories (if it is a directory). Lines of this type accept shell-style globs in place of normal path names. z Restore SELinux security context label and set ownership and access mode of a file or directory if it exists. Lines of this type accept shell-style globs in place of normal path names. Z Recursively restore SELinux security context label and set ownership and access mode of a path and all its subdirectories (if it is a directory). Lines of this type accept shell-style globs in place of normal path names. If the exclamation mark is used, this line is only safe of execute during boot, and can break a running system. Lines without the exclamation mark are presumed to be safe to execute at any time, e.g. on package upgrades. systemd-tmpfiles will execute line with an exclamation mark only if option --boot is given. For example: # Make sure these are created by default so that nobody else can d /tmp/.X11-unix 1777 root root 10d # Unlink the X11 lock files r! /tmp/.X[0-9]*-lock The second line in contrast to the first one would break a running system, and will only be executed with --boot. Path The file system path specification supports simple specifier expansion. The following expansions are understood: Table 1. Specifiers available +----------+----------------+-------------------------------------+ |Specifier | Meaning | Details | +----------+----------------+-------------------------------------+ |"%m" | Machine ID | The machine ID of the running | | | | system, formatted as string. See | | | | machine-id(5) for more information. | +----------+----------------+-------------------------------------+ |"%b" | Boot ID | The boot ID of the running system, | | | | formatted as string. See random(4) | | | | for more information. | +----------+----------------+-------------------------------------+ |"%H" | Host name | The hostname of the running system. | +----------+----------------+-------------------------------------+ |"%v" | Kernel release | Identical to uname -r output. | +----------+----------------+-------------------------------------+ |"%%" | Escaped % | Single percent sign. | +----------+----------------+-------------------------------------+ Mode The file access mode to use when creating this file or directory. If omitted or when set to -, the default is used: 0755 for directories, 0644 for all other file objects. For z, Z lines, if omitted or when set to "-", the file access mode will not be modified. This parameter is ignored for x, r, R, L lines. UID, GID The user and group to use for this file or directory. This may either be a numeric user/group ID or a user or group name. If omitted or when set to "-", the default 0 (root) is used. For z, Z lines, when omitted or when set to -, the file ownership will not be modified. These parameters are ignored for x, r, R, L lines. Age The date field, when set, is used to decide what files to delete when cleaning. If a file or directory is older than the current time minus the age field, it is deleted. The field format is a series of integers each followed by one of the following postfixes for the respective time units: s, min, h, d, w, ms, m, us If multiple integers and units are specified, the time values are summed up. If an integer is given without a unit, s is assumed. When the age is set to zero, the files are cleaned unconditionally. The age field only applies to lines starting with d, D, and x. If omitted or set to "-", no automatic clean-up is done. If the age field starts with a tilde character "~", the clean-up is only applied to files and directories one level inside the directory specified, but not the files and directories immediately inside it. Argument For L lines determines the destination path of the symlink. For c, b determines the major/minor of the device node, with major and minor formatted as integers, separated by ":", e.g. "1:3". For f, F, and w may be used to specify a short string that is written to the file, suffixed by a newline. Ignored for all other lines. EXAMPLE
Example 1. /etc/tmpfiles.d/screen.conf example screen needs two directories created at boot with specific modes and ownership. d /var/run/screens 1777 root root 10d d /var/run/uscreens 0755 root root 10d12h Example 2. /etc/tmpfiles.d/abrt.conf example abrt needs a directory created at boot with specific mode and ownership and its content should be preserved. d /var/tmp/abrt 0755 abrt abrt x /var/tmp/abrt/* SEE ALSO
systemd(1), systemd-tmpfiles(8), systemd-delta(1) systemd 208 TMPFILES.D(5)
All times are GMT -4. The time now is 12:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy