[Kolab-devel] Make template more modular, store the service to restart in the header

[Marcus Hüwe]

Hi,

On 2007-06-28 13:52:59 +0200, Gunnar Wrobel wrote:
> "Alain Spineux" <aspineux at gmail.com> writes:
> 
> > The idea is to be able to add a services to kolab without changing perl code but taking benefice of kolab template.
> > This is what I did with a Before Queue Filtering for postfix.
> >
> > I made my own configuration  template, but a kolabconf don't restart my new service when it update my configuration :-(
> >
> > It could be useful to change the KOLAB_META tag in templates to include relevant information
> > about what to do when the configuration change
> >
> > Here is the postfix header
> >
> > KOLAB_META_START
> > TARGET=/kolab/etc/postfix/main.cf
> > PERMISSIONS=0644
> > OWNERSHIP=kolab-n:kolab-r
> > KOLAB_META_END
> >
> > Include something like
> >
> > SERVICE=postfix
> > UPDATE=service:restart
> > MESSAGE=Postfix is restarting
> >
> > or
> >
> > SERVICE=postfix
> > UPDATE=cmd:/kolab/sbin/postfix reload
> > MESSAGE=Postif reload its configuration
> >
> > maybe include a PRIORITY to know in which order to restart all the changed services ...
> >
> > That could make kolab more "plugins ready" :-)
> 
> Did you try to use the header entry "RUNONCHANGE"?
> 
> This functionality should be available in Kolab-2.1.
> 
Are you sure? I looked through some scripts like kolabconf etc. and it seems
that they didn't support something like that.
Only the example.conf.template contains this "meta string".

Or am I wrong?


Marcus