I´ve got a weird problem with the NULL-Device. In fact I just virtualized a fedora3 machine, which worked quite well. Access via SSH etc. is possible. However there´s one problem with the dev/null-device. The Amavis-milter accesses the /dev/null-device combined with etc/profile, which leads to an error --> /dev/null: permission denied.
How can I solve this problem?
I already deleted dev/null and recreated it...as I already said access via ssh is possible and anything else works...except for the point mentioned above.
Any help is appreciated
Thanks for your reply!
I´m using the following kernel on a fedora-core6 machine:
2.6.18-8.1.15.el5.028stab047.1 #1 SMP Tue Oct 23 15:25:33 MSD 2007 i686 i686 i386 GNU/Linux.
I will have a look at your recommended link.
Regards
Norman
unfortunately I´m still having a weird problem with the dev/null-device.
As i already mentioned, I virtualized a fedora-core 3 machine running stuff like amavisd-new, spamassassin etc.
After recreating all devices and other steps mentioned in the HowTo:P2V, everything seems to work fine...the only exception I could figure out is amavisd-new.
Example:
[root@fedora3p2v /]# /etc/init.d/amavisd-new status
amavis-milter is stopped
amavisd is stopped
amavisd-new is stopped
[root@fedora3p2v /]# /etc/init.d/amavisd-new start
Starting amavis-milter: /etc/profile: line 27: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 3: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 4: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 17: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 18: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 19: /dev/null: Permission denied
/etc/profile.d/colorls.sh: line 20: /dev/null: Permission denied
/etc/profile.d/vim.sh: line 3: /dev/null: Permission denied
-bash: /dev/null: Permission denied
[ OK ]
Starting amavisd-new: [ OK ]
Does anyone know how to fix that problem? I Already upgraded to the latest openvzkernel:2.6.18-53.el5.028stab051.1
I would note that 'vzctl set --devices c:5:2:rw' command is not required.
First, it is not /dev/null device, it is /dev/ptmx
Second, this device file should have 0666 access permissions too. Obviously you have created it by mknod command, and write permission for user and group was restricted by umask.
Marat has corrected our wiki page, now it recommend to execute mknod with --mode option.
iroen Messages: 1 Registered: March 2012 Location: Poland
Junior Member
From: *au.poznan.pl
I had this problem today and this link (I can't use links so sorry, but I wont show you the source ...) solution helped. By default there was "crw" only on the /dev/null and the problem (in this case the starting of allegrograph server) went away after doing chmod 0666 on the file.