Bug 7134

Summary:	Really execute rc.local after all services started + invite users to write custom systemd units
Product:	Mageia	Reporter:	Samuel Verschelde <stormi-mageia>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	dan, mageia, marja11
Version:	Cauldron	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	initscripts	CVE:
Status comment:

Description Samuel Verschelde 2012-08-21 12:41:29 CEST

Currently rc.local is executed among other services, without ordering.

In order to make it safer, it could be good to start as late as possible.

Replacing Type=forking with Type=idle could do the trick.

Note: Colin Guthrie seems to think it could, *maybe*, cause problems: "but it's based on Type=simple, not Type=forking, so not 100% sure if that will cause some knock on problems. but it's probably worth playing with."

Also, we should add as a comment in rc.local that the best way is to create a custom system unit, and maybe link to some documentation about it.

Samuel Verschelde 2012-08-21 12:42:08 CEST

Source RPM: (none) => initscripts
Whiteboard: (none) => MGA2TOO

Comment 1 Dan Fandrich 2013-07-26 21:28:43 CEST

Does someone have a suggestion for the wording that should go into rc.local? What exactly are the "problems" that using it could cause? Is it simply the lack of a fully deterministic execution order? Type=forking seems like an odd choice, since there's no guarantee rc.local does any forking, nor leaves any PID around to track.

CC: (none) => dan, mageia

Comment 2 Marja Van Waes 2016-06-24 21:25:49 CEST

This bug report saw no action since almost 3 years ago.

Is it still valid?

Keywords: (none) => NEEDINFO
CC: (none) => marja11
Whiteboard: MGA2TOO => (none)

Comment 3 Marja Van Waes 2016-07-13 18:37:13 CEST

(In reply to Marja van Waes from comment #2)
> This bug report saw no action since almost 3 years ago.
> 
> Is it still valid?

No reply, so closing as OLD

Please reopen if needed.

Status: NEW => RESOLVED
Resolution: (none) => OLD