On Wed, Aug 06, 2008 at 10:33:01PM +0200, Michal Svec wrote:
Can't we get this information from SCR, without calling explicitely some functions (which is going to be error prone)?
For instance the example above could be generated from SCR (layer), one would (more or less :) only need .path -> file/function translation to create such a log.
SCR could do it if that was a reuqirement from early on, but I am afraid that it is not quite suited for this use at this point. In other words, it would be rather "much more" than "less" I think. Anyway, we can see how that would look like from watching what goes through SCR: Y2DEBUG=1 (or [Debug] scr=true in log.conf), then egrep -A3 'executeSubagentCommand: (Write|Execute)' y2log For example attached is one such log, which I would like to see described as Note "changed ntp server from ntp.suse.cz to random one from pool.ntp.org" Item "/etc/ntp/conf: server list changed to 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org" Item "/etc/sysconfig/ntp: NTPD_RUN_CHROOTED changed to yes" (hmm, that's a gratuitous change) Item "restarted /etc/init.d/ntp" I encourage people to try this with their own modules and perhaps post the results so that we get a better idea if pursuing this path is worthwhile. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu