outex

NAME

SYNOPSIS

outex [ logfile ]

outex last

AVAILABILITY

DESCRIPTION

The intension is to use the outex logfile command directly from within vi when editing a recovery script, as:

  # D: Restore database. 
  #
  ~
  ~
  ~
  :. !outex 2020-06-02_10.52.05__db_restore.log

This will include the contents of the logfile edrc/var/log/2020-06-02_10.52.05__db_restore.log (without logfile header) into the vi session. Each line will be prepended by the # O: documentation tag.

The specified logfile can also be a gzipped file, as: 2020-06-02_10.52.05__db_restore.log.gz

Furthermore if the specified logfile 2020-06-02_10.52.05__db_restore.log does not exist, but the 2020-06-02_10.52.05__db_restore.log.gz does, the contents of the compressed file is included and vice versa.

After receiving the log data in vi, press [Ctrl] + [L] to redraw the terminal.

OPTIONS

-h

usage message.

 

specify the logfile interactively.

logfile

logfile to be read.

The file path must not be specified, due to the fact that outex only computes log files from the edrc/var/log/ directory; if a path is specified, the path part of the input is ignored.

The logfile can be a gnu-zipped log file (file.log.gz) as supported by edrc, it is not needed to decompress the file. Furthermore if the specified file.log does not exist, but the file.log.gz does, the *.gz file is loaded and vice versa.

last

load the last (newest) available recovery script logfile from edrc/var/log.

ENVIRONMENT

EXIT STATUS

4

usage printed.

1

logfile not found.

2

logfile cannot be read.

FILES

EXAMPLES

SEE ALSO

NOTES

BUGS

AUTHOR

COPYRIGHT

This is free software; see edrc/doc/COPYING for copying conditions. There is ABSOLUTELY NO WARRANTY; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.