I don't want to see the intrusive elogind display
that comes after the login prompt but before
I can log in. I tried chmoding -x the entry
in /etc/rc.d but that didn't kill the daemon.

I know this is needed by Gnome, which I thought
that Patrick had abandoned long ago.

How do I kill the elogin daemon?

Oh, and another problem with current:
the conf file for slocate has two export
commands that bomb out locate.

On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:

> I don't want to see the intrusive elogind display
> that comes after the login prompt but before
> I can log in. I tried chmoding -x the entry
> in /etc/rc.d but that didn't kill the daemon.
>
> I know this is needed by Gnome, which I thought

To quote the Gentoo wiki...
"elogind is the systemd project's logind,
extracted to a standalone package. It's
designed for users who prefer a non-systemd
init system, but still want to use popular
software such as KDE/Wayland or GNOME that
otherwise hard-depends on systemd."

I think the key phrase here is "to use popular
software such as KDE/Wayland ... that
otherwise hard-depends on systemd."

Apparently, if you want KDE, you must have
elogind.

> that Patrick had abandoned long ago.
[snip]

--
Lew Pitcher
"In Skills, We Trust"

root <NoEMail@home.org> wrote:
> I don't want to see the intrusive elogind display
> that comes after the login prompt but before
> I can log in. I tried chmoding -x the entry
> in /etc/rc.d but that didn't kill the daemon.

Just removing execute permission from the rc.d file does nothing to the
currently running daemon.

Removing execute permission from the rc.d file just stops the daemon
from being launched the next time you reboot.

If you want to kill the running daemon, then you should kill the
daemon. See the "kill" command.

Also, the rc.d file you changed likely takes parameters:

start - starts the daemon
stop - stops the currently running daemon
....

So what you should have done is:

/etc/rc.d/rc.elogind stop

before you did a "chmod -x /etc/rc.d/rc.elogind"

The first would stop the running deamon. The second would stop it from
launching again after the next reboot.

Note, I'm assuming the rc file name was "rc.elogind" above, you didn't
say here, and for this message the above is enough for you to adapt the
details to the exact name.

On 21.08.2021 at 15:57, Lew Pitcher scribbled:

> On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:
>
> > I don't want to see the intrusive elogind display
> > that comes after the login prompt but before
> > I can log in. I tried chmoding -x the entry
> > in /etc/rc.d but that didn't kill the daemon.
> >
> > I know this is needed by Gnome, which I thought
>
> To quote the Gentoo wiki...
> "elogind is the systemd project's logind,
> extracted to a standalone package. It's
> designed for users who prefer a non-systemd
> init system, but still want to use popular
> software such as KDE/Wayland or GNOME that
> otherwise hard-depends on systemd."
>
> I think the key phrase here is "to use popular
> software such as KDE/Wayland ... that
> otherwise hard-depends on systemd."
>
> Apparently, if you want KDE, you must have
> elogind.

No, only if you want KDE Plasma running on top of Wayland instead of
on top of X.org.

--
With respect,
= Aragorn =

On Sat, 21 Aug 2021 19:46:56 +0200, Aragorn wrote:

> On 21.08.2021 at 15:57, Lew Pitcher scribbled:
>
>> On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:
>>
>> > I don't want to see the intrusive elogind display
>> > that comes after the login prompt but before
>> > I can log in. I tried chmoding -x the entry
>> > in /etc/rc.d but that didn't kill the daemon.
>> >
>> > I know this is needed by Gnome, which I thought
>>
>> To quote the Gentoo wiki...
>> "elogind is the systemd project's logind,
>> extracted to a standalone package. It's
>> designed for users who prefer a non-systemd
>> init system, but still want to use popular
>> software such as KDE/Wayland or GNOME that
>> otherwise hard-depends on systemd."
>>
>> I think the key phrase here is "to use popular
>> software such as KDE/Wayland ... that
>> otherwise hard-depends on systemd."
>>
>> Apparently, if you want KDE, you must have
>> elogind.
>
> No, only if you want KDE Plasma running on top of Wayland instead of
> on top of X.org.

