Re: [opensuse-factory] Re: Re: Tumbleweed: systemd cannot start privoxy

On 11/22/2013 10:00 AM, Yamaban wrote:

On Fri, 22 Nov 2013 11:04, Brian K. White wrote:

...

On 11/20/2013 10:34 PM, Yamaban wrote: [snip]

...

...

/etc/privoxy THIS IS A LINK (points to /var/lib/privoxy/etc)

What genius thought it was a good idea to move system-specific config data out of /etc, so that when an admin backs up /etc, they DON'T in fact have all the important stuff they are SUPPOSED to have?

I don't use privoxy or 13.1, this is a general common sense thing and doesn't matter what package or OS.

Have you ever heard of the concept of jailed services, or chrooted daemons?

To put their config in the base systems /etc dir fucks up their working something firce, as they operate only below a specific directory, in case of privoxy this dir is /var/lib/privoxy/ .

Anything outside of this dir is (or should be) invisible, inaccessible, and just not there for these services.

The basics of chrooted daemons should be basic knowlege of anybody that calls him- or herself admin of ANY unix-like system, this includes Linux-Kernel based systems.

For anybody else there are nicely preped lectures on deamons and their workings around for free on the internet.

- Yamaban.

I am quite familiar with chroot jailed services. If the real info is stored somewhere under /etc, and only a copy is generated on the fly in a jail somewhere else, that is fine. And no reason for any such symlink. But why stop at jails? You could have 50 containerized instances of the same service. Where should a symlink like that point then? Pick someone else to impress with your "basic knowledge of unix". ;) -- bkw -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org