Bug 30392 – syslog can not be deactivated/modified for thin-clients (overlayfs)

Bug 30392 - syslog can not be deactivated/modified for thin-clients (overlayfs)


Summary:	syslog can not be deactivated/modified for thin-clients (overlayfs)

Status:	NEW

Product:	Z_Univention Corporate Client (UCC)
Classification:	Unclassified
Component:	Image Thin Client
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal
Target Milestone:	UCC 2.x
Assigned To:	UCC maintainers
QA Contact:

URL:
Keywords:	interim-3

Depends on:	34794
Blocks:
	Show dependency tree / graph

Reported:	2013-02-11 15:10 CET by Felix Botner
Modified:	2014-05-21 13:42 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2013-02-11 15:10:49 CET

The syslog Settings for the system (not initrd) are stored in UCRV grub/append during the installation. The configuration template for /etc/rsyslog.d/100-ucc.conf extract those settings from grub/append

On systems with overlayfs the /etc/rsyslog.d/100-ucc.conf is always "reverted" to "installation state" and there is no way to modify these settings. 
An ucr policy also does not help because at the time grup/append is modified resyslogd is already running.


Fix: syslog settings should be extracted from /proc/cmdline instead of grub/append
(1) /etc/rsyslog.d/100-ucc.conf extracts syslog settings from /proc/cmdline
(2) /etc/init/rsyslog.conf commits /etc/rsyslog.d/100-ucc.conf

Comment 1 Moritz Muehlenhoff

2013-02-11 15:19:55 CET

The current behaviour has been documented in the UCC 1.0 manual.

Comment 2 Felix Botner

2014-05-21 09:24:37 CEST

As discussed, at first we have to decide where and how UCC client options will be stored. Then we can think about how special options are applied to the system.