> > Just use etc/svc/volatile. There's no need for us to have to do a bunch > > of extra work to reinvent that mechanism. dlmgmt is a service. If it > > runs before the other stuff is mounted, which is a very small number of > > services, then it should go ahead and use that directory. > > etc/svc/volatile is already used for early-boot things such as log files. > > > If we can use etc/svc/volatile directly, that would be great. Is this > directly be ARCed? Which case is that? > > Thanks > - Cathy
There is no explicit interface around that directory, but etc/svc is Committed, and I see no problem with just using it as-is under the general rule that pre-usr services can make use of that. SMF already stores per-service log files there under their fmri name and the suffix .log, so a very reasonable usage that would adhere to the current convention would be to invent some suffix for your file (e.g. ".data", ".cache", or something like that) and use the same prefixing convention so as to avoid name conflicts in the future with other FMRIs. From a method script to generate the appropriate pathname you would do something like this: cache=`echo $SMF_FMRI | cut -d/ -f2- | tr / :`.cache -Mike -- Mike Shapiro, Solaris Kernel Development. blogs.sun.com/mws/
