Bug 43486 - Memcache init script and systemd service file have different behavior (multiple vs one instance)
Summary: Memcache init script and systemd service file have different behavior (multip...
Status: RESOLVED DUPLICATE of bug 45960
Alias: None
Product: UCS
Classification: Unclassified
Component: General
Version: UCS 4.2
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on:
Blocks: 42267 43565 44189 44221
  Show dependency tree / graph
 
Reported: 2017-02-02 15:19 CET by Jürn Brodersen
Modified: 2017-12-29 15:01 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
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):
Customer ID:
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 Jürn Brodersen univentionstaff 2017-02-02 15:19:58 CET 
The systemd service file for memcache, only starts memcache for /etc/memcache.conf.
The old init script started one memcache instance for every /etc/memcache_$server.conf file.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784357

univention-saml and univention-self-service need the old behavior.

For some reason invoke-rc.d calls the init script for memcache if called through another init script. But calls the service file if called directly on a console.
Due to that univention-saml still works because it calls "invoke-rc.d memcached start" inside its own init script.
Comment 1 Stefan Gohmann univentionstaff 2017-12-29 15:01:25 CET 
Should be fixed with Bug #45960.

*** This bug has been marked as a duplicate of bug 45960 ***