Re: mysqld and multilog
Brian Reichert <[email protected]>
| Newsgroups | gmane.comp.djb.syslog |
|---|---|
| Message-ID | <[email protected]> |
On Mon, Nov 22, 2004 at 08:44:03PM +0100, Laurent Bercot wrote: > --log=/service/mysqld/logfifo with a multilog process reading from > the fifo - the standard trick. > "Could not use /service/mysqld/logfifo for logging (error 29)." > 29 means ESPIPE. > Aaugh ! Dorks. Why on earth do they need to seek on that descriptor? Contemporary versions of MySQL want to maintain a 'binary log'; this is used for replication, among other things. I don't know _which_ log you're trying to maintain, of course: http://dev.mysql.com/doc/mysql/en/Log_Files.html > I'm out of ideas. Do I have to let mysqld write its logs into a regular > file, and use logrotate or any other unreliable way of rotating logs? http://dev.mysql.com/doc/mysql/en/Log_file_maintenance.html > Or is there a way to get past that horrible ESPIPE and have a reliable > installation? Google "mysqld daemontools" doesn't help much. I have > found Brian Reichert's run file for mysqld, but it uses --log=/some/fifo > which doesn't appear to work in my case. God, that's still on the net? :) This script for an older MySQL version. I haven't verfied it for 4.x. > -- > Ska -- Brian Reichert <[email protected]> 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large