-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Florian Weimer wrote: > * Christian Perrier: > >> An easy and not too much invasive fix would be to copy the file in /root >> instead of /tmp. > > Isn't this a policy violation?
It would be good to get clarification on this point. Just to be sure everyone understands what is happening here (and maybe suggest a better way). The requirement is to purge Axyl fully (apt-get remove --purge). For that the postrm script needs to know the current locations of home, data and logs which the user may have changed since installation. These are defined in /etc/axyl/axyl.conf but this file is removed by the time postrm runs. Hence I currently copy it to a temporary location in prerm for the short time that the purge runs, then source it from that temporary location in postrm, use the settings to purge the home, data and log areas for Axyl-owned content, and then finally remove the temporary conf file. Root is doing this, and I imagined (perhaps erroneously) that using /root for this brief staging of the conf file would have been ok. If not then what is a better way to carry the conf settings from prerm --> postrm? Would the debconf db do the trick, or is that purged by then too? Any help very much appreciated.;-) Cheers, Paul. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH3ZhVtfkpAgkMOyMRAt62AKDA+v3wxDETSztN+laC7XZvvCkItgCgrVq1 GAkdkHrLf3GOCrzg/YPEM7U= =gqMk -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
