Date: Fri, 30 Aug 2013 15:24:25 +0200
From: Natanael Copa <ncopa@alpinelinux.org>
To: HL <freemail.grharry@gmail.com>
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] Quagga setup bug
Message-ID: <20130830152425.53614bd6@ncopa-desktop.alpinelinux.org>
In-Reply-To: <52206A50.1030909@gmail.com>
References: <52205957.4090800@gmail.com>
	<20130830112719.06a9588c@ncopa-desktop.alpinelinux.org>
	<52206A50.1030909@gmail.com>
Precedence: list
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, 30 Aug 2013 12:48:00 +0300
HL <freemail.grharry@gmail.com> wrote:

> On 30/08/2013 12:27 =CE=BC=CE=BC, Natanael Copa wrote:
> > On Fri, 30 Aug 2013 11:35:35 +0300
> > HL <freemail.grharry@gmail.com> wrote:
> >
> >> Hello,
> >>
> >> It seems that when installing quagga the /etc/quagga dir
> >> is owned by root.root but it should be quagga.root
> > Are you sure? quagga should not edit the config files itself, should it?
> >
> > -nc
> Yes ...
> for instance ...
>=20
> Quagga programs have an interface similar to cisco
>=20
> telnet localhost zebra ...
> enable
> conf terminal
> bla bla bla
> write
>=20
> and the zebra process should be able to write the conf etc ...
>=20
>=20

I checked what fedora does:
http://pkgs.fedoraproject.org/cgit/quagga.git/tree/quagga.spec#n131

Basically, they make zebra.conf and vtysh.conf owned by quagga from
post-install script. They don't let quagga:quagga create new files or
delete existing by setting the permission on /etc/quagga. Instead,
quagga user can only edit existing files.

basically, it is up to the creator of the files and quagga package does
not create them. Maybe it should?

-nc


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---