On Monday 10 August 2009 09:01:39 ron minnich wrote: > > main: create /active/cron/bootes bootes bootes d775 > > This is right. It's supposed to be a directory. > cpu% ls -l /cron/bootes > --rw-r--r-- M 9758 bootes bootes 0 Sep 17 2008 /cron/bootes/cron > > > main: create /active/sys/log/cron bootes bootes a664 > > This is right. It's supposed to be an append-only file. > > cpu% ls -l /sys/log/cron > a-rw-rw-r-- M 9758 bootes bootes 8068019 Aug 10 12:00 /sys/log/cron > cpu% > > I don't see the problem. >
Here's the problem: cpu% ls -ld /sys/log/cron d-rw-rw-r-- M 81 bootes bootes 0 Aug 10 05:19 /sys/log/cron Somewhere along the line '/sys/log/cron' is goes from being an append-only file, to a directory. "/sys/log/cron: rc (cpurc): can't open: 'sys/log/cron' is a directory" This has occurred several times (on every one of my cpu/auth installs), and I'm hoping to pinpoint what might going wrong so that I can avoid this in the future. I've written a Plan 9 standalone cpu/auth server installation and configuration howto - but I don't want any 'bugs' in the documentation, so I'd like to try and weed this one out, but I'm unable to determine where/when this particular issue might be cropping up. I wonder whether 'auth/cron -c' is the culprit, when I first run '/sys/lib/newuser' for bootes.
