just to keep all information together… Begin forwarded message:
> From: Gürkan Myczko <gur...@phys.ethz.ch> > Date: May 24, 2023 at 20:43:49 GMT+2 > To: debian-de...@lists.debian.org > Subject: future of rwhod/rwho/ruptime, and a shell implementation of it > called ruptime > > hello > > i've always liked the ruptime command, it was so useful to see your machines > up or down, and for long and with what load, > but then came multiprocessor machines, and gpus. and it was all clear text > sent over the network, and only in one network. > so i started to try to do something about and out came: > https://github.com/alexmyczko/ruptime/tree/debian (or on salsa: > https://salsa.debian.org/debian/ruptime). i have tried to make it useful for > where i use it, you can read the why on the webpage > or salsa page. (using it on x86_64, and raspberry pies) > > rwho was not implemented, but it would be easy to do so. and it's also easy > to extend it for any sort of data that you want to > be easily accessible. > > since there's that older implementation in C: > netkit-rwho is orphaned, https://bugs.debian.org/1020628 > build time limit for NUSERS (1000): https://bugs.debian.org/489787 > build time option for alarm period: https://bugs.debian.org/360884 > > these are all much easier in the script, but it is much less efficient. > > any feedback if this is a good idea, or wishes? according popcon there's some > users: > https://qa.debian.org/popcon.php?package=netkit-rwho > (glad i'm not alone) > > best > tar
