Shawn Walker wrote: > Dave Miner wrote: >> Shawn Walker wrote: >>> Dave Miner wrote: >>>> Shawn Walker wrote: >>>>> Greetings, >>>>> >>>>> The following webrev contains changes necessary to implement these >>>>> (known) bug entries: >>>>> >>>>> 1449 pkg requires operational history >>>>> >>>>> webrev: >>>>> http://cr.opensolaris.org/~swalker/pkg-1449/ >>>>> >>>>> gui diff (separate from webrev): >>>>> http://cr.opensolaris.org/~swalker/pkg-1449/gui.patch >>>>> >>>>> Sample history output (sorted based on mtime of each history entry >>>>> file): >>>>> >>>>> Short format: >>>>> http://cr.opensolaris.org/~swalker/pkg-1449/short.txt >>>>> >>>>> Long format: >>>>> http://cr.opensolaris.org/~swalker/pkg-1449/long.txt >>>>> >>>> It seems to me that we need a way for the distro constructor (at >>>> least) to be able to clear the history of the image it constructs, if >>>> for no other reason than to eliminate the space the history would use >>>> on the CD. >>> rm -rf /var/pkg/history :-) >>> >> Wrong answer. The DC (and anyone else who has this need) shouldn't be >> mucking around with your implementation details, which is what that >> directory represents. Add this to the already-outstanding bug for the >> same on the download cache, if you like, but I'd like a real interface, >> please. > > Didn't you see the :-) ? >
I did, but in the absence of any other text it's hard to interpret. > There is intentionally no interface to clear the download history. The > pkg history command is modeled after the "zpool history" command, which > as far as I know, doesn't provide a user a way to clear the history of a > pool. > > I understand your need, but I don't know how to satisfy the requirement > of "don't give users knobs they shouldn't have" and give others the > tools they need. > > I'm a little torn here, and I could use some direction. > Why shouldn't the user have the knob? They'll surely discover the ability to remove the /history directory if they really want to do so, and I think there are other legitimate uses besides DC's. If the requirement is for an auditable log of operations, then I'd suggest pkg should use auditing. While you're right that zpool doesn't offer a way to clear its log, it's also implemented as a ring buffer so that its space consumption is bounded. Dave _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
