Aurelien Jarno dixit:
[ explanations ]
>Therefore there is no bug, neither in glibc nor in the manpage. Closing
>it.
Agreed. Thank you for reviewing the problem, though.
bye,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
On Thu, 18 Jul 2019, Thorsten Glaser wrote:
> glibc maintainers: unsure why screen works but not the example
> code given that screen isn’t sgid… maybe you should have a look
> at that, it still doesn’t work with the correct utmp permissions.
This might also be a bug in the example program; if
Processing commands for cont...@bugs.debian.org:
> reassign 932380 initscripts
Bug #932380 [screen] screen: Utmp slot not found -> not removed
Bug reassigned from package 'screen' to 'initscripts'.
No longer marked as found in versions screen/4.6.2-3.
Ignoring request to alter fixed versions of
reassign 932380 initscripts
found 932380 2.95-1
notfound 932380 2.93-8
retitle 932380 initscripts: /etc/init.d/bootmisc.sh: wrong /var/run/utmp
permissions
severity 932380 important
unblock 932380 by 932384
block 932384 by 932380
thanks
On Thu, 18 Jul 2019, Thorsten Glaser wrote:
> After
On Thu, 18 Jul 2019, Thorsten Glaser wrote:
> utmp entries cannot be added (and the GNU screen source code contains
> curse^Wcomplaints about the GNU API for utmp lacking the ability to
> return success/error information, so the applications cannot even de‐
> tect this!), while the file is set up
Package: libc6
Version: 2.28-10
Severity: important
After hitting #932380 I looked at the source code of GNU screen,
saw it uses the getutline(3) function, and compiled the example
from its manpage.
The output is not what I expected:
tglase@tglase:~ $ ./a.out
before adding entry:
tglase :0
6 matches
Mail list logo