How do you monitor disk space on unix systems?

There exists several ways how you can obtain free disk space quote from a remote UNIX system. FYI here are two example methods, one is using 24x7 UNIX remote automation server and another using plain Telnet.

Create new job in 24x7 of script type. Here is an example script:

Dim( process_id, number )
Dim( output, string )
RAConnect( "server name or IP address", 1096, "user name", "valid password" )
RARunAndWait( "df -k", 0, process_id, output )
RADisconnect( )

The format of the returned df command output differs on different UNIX systems. Please add "MessageBox output" at the end of the script or run the job in Debugger to see how your system reports free space. You will need to some straight forward code to extract from the output string the actual numbers and also code some actions that you want to perform in case if the space is low.

Please note that this script requires 24x7 Remote Automation Server (24x7 RA Server) installed on the UNIX system. You can do a similar thing without (24x7 RA Server) using appropriate Telnet commands. Example:

TelnetOpen( "my server", "my user name", "my password" )
TelnetSend( "df -k" )
Wait( 10 )
TelnetReceive( output )
TelnetClose( )

: How do you monitor disk space on unix systems?

I tried the telnet option, but recieve timeout errors. I can open the telnet session from a command line without any problem. When I plug in my information into the sample script I never recieve a login prompt.

Is any issue using this product on Windows 2000?

: There exists several ways how you can obtain free disk space quote from a
: remote UNIX system. FYI here are two example methods, one is using 24x7
: UNIX remote automation server and another using plain Telnet.

: Create new job in 24x7 of script type. Here is an example script: Dim(
: process_id, number )
: Dim( output, string )
: RAConnect( "server name or IP address", 1096, "user
: name", "valid password" )
: RARunAndWait( "df -k", 0, process_id, output )
: RADisconnect( )

: The format of the returned df command output differs on different UNIX
: systems. Please add "MessageBox output" at the end of the script
: or run the job in Debugger to see how your system reports free space. You
: will need to some straight forward code to extract from the output string
: the actual numbers and also code some actions that you want to perform in
: case if the space is low.

: Please note that this script requires 24x7 Remote Automation Server (24x7 RA
: Server) installed on the UNIX system. You can do a similar thing without
: (24x7 RA Server) using appropriate Telnet commands. Example: TelnetOpen(
: "my server", "my user name", "my password" )
: TelnetSend( "df -k" )
: Wait( 10 )
: TelnetReceive( output )
: TelnetClose( )

Insert TelnetConfig("TERMINAL", "SHOW") in the beginning of the script to see where it gets stock. Most likely you need to use TelnetConfig to tell 24x7 what your login or password prompt is, if it is different from the default values. Please TelnetConfig topic in the on-line help for more details.

: I tried the telnet option, but recieve timeout errors. I can open the telnet
: session from a command line without any problem. When I plug in my
: information into the sample script I never recieve a login prompt.

: Is any issue using this product on Windows 2000?

Still no luck.

I'm attempting to connect to an rs/6000. I cannot get a login prompt to show up and the telnet connection times out. Again, I have no problem connecting thru any of my other terminal emulaters.

The IBM host does send some connection information back to the client ahead of the login prompt. Could this be interfering in some way?

: Insert TelnetConfig("TERMINAL", "SHOW") in the beginning
: of the script to see where it gets stock. Most likely you need to use
: TelnetConfig to tell 24x7 what your login or password prompt is, if it is
: different from the default values. Please TelnetConfig topic in the
: on-line help for more details.

You need to include it as a part of the expected "login prompt". The prompt is a kind of virtual filter invented in 24x7 because standard Telnet protocol lacks login commands. The "prompt" can have many lines and be as long as needed.

: Still no luck.

: I'm attempting to connect to an rs/6000. I cannot get a login prompt to show
: up and the telnet connection times out. Again, I have no problem
: connecting thru any of my other terminal emulaters.

: The IBM host does send some connection information back to the client ahead
: of the login prompt. Could this be interfering in some way?

I give up!!

After the telnet open times out, should I be able to press the connect button and see a valid login prompt come back if I leave the username and password empty? I can't even get the telnet client to give me a basic prompt.....

: You need to include it as a part of the expected "login prompt".
: The prompt is a kind of virtual filter invented in 24x7 because standard
: Telnet protocol lacks login commands. The "prompt" can have many
: lines and be as long as needed.

Turn on the tracing option in the Tools/Options, Log tab, "Trace Enabled" check box. This will cause all Telnet commands and data saved in the Telnet.log file in 24x7 installation directory. This is a plain text file which you can conveniently read in the Notepad.

: How do you monitor disk space on unix systems?

Turn on the tracing option in the Tools/Options, Log tab, "Trace Enabled" check box. This will cause all Telnet commands and data saved in the Telnet.log file in 24x7 installation directory. This is a plain text file which you can conveniently read in the Notepad.

: I give up!!

: After the telnet open times out, should I be able to press the connect button
: and see a valid login prompt come back if I leave the username and
: password empty? I can't even get the telnet client to give me a basic
: prompt.....

Here's the bottom line.....

I'm not getting a login prompt after sending the telnet open command. The trace file only contains the commands being sent by the script. Should the responses from the host be in the trace file?

Are their any other hidden configuration options available?

: Turn on the tracing option in the Tools/Options, Log tab, "Trace
: Enabled" check box. This will cause all Telnet commands and data
: saved in the Telnet.log file in 24x7 installation directory. This is a
: plain text file which you can conveniently read in the Notepad.

Yes, everything should be in that file. Please send your telnet.log and script.log files to support@softtreetech.com to let us see what is going on and so can we can better help you

: Here's the bottom line.....

: I'm not getting a login prompt after sending the telnet open command. The
: trace file only contains the commands being sent by the script. Should the
: responses from the host be in the trace file?

: Are their any other hidden configuration options available?