[osiris-devel] monitoring host state

[Alexei_Roudnev]

1) Can anyone remind me, what is filter syntax for Windows (which have not
reg-exp) so that if I want to disable some atrribute checks (bytes, blocks,
mtime, ctime, inode) I can do it (manager is windows, but target systems are
different)?

Brian, may be, we just write out simplified reg-exp functions (able to
recognize 'xxx', '*xxx' and 'xxx*') or even just (* and xxx where xxx is
exact string), to have windows and unix syntax the same? For now, I was not
able to get success with filters?

(I tried both, empty fields and * in fields. May be, I should look into the
source code).
I have such filter, which does not work:

host=;path=;exclude: fileattr ;
host=;path=;exclude: ctime ;
host=*;path=*;exclude: mtime ;
host=*;path=*;exclude: fileattr ;
host=;path=;exclude: mtime ;
host=*;path=*;exclude: ctime ;
host=*;path=*;exclude: bytes ;

2) As you remember, I applied a patch, which calls 'config' (print current
config name) in the end of all configuration lists (so we have current name
in allcommands, which require to enter configuration name - it is impossible
to work without it).
First of all, where (if any) was this feature incorporated (which
versions) - 3.*? /if 3.*, can we include it into 2.4 release as well?/
Second, sometimes this patch cause 'osiris' to loop during 2 - 5 minutes
(90% CPU - osiris and 10% cpu - osirismd) before printing result (it happens
1 time during all session). I (still) have not windows exe files, compiled
in debug mode (do you have it in the new version?), so there is not simple
way to figure out, what is it going.

3) How do we expect to distinguish configuration files for different scanner
versions? It is very important to be able to have different central server
(both, osiris and osirismd) and scanners, because it is unrealistic to
update all 60 - 100 scanners at once, when new version arrives. So, it
became very important to keep protocol compatibility, and to have some way
to distinguish configuration files.

There are 4 possible approaches:
1 - ignore the whole problem. It works only if versions are fully compatible
for 1 - 2 years, which is not our current case.
2 - have backward compatibility, so that new options will be ignored (even
with warning, it is OK) by the old scanners.
3 - have different sets of configurations (use different directories).
4 - use # if # else (something like this) operators.