Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Just to tidy up after mwdecavia (yes, his post was off-topic but that's no reason not to close it down and tidy up the loose ends):
I followed all those "clues" that he provided individually, just to set my mind at rest. Most of them were ultimately references to the symbolic link to elogind in the /run directory. For example, the current working directory of PID 1 is /, so /proc/1/cwd/run is just /run. And there's that link again. It's elogind pretending to be systemd for the benefit of any software (cups for example) that expects systemd to be around.
The one exception that I found was some actual systemd headers in /usr/include/elogind/systemd. But headers are inert; they don't do anything to to your system. They're clearly there for the benefit of people who want to compile something that expects systemd to be on the machine. Again, it's elogind in wolf's clothing.
Actually it is only required because of certain references and "requirements" that have been entered into the KDE source referencing SystemD features or services. If someone has the time and motivation to revert all of that pointless cruft then neither EloginD nor SystemD would be required. IF you MUST have one, EloginD is far less problematic compared to SystemD.
Personally I have not the time or energy to re-maintain KDE after it leaves the developers release, so I can live with EloginD. I will be happy when/if SystemD just goes away and we can stop dealing with the silliness!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.