Re: two small updates

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

Bernard Johnson wrote:
> When packaging tmda for Fedora, I came across these two things that
> should probably be updated.
> 
> A reviewer noted that it was best to have the tofmipd program inactive
> when installed with chkconfig.  Also, a reload function should be
> provided in the init script (even if it simply does the same as restart):
> 
> http://cvs.fedora.redhat.com/viewcvs/devel/tmda/tofmipd-init.patch?root=extras&rev=1.1&view=auto

That patch looks sane to me. Just one question though: In the chkconfig
line, the 2345 got removed, which is I assume what disabled the service
by default. If I then do "chkconfig --on tofmipd", how does chkconfig
know which runlevels to enable the service in. I was vaguely under the
impression that the chkconfig line in the init file was the set of
run-levels that the service should be enabled in if it gets enabled, and
presumably there's a script in the RPM that gets run postinstall that is
running "chkconfig --on tofmipd" to actually enable the service? But,
perhaps I misunderstand how chkconfig and rpm interact...

 > I also noticed that the INSTALL file
> (http://tmda.svn.sourceforge.net/viewvc/tmda/trunk/tmda/INSTALL?revision=2059&view=markup)
> says "
> A local copy of the HTML documentation matching this release is included
>  in the htdocs directory."
> 
> I believe that the up to date documentation is the wiki, right?

Yes. Although there was some talk of including an up-to-date snapshot in
each release. I think that happened (if there are docs in the release
tarballs, then I guess it did!)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF3xfnhk3bo0lNTrURAglqAJ9eKot6SYa3Nsz+UquoRS2abt2nSACgmmkk
u/pc9OX0toXpS2BTXjSfhTs=
=mI3X
-----END PGP SIGNATURE-----