> > May 15 04:25:10 crocus anftpd[340] retrieve private/software.tgz (failed) > add event to session_340_anftpd > create alias to session_340_anftpd called report_session_340_anftpd > > 10 May 15 04:25:12 crocus anftpd[340] logout > set timeout on session_340_anftpd to 1 second > reset termination action to: report session_340_anftpd notify.sh > (because the action "set session_340_anftpd 1" wipes out any > existing termination action, I think this is a bug) > unalias session_340_anftpd > > The unalias is the key. If no alias was made to the session_340_anftpd > context, then the unalias acts like delete and removes the context > with no report. If however an alias was made to the context, then it > will survive the unalias and time out in 1 second causing a report to > be sent. > > What I would like is that ability to report the context that is > undergoing deletion without having to get its name. In this case I can > use report_session_340_anftpd but when following multiple streams a > given event that triggers a report may accessing the context under > another name and thus there is no way for the session end event to > figure out what name the report command should use. > > Also I think the set command should not change any termination > action. If the user want to use set to change both the time and the > termination action they can explicitly use "none" as the termination > action. >
My answer is somewhat late -- my apologies :( The current behavior of the 'set' action is not a bug, but a feature that has always been there. To explain this a bit, specifying the 'none' action and no action list are not exactly the same -- in the first case, some overhead is involved for invoking the action list. I ackowledge, though, that the current need to re-specify the same action list for 'set' is not handy. The problem is that introducing this feature to the code will change the semantics of older rulesets. As for the example about alias, I wasn't quite able to follow it -- the process ID is present in all messages, why is it not sufficient to create and delete aliases correctly? best regards, risto ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Simple-evcorr-users mailing list Simple-evcorr-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/simple-evcorr-users