On Fri, 16 Dec 2005, Uwe Dippel wrote:

> On Thu, 15 Dec 2005 18:07:52 +0100, Otto Moerbeek wrote:
> 
> > Please report exact command lines and error messages.
> 
> chpass _mysql
> [change daemon into mysql or _mysql]; :wq
> chpass: illegal character in the "class" field
> re-edit the password file? [y]:

I cannot reproduce this here. _mysql is accepted and processed correctly.

> 
> > Use su(1) to start the command with a given login class.
> 
> like
> # su -c _mysql _mysql -c date
> This account is currently not available.
> ?
> 
> Hey, I don't want to offend anyone in here !
> I only found some 20 occurrences of that additional login class and the
> same number of this suggestion. While typing, I asked myself, how the
> environment will be picked up, ever. And started to think ... and started
> to have doubts.

You'll have to give it the right args:

# su -m -c staff bin -c "ulimit -a"
time(cpu-seconds)    unlimited
file(blocks)         unlimited
coredump(blocks)     unlimited
data(kbytes)         159744
stack(kbytes)        4096
lockedmem(kbytes)    157262
memory(kbytes)       471136
nofiles(descriptors) 64
processes            128
# su -m -c daemon bin -c "ulimit -a"
time(cpu-seconds)    unlimited
file(blocks)         unlimited
coredump(blocks)     unlimited
data(kbytes)         524288
stack(kbytes)        8192
lockedmem(kbytes)    157262
memory(kbytes)       471136
nofiles(descriptors) 128
processes            532
# 

> I bet 90% of those people who report success with mysql with this class do
> not have it due to this login class, but due to the values of the daemon
> class. With which their mysql runs, incidentially.
> 
> # sudo -c _mysql -u _mysql date
> Fri Dec 16 09:51:03 SGT 2005
> 
> This is what I was hinting at in my post, btw. This is the only thing I
> got working for a user with nologin.

        -Otto

Reply via email to