Ok, it appears to be a bug.... or an oversight at least.... Radiator creates the log file (RADLOG) with columns TIMESTAMP, PRIORITY, and MESSAGE (or thereabouts). The insert statment in LogSQL is hardcoded for these columns names. However, when RADMIN creates its log file (RADMESSAGES) it creates the columns TIMESTAMP, TYPE, and MESSAGE. But there is no LOG RADMIN clause in your config file, so you're supposed to just use the LOG SQL clause. This chokes because there is no PRIORITY column. So what's the best way to fix this? You can't specify a different insert command with the right columns in your LOG SQL clause in your config file (ok, you could hack up the LogSQL.pm code, but I don't want to). For the future release to fix this, I would see several options... 1) When the radmin install procedure creates it's log file (RADMESSAGES), have it use the same column names as Radiator does for RADLOG or 2) Create a LOG RADMIN clause to use instead of LOG SQL that does the right insert statement or 3) Allow uses to specify their own update statement in the LOG SQL clause in the config file so they can specify any columns they want I'd like to know how the authors intend to address this so that my "quick and dirty" workaround doesn't get stepped on by future releases. Thanks! Jay West === Archive at http://www.starport.net/~radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
