Hi,
the init.d script works after changing permissions.In my case I have solved by
chown -R radicale:adm /etc/radicale
BestRoberto
Quoting Slavko (2017-04-13 11:01:31)
> On Fri, 07 Apr 2017 23:27:36 +0200 Jonas Smedegaard
> wrote:
>
> > When you sidestep the init script then it is your responsibility to
> > ensure that the environment is aligned with however you want to use
> > the package.
> >
> > This bugreport concern
Hi Slavko,
Quoting Slavko (2017-04-07 20:18:13)
> On Mon, 1 Aug 2016 21:04:02 +0100 D McA wrote:
> > I am also affected by this bug. I installed Radicale with apt-get
> > and did not suppress any package recommendations.
> today i install stretch's radicale in virtualbox:
>
> dpkg -l radicale
I am also affected by this bug. I installed Radicale with apt-get and
did not suppress any package recommendations.
> Did you edit /etc/radicale/config and /etc/default/radicale?
Yes. I enabled in the defaults (though in my experience with other packages
since moving to jessie, systemd tends to ignore /etc/defaults in many of them).
I am fairly certain this is a regression in my setup and that it used to star
Hi Stephen,
Quoting Stephen Paul Weber (2016-07-22 19:16:03)
> If I run `radicale -d` as root myself, it works fine. But if I run
> `/etc/init.d/radicale start` as root, it claims to be using a systemd
> service file and then does nothing. I cannot find said systemd
> service file -- can it b
Package: radicale
Version: 0.9-1+deb8u1
If I run `radicale -d` as root myself, it works fine. But if I run
`/etc/init.d/radicale start` as root, it claims to be using a systemd
service file and then does nothing. I cannot find said systemd service file
-- can it be that it was not created an
7 matches
Mail list logo
