[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

9.9 Activity log

All activity of days, tasks and jobs is recorded by `dio87d' daemon. It's possible to know when a task started, when a job was aborted, which are jobs output...

We create a referential `ref1' (ra command) with two tasks `task1' and `task2'.

 
$ dio87c ra ref1
$ dio87c rta ref1 task1
$ dio87c rta ref1 task2

We specify that this tasks must be run every days (rtoa command) :

 
$ dio87c rtoa ref1 task1 add always
$ dio87c rtoa ref1 task2 add always
$

We add two jobs `job1' and `job2' to the task `task1'. We link `job1' with shell command `/bin/ls' (rjsp command) and an argument `"/"'. Finally, we link `job2' with `/bin/ps' shell command.

 
$ dio87c rja ref1 task1 job1
$ dio87c rjsp ref1 task1 job1 "/bin/ls"
$ dio87c rjsa ref1 task1 job1 "/"
$
$ dio87c rja ref1 task1 job2
$ dio87c rjsp ref1 task1 job2 "/bin/ps"
$

At the present time, there is no exploitation days in `dio87d' daemon (xdc command returns 0) et no log days in `dio87d' (ldc command returns 0).

 
$dio87c xdc
0
$dio87c ldc
0
$

Now, we create a new day `day1' with `rp' command :

 
$ dio87c rp ref1 "2004-08-10" day1 
$

Now, there is one exploitation day (xdc and xdl commands) and a log day (ldc and ldl commands).

 
$ dio87c xdc
1
$ dio87c xdl
day1
$
$ dio87c ldc
1
$ dio87c ldl
day1
$

If you want to get informations about `day1', you can use ldel command which prints log entries associated with the day :

 
$ dio87c ldel day1
2004-08-10 22:44:00	command	xda 'day1' (by 'diogene')
2004-08-10 22:44:00	command	xdse 'day1' true (by 'admin')
$

You can see that day was created at 10:44 AM. To print the tasks list of this day, we call ltl command :

 
$ dio87c ltl day1
task1
task2

To print log entries associated with a task of a log day, we use ltel command :

 
$ dio87c ltel day1 task1
2004-08-10 22:44:00	wait_for_condition	
2004-08-10 22:44:00	wait_enabled	
2004-08-10 22:44:00	running	
2004-08-10 22:44:00	terminated	
$

You can see when the task starts and when the task is terminated.

You can use ljl and ljel commands to get informations about jobs. ljl command prints tasks list of a task in a log day. ljel command prints log entries associated with a job :

 
$ dio87c ljl day1 task1
job1
job2
$
$ dio87c ljel day1 task1 job1
2004-08-10 22:44:00	wait_enabled	
2004-08-10 22:44:00	running	
2004-08-10 22:44:00	terminated	
$

ljel command accept a `-o' option to print screen outputs made by the executable associated with a job. For example, you can see the result of /bin/ls command of `job1' by adding `-o' option :

 
~$ dio87c -- ljel -o day1 task1 job1
2004-08-10 22:44:00	wait_enabled	
2004-08-10 22:44:00	running	
2004-08-10 22:44:00	output	bin
2004-08-10 22:44:00	output	dev
2004-08-10 22:44:00	output	etc
2004-08-10 22:44:00	output	lib
2004-08-10 22:44:00	output	mnt
[...]
2004-08-10 22:44:00	output	opt
2004-08-10 22:44:00	output	tmp
2004-08-10 22:44:00	output	usr
2004-08-10 22:44:00	output	var
2004-08-10 22:44:00	terminated	
$

Screen outputs starts with the word `output'. You can also see the result of ps command of `job2' :

 
$ dio87c -- ljel -o day1 task1 job2
2004-08-10 22:44:00	wait_enabled	
2004-08-10 22:44:00	running	
2004-08-10 22:44:00	output	  PID TTY          TIME CMD
2004-08-10 22:44:00	output	 5294 ?        00:00:00 dio87d
2004-08-10 22:44:00	output	 5307 ?        00:00:00 dio87d
2004-08-10 22:44:00	output	 5310 ?        00:00:00 dio87d
2004-08-10 22:44:00	output	 5313 ?        00:00:00 dio87d
2004-08-10 22:44:00	output	 5393 ?        00:00:00 ps
[...]
2004-08-10 22:44:00	terminated	
$

Log days which are stored by `dio87d' are not dependant of exploitation days in `dio87d' daemon. You can delete a exploitation day (with `xdk' command) and continue to consult log day (ldl, ltl and ltel commands) :

 
$ dio87c xdk day1
$ dio87c xdc
0
$ dio87c ldl
day1
$ dio87c ltl day1
task1
task2
$ dio87c ltel day1 task1
2004-08-10 22:44:00	wait_for_condition	
2004-08-10 22:44:00	wait_enabled	
2004-08-10 22:44:00	running	
2004-08-10 22:44:00	terminated	
$

As soon as an exploitation day is terminated, it's a good idea to delete it (xdk command) and to keep the log day some days. Once log day consultation is not necessary, it's possible to delete the log day with `ldk' command :

 
$ dio87c ldl
day1
$ dio87c ldk day1
$ dio87c ldl
$


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated by dom on September, 11 2005 using texi2html