Your message dated Fri, 20 Apr 2018 12:55:19 +0000
with message-id <[email protected]>
and subject line Bug#895904: fixed in runit 2.1.2-12
has caused the Debian Bug report #895904,
regarding getty-run may conflicts with other gettys
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
895904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: getty-run
Version: 2.1.2-11
Severity: important
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.12-van (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init) ( EDIT: It's actually runit )
Versions of packages getty-run depends on:
ii runit 2.1.2-11
ii runit-helper 2.7.2
Versions of packages getty-run recommends:
ii fgetty 0.7-3
getty-run suggests no packages.
-- Configuration Files:
/etc/sv/getty-tty3/finish changed:
SERVICE=getty-tty3
[ $1 = 163 ] && echo "runsv: ERROR $1 in $SERVICE: another getty already on
tty3" \
&& sv d $(dirname $0) && exit 0
exec utmpset -w tty3
/etc/sv/getty-tty3/run changed:
pgrep -x getty -t tty3 && exit 163
pgrep -x agetty -t tty3 && exit 163
! type fgetty >/dev/null 2>&1 || exec chpst -P fgetty tty3
exec getty 38400 tty3 linux
-- no debconf information
Welcome back :)
The getty-run package does not check whether the tty is busy with another getty
(nor try to stop the
already-running getty) before starting the getty-ttyX services.
As far as I know the default is to have a getty running in each of the six
ttys, so the conflict will
happen by default unless the admin takes some action to prevent it.
In my case the getty-run package was installed as a dependency of runit-init,
so I start noticing the cpu
usage at 100% and it took me a while to understand why..
A easy way to prevent this is to check for an already runing getty (and exit if
such a getty is found) in
the run file as you see in the /etc/sv/getty-tty3/run file attached above;
also, it's good to print some debug message that explain why the service is not
running and finally do a
'sv d service', otherwise runit will endlessly try to restart the service ( see
the finish file above).
Many Thanks
Lorenzo
--- End Message ---
--- Begin Message ---
Source: runit
Source-Version: 2.1.2-12
We believe that the bug you reported is fixed in the latest version of
runit, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dmitry Bogatov <[email protected]> (supplier of updated runit package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 20 Apr 2018 14:46:17 +0300
Source: runit
Binary: runit runit-systemd runit-sysv getty-run runit-init
Architecture: source
Version: 2.1.2-12
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov <[email protected]>
Changed-By: Dmitry Bogatov <[email protected]>
Description:
getty-run - runscripts to supervise getty processes
runit - system-wide service supervision
runit-init - system-wide service supervision (as init system)
runit-systemd - system-wide service supervision (systemd integration)
runit-sysv - system-wide service supervision (sysv integration)
Closes: 895904 895914
Changes:
runit (2.1.2-12) unstable; urgency=medium
.
* Improve 'contrib/1' to support boot in single mode. (Closes: #895914)
+ Thanks: Lorenzo Puliti <[email protected]>
* Simplify code (in particular, debian/rules), generating getty runscripts.
* Improve getty runscripts to not waste CPU when tty is already busy.
(Closes: #895904)
+ Thanks: Lorenzo Puliti <[email protected]>
Checksums-Sha1:
932b93287b2487e09af19aa939cef9103a94de8d 2091 runit_2.1.2-12.dsc
d0c04fed2ff4cbc8616e2d7018fb84963bd5ef90 23740 runit_2.1.2-12.debian.tar.xz
855716d336dc0605b416093de402ba6ec5e76e89 5281 runit_2.1.2-12_source.buildinfo
Checksums-Sha256:
99e8e7f588f1552a753ca8e2a322791de9eb4e945d66b84e0436f53bec62db37 2091
runit_2.1.2-12.dsc
f61e46b7e7568b731b0d10c69a7252c6b1f73fb6db47ad1e96fc0beb0f6281dd 23740
runit_2.1.2-12.debian.tar.xz
d364cab6033e34aea17e9501eedd9d7d201655396c622d70614479591f788fc6 5281
runit_2.1.2-12_source.buildinfo
Files:
fa5057a9ebaf979f9282b0238ea394b1 2091 admin optional runit_2.1.2-12.dsc
1b2d624698eed00069844f24a0451bc0 23740 admin optional
runit_2.1.2-12.debian.tar.xz
2212214ea78c5d6cdf93120f950b9151 5281 admin optional
runit_2.1.2-12_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEbEPcK+5mZmLK5jNU1v5xA2P4XdMFAlrZ3V8ACgkQ1v5xA2P4
XdNZUw//fq2bYKgmQiBcu49woeHV8jnnfhD+IvMLkpI/nmW43igSOkCqea0hUwST
wSyN+aMgnkCWv/aGWDtQImDa9AW035bkhl6lv2tIDuUMHF9Cie55SgVYvMURU+9p
D4rp+2n708KJiQbq81NRl28VzBMNK1Q/bMlRn+pwVtLoeB9ki14MashuhZ6ZoOjc
MZipInCRH0jI4EaQmWITEzql8QVO+64gsbS8dLDBiPebONr+ddK3mKKT9BFOr6T9
MHHj/UxhOYlADiV+TbS2C0Q57KIqYJGc4Qo6Z89IeWPTgbs1ze0Hw8Rdqup09cOk
LTVyPwrhNWeAX+ntbgdsdAhY3FEHkPpgeY471CLtpIk9h2EGxHbb2Eg8bXygEDke
7o0QF5S1dL/ybcfe2URwiiin3A+tfuYfnPyapiw1uyWXOgN3Ja5wVn2tJOYL6ysl
qVOtJD7L1QVG49VoqqokOF2b/LgNQ9rvDzSN421qEnddaP9oHiSvpD8FKMYIPZvl
L4Ahdf+HhNtWyPMme2Deh6qcks96fMoGJL8UaoZT7nxuf8/5x3dtXwe9AYYiZVrQ
70G7ojq0gJKTrj1rR+1souI83LLVG44SaO0iCXoOn3Kgz6fOyzjBVbm/VmByA96G
LKouxkRTxjfMCk4f8Q7Y/2DqGZeJTVF31RqEJzUIRRkpj0ae7Jo=
=qdAa
-----END PGP SIGNATURE-----
--- End Message ---
