[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
RE: Removing directories/files in RPM erase
- From: "Hajducko, Steven" <steven hajducko digitalinsight com>
- To: "RPM Package Manager" <rpm-list redhat com>
- Subject: RE: Removing directories/files in RPM erase
- Date: Thu, 22 May 2008 09:23:49 -0700
Cool, thanks for the sage words of advice guys.
As it turns out, the RPM would own this directory, because it's installing to it's own directory under /opt and it's in that directory that it's creating these files during run time.
Unfortunately, I can't possibly know the name of each file that it's going to create ( it creates ssl certs based on the hosts that connect to it.. ), so it looks like the %ghost attribute isn't going to work and I'll just have to go along with uninstall scripts.
Thanks again
--
sh
> -----Original Message-----
> From: rpm-list-bounces redhat com
> [mailto:rpm-list-bounces redhat com] On Behalf Of Tim Mooney
> Sent: Wednesday, May 21, 2008 10:08 PM
> To: RPM Package Manager
> Subject: Re: Removing directories/files in RPM erase
>
> In regard to: Re: Removing directories/files in RPM erase,
> Jeff Johnson...:
>
> >>> However, when I remove the RPM, it doesn't remove the directories
> >>> because they aren't empty. Should I setup a post
> uninstall to see
> >>> if this is the last instance of the package and if it is,
> manually
> >>> remove those directories?
> >>
> >> Look up the %ghost attribute (?, token?, I'm not sure what
> it should
> >> be classified as) and see if that does what you need.
> >>
> >
> > %ghost won't solve removing nonempty directories. The %ghost
> > directive, with its mysterious name, claims ownership for a
> package of
> > a pre-existing path.
>
> No, but if the %ghost is applied to the log files and the
> other files that are created as part of the execution of the
> programs, then those will be removed when the package is
> removed, and hence the directory will be empty.
>
> > Establishing ownership of a directory in packaging,
> particularly for
> > some public path in which, say, modules are installed, can be quite
> > complicated.
>
> :-) Don't I know it! I started a pretty lengthy thread about
> that exact issue right after 4.4.7 or 4.4.8 came out and I
> first experienced needing to claim directories (which I also
> think is The Right Thing, it's just hard to do in some cases
> because of ambiguous ownership).
>
> Tim
> --
> Tim Mooney
> mooney dogbert cc ndsu NoDak edu
> Information Technology Services (701) 231-1076 (Voice)
> Room 242-J6, IACC Building (701) 231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
>
> _______________________________________________
> Rpm-list mailing list
> Rpm-list redhat com
> https://www.redhat.com/mailman/listinfo/rpm-list
>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]