tags #387699 confirmed pending
thanks
On Sat, Sep 16, 2006 at 09:24:33AM +0200, Petter Reinholdtsen wrote:
The exim4 init.d script is creating files in /var/run/exim4/, but do
not make sure the directory exist before doing this. This will break
when I change /var/run/ to be a tmpfs in
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Andreas Metzler]
Hello,
apt-file (and packages.d.o) will not help you, as Contents* only lists
files but not directories. I have used dpkg on merkel's mirror to
check for packages shipping /var/run or a subdirectory of /var/run
Package: exim4-base
Version: 5.40-8
Severity: important
Tags: patch
The exim4 init.d script is creating files in /var/run/exim4/, but do
not make sure the directory exist before doing this. This will break
when I change /var/run/ to be a tmpfs in initscripts.
Here is a patch to solve
[Andreas Metzler]
Hello,
this creates /var/run/exim4 with incorrect permissions.
exim4-base.postinst uses
install -d -oDebian-exim -gDebian-exim -m750 /var/run/exim4
to setup the directory.
OK.
BTW I am not convinced that generating this stuff in the init script
is the correct
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
Package: exim4-base
Version: 5.40-8
Severity: important
Tags: patch
The exim4 init.d script is creating files in /var/run/exim4/, but do
not make sure the directory exist before doing this. This will break
when I change
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Andreas Metzler]
[...]
You should somehow try to save this info, instead of changing every
package using its own directory in /var/run.
I fail to see the advantage of adding that complexity when we can just
add 'mkdir' calls to
[Andreas Metzler]
If directories under /var/run/ are no persistent, this breaks. (You
might tell me that I should have used /var/local/run. ;-)
Actually, you should have used /var/lib/package-name/. /var/lib/ is
the location for persistent stuff.
There is also the partial-upgrades issue,
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Andreas Metzler]
If directories under /var/run/ are no persistent, this breaks. (You
might tell me that I should have used /var/local/run. ;-)
Actually, you should have used /var/lib/package-name/. /var/lib/ is
the location for
[Andreas Metzler]
Removing these directories *will* break partial upgrades.
Why, if the packages using /var/run/directory/ are updated to create
these directories if they are missing after boot? As far as I can
see, there are not very many such packages including directories in
/var/run/ as
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Andreas Metzler]
Removing these directories *will* break partial upgrades.
*^*
Why, if the packages using /var/run/directory/ are updated to create
these directories if they are
[Andreas Metzler]
I was talking about *partial* upgrades, i.e. upgrading sysvinit
without upgrading e.g. exim4.
Right. I see. I guess we need to add conflicts on the packages
expecting persistense in /var/run/. Conflict: exim4-base (= 4.62-4)
might do it, if a updated exim4 version is
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[Andreas Metzler]
I was talking about *partial* upgrades, i.e. upgrading sysvinit
without upgrading e.g. exim4.
Right. I see. I guess we need to add conflicts on the packages
expecting persistense in /var/run/. Conflict:
On 2006-09-16 Petter Reinholdtsen [EMAIL PROTECTED] wrote:
[...]
Why, if the packages using /var/run/directory/ are updated to create
these directories if they are missing after boot? As far as I can
see, there are not very many such packages including directories in
/var/run/ as part of the
[Andreas Metzler]
Hello,
apt-file (and packages.d.o) will not help you, as Contents* only lists
files but not directories. I have used dpkg on merkel's mirror to
check for packages shipping /var/run or a subdirectory of /var/run in
the deb.
Great. Thank you. How did you do this? I would
14 matches
Mail list logo
