* Mark Maule <mark_maule at yahoo.com> [2009-12-09 21:39]: > Still working on the truss(1) info - will post that separately. For > this appliance, my intent is to run with a writable ram based root fs. > As such, I do not have currently have any extra filesystems. When I > build my root archive, I make it about 50mb larger than it needs to > be, and then remount it to be writeable. So /etc/svc/volatile is just > a directory in my archive. The contents currently (the cores were > generated earlier with gcore): > > # pwd > /etc/svc/volatile > # ls -l > total 40064 > -rw-r--r-- 1 0 0 5819791 Dec 9 01:48 confd.core.100008 > -rw-r--r-- 1 0 0 4423163 Dec 9 01:46 core.100006 > -rw-r--r-- 1 0 0 5819791 Dec 9 01:46 core.100008 > -rw------- 1 0 0 412 Dec 9 01:16 init.state > Drw-r--r-- 1 0 0 0 Dec 9 01:17 repository_door > -rw-r--r-- 1 0 0 4423163 Dec 9 01:48 startd.core.100006 > -rw------- 1 0 0 18432 Dec 9 01:17 svc_nonpersist.db
/etc/svc/volatile is expected to be a tmpfs filesystem that's always writeable. If svc.startd can't write there (with EROFS returns if the filesystem isn't read-write as you mention), then it won't be able to log there; similarly, svc.configd expects to be able to create that svc_nonpersist.db (temporary state) in that location. It's strange that you have one, but not the other... - Stephen -- sch at sun.com http://blogs.sun.com/sch/
