Re: configuration patch - final version

[Oliver Jehle]

I think, the format should be simple... and easy... for example

boottime \tab   3333333
status    \tab  stopped|started
timestamp \tab  4444444
config  \tab    param=x
config  \tab    param=y
processlist\tab heartput        active
processlist\tab b
processlist\tab c


so you can easy check it with a cat or more.... and its easy to read...
readline and with index the pos of the tab.... 

i don't like files, i can't view with a normal *nix tool... 


i think, the boot time is important, because if you restart monit, you
should know, if the server is crashed (boottime in file != actual
boottime) or its a restart (crash| reload ) of monit... (boottime in
file == actual boottime)....  








On Tue, 2003-02-11 at 22:40, Martin Pala wrote:
> Jan-Henrik Haukeland wrote:
> 
> >  
> >
> >>-----Original Message-----
> >>From: address@hidden
> >>[mailto:address@hidden Behalf Of
> >>Martin Pala
> >>Sent: 11. februar 2003 21:43
> >>To: The monit developer list
> >>Subject: Re: configuration patch - final version
> >>
> >>
> >>Jan-Henrik Haukeland wrote:
> >>
> >>    
> >>
> >>>So all our remaining tasks are done according to the monit 3.2 release 
> >>>plan,
> >>>
> >>>      
> >>>
> >>Yet one remains - to add Oliver's documentation for monit+heartbeat. I
> >>can add it if needed too :)
> >>    
> >>
> >
> >Yes, please! I'll buy you a beer if I visit Czech one day :-)
> >
> OK :)
> 
> >
> >  
> >
> >>>I propose that we test
> >>>the system a few days and release it this Friday, if everything is
> >>>      
> >>>
> >>okay. Agree?
> >>    
> >>
> >>Agree
> >>    
> >>
> >
> >Okay, Friday it is.
> >
> >  
> >
> >>>I was thinking about Olivier's proposal about writing the state to a
> >>>"state-file". I suggest that we simply write the processlist to a
> >>>binary file
> >>>      
> >>>
> >>It will be probably the simplest way to do it. Maybe it will be suitable
> >>to use ASN.1 BER rules to encode runtime structures into binary form -
> >>it defines standard method for encoding/decoding structured data into
> >>binary format and it will be easier than XML parser (however XML file is
> >>more user-friendly for edit :)
> >>    
> >>
> >
> >Much easier than XML, I was simply thinking about using something ala
> >
> >for(p= processlist; p; p= p->next)
> >     fwrite(p, 1, sizeof *(p), binaryfile);
> >
> >
> >I have never heard of ASN.1 BER rules, do you have an URL?
> >
> It is widely used in SNMP, LDAP and SSL for data for transmision. It is 
> usualy sufficient to use only subset of these rules (depends on the 
> needs). It is suitable for storing structured data directly into 
> key-value database (for example berkeley db) as well. You can read about 
> it for example here:
> 
> http://www.itu.int/ITU-T/studygroups/com17/languages/X.690_1297.pdf
> 
> Cheers,
> Martin
> 
> 
> 
> _______________________________________________
> monit-dev mailing list
> address@hidden
> http://mail.nongnu.org/mailman/listinfo/monit-dev