because, when the disk is full, what you really want to do is halt the boot process
Dec 29 09:53:09 some-server mysqld[900]: /usr/sbin/mysqld: Disk is full writing '/var/log/mysql/mysql-bin.000219′ (Errcode: 28). Waiting for someone to free space… Retry in 60 secs
because, you know, it's OK to block the boot process (/etc/init.d/mysql hangs) becuase MySQL can't write to disk, in fact, if your going to do this, make absolutely sure that you startup before sshd. Also, under no cirumstances report useful messages to the terminal. Because, we all know that the MySQL people are in cahoots with the remote hands service at datacenters (it's a freemason-like secret society thing) and are all just conspiring to rack up remote hands charges.
There is *no* reason why sshd should not startup after the network comes online.
1 Comment »
RSS feed for comments on this post. TrackBack URI
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
January 25th, 2006 @ 08:45:55
[…] Yep, you see that right. This system was installed back in 2002. Never been upgraded, to the best of my recollection I have never had issues with log file rotation not occuring and causing problems. […]