it's a problem for us, we have a nfs mount from
the troubleticketsystem to trapd.log.
is there an other solution to flush the buffers ?
>
>
>
>
> trapd.log uses buffered I/o, so the last event is not written to the log
> until the next one is received.
> Usually this is not a problem in most environments because the trap rate
> is
> at least one every second or so.
> If you need to make certain that trapd.log has the last event you saw on
> the browser, then you can send a dummy one with the event command to f
lush
> the buffers
>
> James Shanks
> Level 3 Support for Tivoli NetView for UNIX and Windows
> Tivoli Software / IBM Software Group
>
>
>
> "charly"
> <ylvie3434@gmx.ne
> t> To
> Sent by: nv-l@lists.us.ibm.com
> owner-nv-l@lists. cc
> us.ibm.com
> Subject
> [nv-l] Node up/down delay in
> 03/04/2005 06:32 trapd.log
> AM
>
>
> Please respond to
> nv-l
>
>
>
>
>
>
> we use NV 7.1.2 and 7.1.4 on Sun/Solaris 8
> and Win2000.
>
> When a node goes down, the event browser shows the message, but
> in trapd.log it is a large time, to represent the event.
> it seems, that there must be a next event (node up), to trigger
> and send the node up or down event to trapd.log.
>
> please help me
>
> charly
>
>
> --
> charly
>
> DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen!
> AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
>
>
>
--
charly
SMS bei wichtigen e-mails und Ihre Gedanken sind frei ...
Alle Infos zur SMS-Benachrichtigung: http://www.gmx.net/de/go/sms
|