On Sun, 23 Jan 2005 14:27:38 +0100 Sebastian Dransfeld <[EMAIL PROTECTED]>
babbled:
> Hi!
>
> Two things:
>
> 1. Why isn't ecore_x_shutdown() and ecore_shutdown() called in
> entrance_session.c before the exec's?
i think that was because that closes the x display. if x gets its display closed
it will reset. we need to keep the connection open until the users clients
connect. :)
> 2. I sent at patch a while ago to fix the pam_close_session() problem. I
> have since checked quickly through the modules included with pam, and it
> seems no core module is erronous coded. Therefore I think that my patch
> still is a better way to do it than to simply ignore the error. If it
> leads to problems, maybe people will fix their pam modules!
atmos? xcomp? what do u guys think?
> From the pam guide:
> "It should be possible for sessions to be opened by one application and
> closed by another. This either requires that the module uses only
> information obtained from pam_get_item(), or that information regarding
> the session is stored in some way by the operating system (in a file for
> example)."
>
> Regards
> Sebastian
--
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler) [EMAIL PROTECTED]
裸好多 [EMAIL PROTECTED]
Tokyo, Japan (東京 日本)
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
