On Fri, Jul 01, 2005 at 06:12:07PM -0600, Gerard Beekmans wrote: > > There must be nice > software packages out there that would help around with it.
I use http://www.bestpractical.com/rt/ at work. It's an issue tracker as well. Though trac might do the both jobs also and I know Matt is itching to try trac. :) > UML might be something to look into as long as it doesn't have too > much of a performance hit. When you say it like that, it makes it sound as if this move isn't in the very near future. Just curious. > I also have to document things for work, A good sysadmin keeps his job security intact by making it impossible for another sysadmin to figure out how to admin the boxen. :P > we can run it through "nice" give it a low priority so nothing else > suffers like smtp, http, svn, etc. With a low nice value, then simultaneous wouldn't really hurt. > Alternatively, we can do a semi render-on-demand too. If you fix a typo > there's no real need to re-render the book. Create some dummy file "renderme" > in the repository when you commit stuff that's worthy of being renderred > immediately rather than the current nightly job. If the post-commit hook > script sees the renderme file, run the rendering script (and remove the > renderme file). If not, "exit 0" and everybody is happy. That sounds nice. -- Archaic Want control, education, and security from your operating system? Hardened Linux From Scratch http://www.linuxfromscratch.org/hlfs -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