OK. Good to know.

So, I wonder why Pat included elogind.

--
Lew Pitcher
"In Skills, We Trust"

Rich <rich@example.invalid> wrote:
>
> Also, the rc.d file you changed likely takes parameters:
>
> start - starts the daemon
> stop - stops the currently running daemon
> ...
>
> So what you should have done is:
>
> /etc/rc.d/rc.elogind stop
>
> before you did a "chmod -x /etc/rc.d/rc.elogind"
>
> The first would stop the running deamon. The second would stop it from
> launching again after the next reboot.
>
> Note, I'm assuming the rc file name was "rc.elogind" above, you didn't
> say here, and for this message the above is enough for you to adapt the
> details to the exact name.

Thanks for responding. I know about start/stop. I chmoded -x, then
rebooted. The daemon still came up. There is some executable involving
elogin, I tried renaming that, still the daemon. I don't care about
kde or plasma or any of that stuff.

root <NoEMail@home.org> wrote:
> Rich <rich@example.invalid> wrote:
>>
>> Also, the rc.d file you changed likely takes parameters:
>>
>> start - starts the daemon
>> stop - stops the currently running daemon
>> ...
>>
>> So what you should have done is:
>>
>> /etc/rc.d/rc.elogind stop
>>
>> before you did a "chmod -x /etc/rc.d/rc.elogind"
>>
>> The first would stop the running deamon. The second would stop it from
>> launching again after the next reboot.
>>
>> Note, I'm assuming the rc file name was "rc.elogind" above, you didn't
>> say here, and for this message the above is enough for you to adapt the
>> details to the exact name.
>
> Thanks for responding. I know about start/stop. I chmoded -x, then
> rebooted. The daemon still came up.

And how do we know you rebooted if you don't tell us?

> There is some executable involving elogin, I tried renaming that,
> still the daemon.

You renamed the executable that is elogin and yet it still was
launched? That is quite odd.

Is elogin installed as a standalone package? You might test
'removepkg' on the package to see if that helps (or hurts).

On Sat, 21 Aug 2021 18:03:21 +0000, Lew Pitcher wrote:

> On Sat, 21 Aug 2021 19:46:56 +0200, Aragorn wrote:
>
>> On 21.08.2021 at 15:57, Lew Pitcher scribbled:
>>
>>> On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:
>>>
>>> > I don't want to see the intrusive elogind display
>>> > that comes after the login prompt but before
>>> > I can log in. I tried chmoding -x the entry
>>> > in /etc/rc.d but that didn't kill the daemon.
>>> >
>>> > I know this is needed by Gnome, which I thought
>>>
>>> To quote the Gentoo wiki...
>>> "elogind is the systemd project's logind,
>>> extracted to a standalone package. It's
>>> designed for users who prefer a non-systemd
>>> init system, but still want to use popular
>>> software such as KDE/Wayland or GNOME that
>>> otherwise hard-depends on systemd."
>>>
>>> I think the key phrase here is "to use popular
>>> software such as KDE/Wayland ... that
>>> otherwise hard-depends on systemd."
>>>
>>> Apparently, if you want KDE, you must have
>>> elogind.
>>
>> No, only if you want KDE Plasma running on top of Wayland instead of
>> on top of X.org.
>
> OK. Good to know.
>
> So, I wonder why Pat included elogind.

To answer my own question...

Slackware 15 will include an option to run Wayland. It will also include
KDE. KDE/Wayland requires elogind, and elogind can substitute for the
existing ConsoleKit2.

So, PV moved from ConsoleKit2 to elogind to facilitate KDE under Wayland
on Slackware 15.

--
Lew Pitcher
"In Skills, We Trust"

