[NTLUG:Discuss] sed question

[Jason Burnett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

At the point you are at now, I would probably go with a perl/php script
and small mysql db. The history can be stored easily and new entries can
be updated/inserted with little effort. You could easily have default
values that are left untouched and have the cgi generate a new ntp.conf
at the end of each session/change/update.

on Thu Apr 08 Ralph Green, Jr spoke forth with the blessed manuscript
> Val,
>  I thought about a solution like this, but I don't think it will be
> robust enough.  I need to be able to handle any file ntpd can.  If there
> are a few thousand of these systems deployed, we are bound to have some
> users monkeying with the files.  Low maintenance and reliability are
> diving factors. Those are even above functionality, as long as we are
> minimally functional.
> Thanks,
> Ralph

> On Wed, 2004-04-07 at 16:07, Val Harris wrote:
> > How about bracketing your Server Lines with unique text?  For example:
> > 
> > # - - - Sync_Server_Start - - - - - - -
> > server  ntppub.tamu.edu
> > server  tick.usno.navy.mil
> > # - - - Sync_Server_End - - - - - - - -



> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss


- -- 
PGP key - http://www.monkeypr0n.org/keyring/jason@monkeypr0n
793A 39E7 5655 0415 5C5E  976E 94D8 F8C4 C061 DF64
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAdP35lNj4xMBh32QRAmWAAKCWax9DtHeYI5zPt+jQ3rcKVmVxPgCdEFGc
YheLP0hDKFOf90vyWC2Wo9s=
=wZyF
-----END PGP SIGNATURE-----