Jan Hnatek wrote:
It doesn't look like 6517953, I created the instance with
svccfg -s pkg/server add <..>
svccfg -s pkg/server:<..> addpg pkg application
...
I did a couple of tests and the issue is probably a bit
simpler - a safe way to reproduce is
- perform one start without the external drive
- reboot and plug in the drive
The pkg/server service creates an empty repository
at the specified mount-point, breaking the next
boot with the drive connected.
To clean up this situation I need to:
- remove the contents of the mount-point
- svcadm clear filesystem/local
So I wonder if this is seen as a bug and pkg should
somehow remember it was populated and/or be more careful
when started with an empty directory.
By design, the pkg.depotd server creates a repository where it is told
to if one does not exist already.
The pkg/server SMF service is dependent on filesystem-local, and will
not start until it does (assuming SMF handles the dependencies as expected).
I'm now confused as you originally asked if the depot was starting
before filesystem-local.
Cheers,
--
Shawn Walker
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