Rich <rich@example.invalid> wrote:
>
>
> You renamed the executable that is elogin and yet it still was
> launched? That is quite odd.

The executable I renamed was elogin-xxx, meaning something
else was in the name. I have to reboot my system to find
out more.
>
> Is elogin installed as a standalone package? You might test
> 'removepkg' on the package to see if that helps (or hurts).

I don't know about that too.

I'll get back to you.

Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:
>
> Slackware 15 will include an option to run Wayland. It will also include
> KDE. KDE/Wayland requires elogind, and elogind can substitute for the
> existing ConsoleKit2.
>
> So, PV moved from ConsoleKit2 to elogind to facilitate KDE under Wayland
> on Slackware 15.
>

There were some ConsoleKit packages.

root <NoEMail@home.org> wrote:
> Rich <rich@example.invalid> wrote:
>>
>>
>> You renamed the executable that is elogin and yet it still was
>> launched? That is quite odd.
>
> The executable I renamed was elogin-xxx, meaning something
> else was in the name. I have to reboot my system to find
> out more.
>>
>> Is elogin installed as a standalone package? You might test
>> 'removepkg' on the package to see if that helps (or hurts).
>

It was a package (elongind-246.1.10) which, when removed, make
the problem go away. I guess I'll never know how the daemon
rose up after chmoding the rc file.

root <NoEMail@home.org> wrote:
> root <NoEMail@home.org> wrote:
>> Rich <rich@example.invalid> wrote:
>>>
>>>
>>> You renamed the executable that is elogin and yet it still was
>>> launched? That is quite odd.
>>
>> The executable I renamed was elogin-xxx, meaning something
>> else was in the name. I have to reboot my system to find
>> out more.
>>>
>>> Is elogin installed as a standalone package? You might test
>>> 'removepkg' on the package to see if that helps (or hurts).
>>
>
> It was a package (elongind-246.1.10) which, when removed, make the
> problem go away.

Then problem solved.

> I guess I'll never know how the daemon rose up after chmoding the rc
> file.

Changing the execution bit on the rc file just controls whether the rc
file is executed at boot or not. It means nothing if some other
program somewhere launches the deamon directly if it (the other
program) finds the deamon is not running.

with <sfr7q2$8m6$2@dont-email.me> Lew Pitcher wrote:
> On Sat, 21 Aug 2021 15:34:15 +0000, root wrote:

>> I don't want to see the intrusive elogind display that comes after
>> the login prompt but before I can log in. I tried chmoding -x the
>> entry in /etc/rc.d but that didn't kill the daemon.
>>
>> I know this is needed by Gnome, which I thought
>
> To quote the Gentoo wiki...
> "elogind is the systemd project's logind, extracted to a standalone
> package. It's designed for users who prefer a non-systemd init
> system, but still want to use popular software such as KDE/Wayland or
> GNOME that otherwise hard-depends on systemd."
>
> I think the key phrase here is "to use popular software such as
> KDE/Wayland ... that otherwise hard-depends on systemd."
>
> Apparently, if you want KDE, you must have elogind.

Also, if you want 'procps-ng' (and there's no other option) you want
'elogind' too.

# ldd ` whence ps `
linux-vdso.so.1 (0x00007ffc1fe93000)
libprocps.so.8 => /lib64/libprocps.so.8 (0x00007fdc00d12000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fdc00d0d000)
libc.so.6 => /lib64/libc.so.6 (0x00007fdc00b2e000)
libelogind.so.0 => /lib64/libelogind.so.0 (0x00007fdc00a84000)
/lib64/ld-linux-x86-64.so.2 (0x00007fdc00d5f000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007fdc00a79000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdc00a58000)

I don't run recommended Slackware (-current) thus I can't say what else
would be broken (besides installed), but 'iptables' and 'iproute2'
missing would bring in kinda havoc.

*CUT*

--
Torvalds' goal for Linux is very simple: World Domination
Stallman's goal for GNU is even simpler: Freedom