Re: /dev/null: permission denied - problem
OK, I've done so like you told me. It now works. I also mailed the selection list. Kind Regards, Stephan Hachinger - Original Message - From: Santiago Vila Doncel [EMAIL PROTECTED] To: Stephan Hachinger [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Sent: Thursday, April 27, 2000 8:16 PM Subject: Re: /dev/null: permission denied - problem On Sun, 23 Apr 2000, Stephan Hachinger wrote: At least since I mixed my slink system with potato packages (glibc 2.1) a couple of months before, I have a problem with /dev/null. Firstly, lprng reported at startup: setuplog: open /dev/null failed: permission denied (I fixed it by installing lpr which does not complain about it), and now since I installed exim correctly, I always get mails like this one: [...] /bin/sh: /dev/null: Permission denied Has anyone experienced this problem and can help me, please? /dev/null should be writeable by everybody, if it is not, please do: chmod 666 /dev/null BTW: There is a user who reported a similar problem. So far, we have been unable to discover which package exactly is the responsible for that. Could you please post the output of dpkg --get-selections to the [EMAIL PROTECTED] address? (if you think it is not sensitive information, of course). I have asked the same to the other user, hopefully we will be able to compare both lists and see what common packages do you have. Thanks.
Re: /dev/null: permission denied - problem
On Sun, 23 Apr 2000, Stephan Hachinger wrote: At least since I mixed my slink system with potato packages (glibc 2.1) a couple of months before, I have a problem with /dev/null. Firstly, lprng reported at startup: setuplog: open /dev/null failed: permission denied (I fixed it by installing lpr which does not complain about it), and now since I installed exim correctly, I always get mails like this one: [...] /bin/sh: /dev/null: Permission denied Has anyone experienced this problem and can help me, please? /dev/null should be writeable by everybody, if it is not, please do: chmod 666 /dev/null BTW: There is a user who reported a similar problem. So far, we have been unable to discover which package exactly is the responsible for that. Could you please post the output of dpkg --get-selections to the [EMAIL PROTECTED] address? (if you think it is not sensitive information, of course). I have asked the same to the other user, hopefully we will be able to compare both lists and see what common packages do you have. Thanks.
/dev/null: permission denied - problem
Hello! At least since I mixed my slink system with potato packages (glibc 2.1) a couple of months before, I have a problem with /dev/null. Firstly, lprng reported at startup: setuplog: open /dev/null failed: permission denied (I fixed it by installing lpr which does not complain about it), and now since I installed exim correctly, I always get mails like this one: From [EMAIL PROTECTED] Sun Apr 23 20:38:01 2000 Envelope-to: [EMAIL PROTECTED] Received: from root by PENTIUMDIOXID with local (Exim 3.12 #1 (Debian)) id 12jRGa-PD-00 for [EMAIL PROTECTED]; Sun, 23 Apr 2000 20:38:00 +0200 From: [EMAIL PROTECTED] (Cron Daemon) To: [EMAIL PROTECTED] Subject: Cron [EMAIL PROTECTED] if [ -x /usr/sbin/exim -a -f /etc/exim.conf ]; then /usr/sbin/exim -q /dev/null 21; fi X-Cron-Env: SHELL=/bin/sh X-Cron-Env: HOME=/var/spool/mail X-Cron-Env: PATH=/usr/bin:/bin X-Cron-Env: LOGNAME=mail Message-Id: [EMAIL PROTECTED] Date: Sun, 23 Apr 2000 20:38:00 +0200 /bin/sh: /dev/null: Permission denied Has anyone experienced this problem and can help me, please? Kind Regards, Stephan Hachinger
Re: /dev/null: permission denied - problem
Stephan Hachinger [EMAIL PROTECTED] writes: /bin/sh: /dev/null: Permission denied Well, have you actually looked what the permissions to /dev/null look like? ls -l /dev/null. They should be crw-rw-rw- root.root. -- Arcady Genkin http://www.thpoon.com Nostalgia isn't what it used to be.
Re: /dev/null: permission denied - problem (solved)
Hello! Thanks for your quick replies. I already thought of this solution, but mc did not let me chmod the null device, and so I thought there is no possibility of chmod for the /dev files. I think it's solved now. Kind Regards, Stephan Hachinger
