[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    Re: kdebase/kdm/greeter
From:       Michael Matz <matz () ifh ! de>
Date:       2000-12-12 12:06:15
[Download RAW message or body]

Hi,

On Tue, 12 Dec 2000, Oswald Buddenhagen wrote:
> > Can't you link whoever is loading/unloading the chooser against the KDE/Qt 
> > libs? That way they will not get unloaded.
> > 
> the greeter is dynamically loaded.
> of course, i could link kdm against qt/kde, but this is exactly what i do
> NOT want to do - the kdm (or, better said, xdm) core should be unspecific
> to a certain greeter module - this was the idea behind dynamic greeters in
> the first place.
> 
> if nothing helps, i will make the greeter library non-kde, too, and
> let it simply fork off a separate process, which then in turn exec()s a
> stand-alone greeter application.  steffen hansen wanted to separate
> the greeter into an own process anyway (unpriviledged because of
> security reasons - whatever sort of ...), so this might be not the
> worst thing which could happen. but it will be a pain to implement, as
> the xdm core provides a lot of library functions to the greeter ...

All what you describe are exactly the reasons, why the greeter in KDM was
linked statically to it. Don't think we didn't try to seperate both, just
that it was too painfull and errorprone. You can get away with linking all
(kde)libs the greeter needs itself, also to the main binary. This way the
unloading of them is prevented, when unloading the greeter. Note, that
this doesn't mean, the main binary depends on kdelibs, it would still
function without them (if relinked). Even better it would be, if you
prevent the unloading of the greeter. That would solve most of your
problems. Note here too, that this wouldn't change _any_ behaviour in kdm.

The greeter in a process on it's own will not work easily with the more
special authentication mechanisms. Try to avoid that.


Ciao,
Michael.

[prev in list] [next in list] [prev in thread] [next in thread]