Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-02-03 Thread Andras Korn
On Wed, Jan 30, 2019 at 08:48:34PM +, Dmitry Bogatov wrote: > > > What is so bad about cluttering environment of daemon? > > > > Normally you'd want to avoid passing unnecessary environment variables to > > daemons. Maybe they'll affect its operation in some way; maybe they'll > > affect a

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-30 Thread Dmitry Bogatov
[2019-01-27 18:56] Andras Korn > > Complicated. And depends on $0 trickery. We, at sysvinit team, had > > problems with $0 trickery. > > How is this trickery? We're just obtaining the name of the script being > executed, and its path. Relying on $0 makes me uneasy. Because one day I may want

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-27 Thread Andras Korn
On Sat, Jan 26, 2019 at 10:17:05AM +, Dmitry Bogatov wrote: Hi, > > I believe instead of > > > > rm /etc/service/getty-@TTY@ > > > > you should do > > > > rm "$(pwd)" > > > > because then it won't matter what the service is called and where the > > runsvdir root is (/etc/service or somewhere

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-26 Thread Dmitry Bogatov
[2019-01-25 10:34] Andras Korn > I believe instead of > > rm /etc/service/getty-@TTY@ > > you should do > > rm "$(pwd)" > > because then it won't matter what the service is called and where the > runsvdir root is (/etc/service or somewhere else). I find it unsafe. Explicit is better implicit.

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-25 Thread Andras Korn
On Tue, Jan 22, 2019 at 07:16:43PM +, Dmitry Bogatov wrote: Hi, > > (Alternatively, the getty run scripts could start with something like this: > > > > [ -c /dev/ttyX ] || rm /etc/service/getty-ttyX > > > > and /etc/runit/1 could re-create these symlinks, just to be absolutely sure. > > > >

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-22 Thread Dmitry Bogatov
[2019-01-18 20:27] Andras Korn > sorry, didn't look at bug mail for a while. > > > > However, whenever the getty-run package is installed in a vserver, I have > > > to > > > manually remove the /service/getty-tty* symlinks. > > > > > > Can you please modify the postinst script so it only

Bug#914788: Please don't enable getty services for tty devices that don't exist

2019-01-18 Thread Andras Korn
On Wed, Nov 28, 2018 at 06:47:59PM +, Dmitry Bogatov wrote: Hi, sorry, didn't look at bug mail for a while. > > However, whenever the getty-run package is installed in a vserver, I have to > > manually remove the /service/getty-tty* symlinks. > > > > Can you please modify the postinst

Bug#914788: Please don't enable getty services for tty devices that don't exist

2018-11-28 Thread Dmitry Bogatov
[2018-11-27 11:14] Andras Korn > Ideally, I wouldn't even have to install the getty-run package, but I > understand it's there to help avoid people shooting themselves in the > foot by installing runit and then not having any way to log in. True. I too do not like hard dependency, but Debian

Bug#914788: Please don't enable getty services for tty devices that don't exist

2018-11-27 Thread Andras Korn
Package: getty-run Version: 2.1.2-18 Severity: wishlist Hi, I use runit as init extensively in linux-vserver guests which don't have console devices and thus can't run getty. Ideally, I wouldn't even have to install the getty-run package, but I understand it's there to help avoid people