I've been running the updated crontab on a server since my last email and have been getting emails like this from the cron daemon:
Cannot stat file /proc/8419/fd/1: No such file or directory Cannot stat file /proc/8419/fd/2: No such file or directory Cannot stat file /proc/8419/fd/3: No such file or directory I presume it's fuser printing this as the files its been told to look at no longer exist. (They've probably been garbage collected by php) Would it be safe to add a "2> /dev/null" to this? Are there any other error conditions we might actually want to hear about? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
