On Fri, 16 Dec 2005, Uwe Dippel wrote:
> Just another curiosity:
> The archive is full of suggestions to combat the dreaded MySQL Error No.9
> with a specific login class (and others); usually suggested to be 'mysql'
> in login.conf.
>
> Now, for reasons of pure logic and beauty, I call it _mysql.
> Then - if my logic is correct - I need to define this class for the user
> _mysql. 'chpass' is a way. Alas, it won't accept neither _mysql nor mysql
> as class and mumbles something about a typo.
Please report exact command lines and error messages.
> This I don't understand, because from the creation of login.conf onwards,
> _mysql is shown as possible login class with adduser. Would this be a bug
> in chpass ? Using vipw permits this change, though.
>
> Second: In my understanding, rc runs as daemon; so will there be any
> effect to starting mysql in rc.local through this class ? Will rc not
> automatically and irrevocably start mysql with the parameters of daemon
> (login class) ?
> The only way I could imagine this class to ever take effect would be when
> starting mysql as root with sudo on an already running box.
>
> All this could be badly wrong, though. Please correct me if it is !
> Only, if it is: Is this (_)mysql login class not rather useless ? Should
> we then not rather put _mysql into daemon; in order to have exactly the
> same parameters starting from rc (at boot) and anytime later ?
Use su(1) to start the command with a given login class.
-Otto
