Zhao Yi wrote:
> why does ruby check its permission?

Because not heeding this warning is approximately the same as posting 
your password in clear text to all users on the system.

Even if you have no other users on your system, if someone happens to 
break in (e.g. through your web server or mail server), and gets a shell 
running as any daemon user, they can exploit this hole to run any script 
as *your* userid.

> I do want this path writable. how 
> can I disable this warning?

I already pointed you at file.c. You will find a #if check in there, 
which lets you recompile ruby with this check disabled.

I'm not going to hint further. If you are smart enough to understand 
fully the consequences of disabling this check, then you a smart enough 
to read the configure script and recompile ruby with this check 
disabled.
-- 
Posted via http://www.ruby-forum.com/.