Sangeeta Misra writes: > On 03/25/09 05:25, James Carlson wrote: > > The bottom line on this is that I don't quite understand what is > > accomplished by real-time monitoring of internal events in this one > > subsystem. > I wanted to borrow the tracefile notion from in.routed daemon > implementation.
The trace file in in.routed, though, is just a log. It's not at all the same as "ilbadm monitor." It's much more like just calling syslog(). The reason that file exists in in.routed is that we ported in an open source package, and we wanted to retain as much of the common platform-independent behavior as we could. Otherwise, that would certainly have been done differently. > I recall we used that facility a lot to debug things > when a certain action did not yeild a specific result, and the tracefile > was used to find out what expected sequence of steps did not occur. But > you are right that in a ILB case it will the events are interelated > between various subsystems ( servers, backup loadbalancer) . ... which is why writing to syslog is common practice. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
