Hi Liane, Thanks so much for getting back to me about this. I learned a lot about smf repositories and dependencies over the weekend when trying to get this to work :)
> What do you see if you run "svcprop filesystem/minimal" instead? (You > probably won't see your dependency.) Correct, my dependency is not present. > My guess is that the $ROOT/etc/svc/repository.db you're building on top of > has already had its running snapshots created. Thus, you're in need of > a "svcadm refresh" of the service to copy the properties you just > imported into the running snapshot. During the ON build, we have no > running snapshots created, because we've just built the repository. Ah, I see. My repository.db is updated in a golden ramdisk image that was created from a running machine. So it makes sense that snapshots already exist. > The functionality to run this refresh is not currently available due to: > 5087504 svccfg should allow 'refresh' of services on an alternate repository > > (I've just moved the comments content to the description field, > sorry...) This sounds exactly like what I need. > You can also test this by doing svccfg repository <your repository>, > select filesystem/minimal:default, then 'listsnap'. If there's any > running snapshot in the repository you're building on, a refresh is > necessary -- but you haven't had a chance to do the refresh. Correct again. There are number of existing snapshots in the ramdisk's repository: NODE hcb101 ~ $ svccfg svc:> select filesystem/minimal:default svc:/system/filesystem/minimal:default> listsnap initial last-import previous running start > One way to resolve this today would be to explicitly build the repository > up yourself from the seed, rather than copying one from a machine. > That way you wouldn't have any running snapshots, and we'd > automatically create them when we started the service the first time. Ok, I'll try that. Seems easy enough from looking at svc/seed/Makefile. > (In the medium term, the plan is to have manifest-import run first > thing during boot, before any services have started. That might help > solve your problem, but not in the next 2 hours. Publishing that > proposal here is #2 on my list of things to do, after I publish the > next templates draft.) That also sounds like it will solve my problem. thanks! Mike
