Brad Mitchell wrote: > Just to update for anyone who is interested. > > The problem that I have encountered with remounting /etc from a writable > location, in this case, from /tmp/XXXX/etc is to do with mounting over the > top of the repository.db located under /etc/svc. The file is essentially the > same, however, this causes problems with svc.configd. If you run svcs in > say, maintenance mode after this mounting has taken place, it states an error > reading from the repository. > ... > 2) Killing the configd process from within fs-root. This worked and starts > on the fs-usr script however, this didn't continue to work past that. When > the process was killed from maintenance and "svcadm clear fs-root" was called > (I needed to remount,rw in order to log some debug to a log file on /) it did > work. > > The only thing that can be done is to locate the repository elsewhere > (hopefully it will work on a read-only location) such as /repository which I > won't mount over the top of. ...
What about being able to teach svc.configd to close and then repoen the repository? I.e. in response to a SIGHUP, it closes /etc/svc/repository.db and then reopens it? If the repository.db file starts out on a read-only filesystem, then no changes are going to be written out...so nothing is lost between the open and close. Darren
