strange codes

[texpert]

Can you copy paste this to your host and ask why then it's still 644.

jefersoncardo@jefersoncardo-1:~$ stat /dev/null
File: `/dev/null'
Size: 989559 Blocks: 2009 IO Block: 4096 regular file
Device: 801h/2049d Inode: 9502 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2010-09-14 00:00:02.000000000 -0400
Modify: 2010-09-14 03:09:53.000000000 -0400
Change: 2010-09-14 03:09:53.000000000 -0400
jefersoncardo@jefersoncardo-1:~$ date
Tue Sep 14 03:10:03 EDT 2010

regards
Alex

[jeferson]

Im still seeing the codes

[texpert]

Yes i know, because your host didn't change permissions on /dev/null to 666 permanently!

ls -l /dev/null
You should see this if everything is correctly
set:
crw-rw-rw- 1 root root 1, 3

If you get a different set of permissions like
this maybe:
-rw-r--r-- 1 root root 1, 3

then you should (as root) delete the /dev/null with:
rm /dev/null

and recreate it (as root) again with:
mknod -m 0666 /dev/null c 1 3

(The device number according to the Kernel source
in the documentation under Documentation/devices.txt
supposed to be Major=1 und Minor=3)

Now, list the /dev/null again and you should see
the permissions as above.

Hope this helps..

regards
Alex

[jeferson]

Hi there,
Here you go,

jefersoncardo-1:# stat /dev/null
File: `/dev/null'
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: 801h/2049d Inode: 10626 Links: 1 Device type: 1,3
Access: (0666/crw-rw-rw-) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2010-09-17 18:04:21.000000000 -0400
Modify: 2010-09-17 18:04:21.000000000 -0400
Change: 2010-09-17 18:04:21.000000000 -0400
jefersoncardo-1:#


Thanks,

[texpert]

Hi,

ls -l /dev/null
If permissions were set as they should be set you would see:
crw-rw-rw- 1 root root 1, 3

Not sure why your host can't manage that? Perhaps some module on the server changes the permissions back after they modify them and perhaps that is the reason why it doesn't work permanently. Talk to your host about it and explain them everything we've told you. Your permissions are NOT set properly.

We can also take a look, if u want to PM me your root pass, but your host is the one that is the most familiar with your server ,so they should be able to do that.

best regards,
Jim

[jeferson]

hey, here the support aswer

Hi,

It is 666 again. It was created with "mknod -m 0666 /dev/null c 1 3" which is the way it is always done. Have them try again and see if it's working for them.

Thanks,
Chris

[texpert]

Please send us root access, so we can try test it by ourselves.

regards,
Jim