Bug 36702 – univention-maintenance: dmesg -n 8 is invalid

Bug 36702 - univention-maintenance: dmesg -n 8 is invalid


Summary:	univention-maintenance: dmesg -n 8 is invalid

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Update - univention-updater
Version:	UCS 4.0
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	36508
	Show dependency tree / graph

Reported:	2014-11-14 14:11 CET by Philipp Hahn
Modified:	2019-01-03 07:17 CET (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 Philipp Hahn

2014-11-14 14:11:47 CET

# /etc/init.d/univention-maintenance start
...
dmesg: unknown level '8'

# grep -n dmesg /etc/init.d/univention-maintenance 
51:             dmesg -n 1
224:            dmesg -n 8

# dmesg --help
...
 -n, --console-level <level> set level of messages printed to console
...
Supported log levels (priorities):
   emerg - system is unusable
   alert - action must be taken immediately
    crit - critical conditions
     err - error conditions
    warn - warning conditions
  notice - normal but significant condition
    info - informational
   debug - debug-level messages

Comment 1 Stefan Gohmann

2019-01-03 07:17:25 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.