[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#760423: marked as done (lighttpd: systemd service does not automatically create /var/run/lighttpd)

Your message dated Thu, 14 Feb 2019 12:03:02 +0100
with message-id <20190214110258.jpjjmsxu5v7qfq32@laureti-dev>
and subject line Re: Bug#760423: lighttpd: systemd service does not automatically create /var/run/lighttpd
has caused the Debian Bug report #760423,
regarding lighttpd: systemd service does not automatically create /var/run/lighttpd
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
760423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760423
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lighttpd
Version: 1.4.35-3
Severity: important

Dear Maintainer,

When switching to systemd, the directory /var/run/lighttpd is not automatically
created (and chown www-data), causing the resulting service to fail.

A workaround is to manually create the directory with the right ownership, but
I have not verified if this persists across restarts.

Please automatically create the directory if it does not already exist.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lighttpd depends on:
ii  init-system-helpers         1.21
ii  libattr1                    1:2.4.47-1
ii  libbz2-1.0                  1.0.6-7
ii  libc6                       2.19-9
ii  libfam0                     2.7.0-17.1
ii  libldap-2.4-2               2.4.39-1.1+b1
ii  libpcre3                    1:8.35-3
ii  libssl1.0.0                 1.0.1i-2
ii  libterm-readline-perl-perl  1.0303-1
ii  lsb-base                    4.1+Debian13
ii  mime-support                3.56
ii  perl                        5.18.2-7
ii  systemd                     208-8
ii  zlib1g                      1:1.2.8.dfsg-1

Versions of packages lighttpd recommends:
ii  spawn-fcgi  1.6.4-1

Versions of packages lighttpd suggests:
ii  apache2-utils  2.4.10-1
ii  openssl        1.0.1i-2
pn  rrdtool        <none>

-- Configuration Files:
/etc/lighttpd/lighttpd.conf changed [not included]
/etc/logrotate.d/lighttpd changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,

On Tue, Dec 04, 2018 at 09:14:12AM +0100, Helmut Grohne wrote:
> Can you reproduce the issue at all? If no, please close the bug.

I received a private reply that the bug likely no longer exists. It
could have been connected to a switch from sysvinit to systemd.

I also wondered whether possibly the tmpfile snippet wasn't run in
postinst, because it wasn't debian/$pkg.tmpfile, but indeed debhelper
does pick up manually installed tmpfiles and creates the relevant
postinst snippet.  My other theory thus proved wrong.

I don't think there is anything actionable left on this bug and
therefore close it.

Helmut

--- End Message ---
Reply to: