Hi all
I appreciate the answers, but they have nothing to do with my question. If the file doesn't support the include directive, I can simply cron a task to merge the files.
What I wanted to know, is if there is a method of sanity-checking the files before presenting them to hobbit.
Remember, Windoze admins are going to be editing at least one of these files through Samba. Windoze editors leave <CR><LF> rubbish everywhere, and all sorts of unwanted formating. I need to sanitise these files before giving them do Hobbit. But this is the easy bit.
How do I check that these files are syntactictically correct from a Hobbit perspective?
Regards Vernon
-----Original Message----- From: Levin, Alexandre [mailto:alevin at reveredata.com] Sent: Friday, 4 July 2008 3:30 AM To: hobbit at hswn.dk Subject: RE: [hobbit] Sanity check for config files
I could add that I'm using the include directive in all config files
And practically the only change in the original config is the additional "include" directive.
Such schema allows easy maintain config files and do regular updates of the "current" hobbit server.
Alexandre Levin
-----Original Message----- From: T.J. Yang [mailto:tj_yang at hotmail.com] Sent: Thursday, July 03, 2008 9:28 AM To: hobbit at hswn.dk Subject: Re: [hobbit] Sanity check for config files
<snip>
All three of these work, which is a good thing.
I will check it out on my test hobbit server.
Thanks for great tip.
tj
To my knowledge and practice, only bb-hosts support "include" directive. not hobbit-alerts.cfg and hobbit-client.cfg. I wish these two cfg files support include also.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
NOTICE: This email and any attachments are confidential. They may contain legally privileged information or copyright material. You must not read, copy, use or disclose them without authorisation. If you are not an intended recipient, please contact us at once by return email and then delete both messages and all attachments.