3.3

Maintaining the Database
53
Since dblines examines every story in your database, it requires several hours to complete its
task, so run dblines before you go home at night. By the time you return in the morning, it
should be done.
When dblines discovers an error, it ordinarily sends an error message to the console.
However, if you run it at night, you can have the system send its messages to a log file for
you to review the next day.
n
For more information on the various commands used in this section, see “Command
References” on page 109.
To execute the command and have it send output to a log file:
1. Enter superuser mode on the master computer.
2. Type:
dblines . > /tmp/dblines.log
You can also use the at command to schedule the dblines command to run at a specified
time. For instance:
To execute the dblines command so it logs at a specified time:
1. Enter superuser mode on the master computer
2. Get the current time, using the date command:
NRCS-A# date
Sat Jul 10 11:05:07 EDT 2010
n
You must use 24-hour military time.
3. Set the schedule, such as 5 minutes later, using the at command:
NRCS-A# at 11:10
4. Type the dblines command line:
/exc/dblines . > /tmp/dblines.log
<Ctrl+D>
Pressing Ctrl+D after entering the command line marks the end of commands to be
executed according to the at schedule. Afterwards, the server prompt returns to the
original prompt, showing the server name, such as NRCS-A#.
After the dblines is complete, you can check the log file for error messages, by using the
grep command:
NRCS-A# grep failed /tmp/dblines.log