> For our more restricted systems, I syslog bash command history to a remote > host so that I can confirm I'm to blame when something goes wrong.
We just have serial consoles on everything, which go through tightly locked-down console servers running conserver, which allows logging of everything that happens on the console. www.conserver.com > We also have some stuff in an extremely crufty home-grown FileMaker trouble > ticket system. I feel your pain. > We also have some (NT) stuff in an Access database. Oh, I see: you guys just *like* pain. > We also have some people who want to spend a lot of money on a commercial > issue tracking system. > > We also have some people who want to use RT because the commercial issue > tracking system was chosen for feature bloat, not usability, and only has a > proprietary Win32 interface. We've had RT for a year and just over 1000 tickets and we have no idea how we got along without it. No closed system could be as flexible, and even if you pay them for siginficant customizations and feature enhancements, it's far less money than any "turn key" system. And for the suits, you can buy a support contract now. www.bestpractical.com ---Alex Carl Alexander Sr. Systems & Network Administrator TERC --- Send mail for the `bblisa' mailing list to `[EMAIL PROTECTED]'. Mail administrative requests to `[EMAIL PROTECTED]'.
