409469 – sys-process/runit - make getty-ttyX symlinks optional

Bug 409469 - sys-process/runit - make getty-ttyX symlinks optional

Summary: sys-process/runit - make getty-ttyX symlinks optional

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal minor (vote)
Assignee:	William Hubbs

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2012-03-23 20:57 UTC by Ron Bickers
Modified:	2014-11-13 19:47 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

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 Ron Bickers 2012-03-23 20:57:26 UTC

In every version of sys-process/runit, the ebuild adds symlinks that enable and thus immediately start getty-ttyX services.  I don't want these services enabled in runit at all, so I'm forced to remove the symlinks every time I upgrade.

Reproducible: Always

Steps to Reproduce:
1. Upgrade sys-process/runit
2. Unwanted /var/service/getty-ttyX symlinks are created and getty services start immediately.


Expected Results:  
The ebuild should leave /var/service alone and let users enable services as desired.

Comment 1 William Hubbs gentoo-dev

2014-11-13 19:47:51 UTC

This should be fixed in 2.1.2.
Now the ebuild will set up services for you once, when you install the
package for the first time, but it should leave them alone after that.