On Mon, 13 Jun 2016 10:14:08 +0200 Michaël Bouchaud <y...@efl.so> said:
> yes entrance_server only launch the session and don't wait it. But > entrance_server switch to entrance_wait to wait the session, and finaly > entrance_wait, when the session is closed, rerun entrance_server to clean > place and quit. > That's how entrance work and it's fine like this. To have a new session > systemd must relaunch entrance. > This is the only way how to do the job, because a login manager dunno it's > a reboot or just an end of session. that is true. it doesn't know. all it knows is session ended and it probably wants to start up again even while system is going down. this is why i think in future given wayland directions we probably want to merge entrance into e and bind them decently well. so entrance is really just an initial stage of enlightenment that handles some user auth then spawns the real e with the real uid etc. we want them tied cleanly - eg "entrance" starts and presents a login using drm/kmd engine like e does as compositor. it fades in and waits. when you have authed it fades out to black and e instantly takes over fading in from black. it should be "seamless" (if resolution etc. doesn't change, and even if it does this should be accounted for with a pause to wait for monitor resyncs). then when e logs out it fades to black, and entrance takes over knowing now if e said "please shut down/reboot" or not. if it did, entrance displays some shutdown screen integrating with systemd somehow knowing the state of shutdown, then exits when all is done. likely on boot maybe do a simplar thing. if it starts while booting somehow talk to systemd and get boot status... we likely also would have the entrance daemon bit do the shutdown/reboot - e just uses a specific error code to indicate this for example. > 2016-06-13 9:20 GMT+02:00 Carsten Haitzler <ras...@rasterman.com>: > > > On Sun, 15 May 2016 20:07:42 +0200 (CEST) Peter Koellner < > > pe...@asgalon.net> > > said: > > > > > Hi! > > > > > > I have played around with the entrance source, and hav emade some slight > > > progress. It looks like the entrance_server just went into idle main loop > > > after starting the user session, without ever showing the slightest > > interst > > > in when or if the user terminated the session later. This is why it > > > apparently had to be kicked out when shutting down and left a > > dysfunctional > > > display when simply logging out. I can't say that I have really solved > > the > > > underlying problem, because it would need some better understanding of > > the > > > ecore API. What I did was > > > - adding a signal handler for SIGCHLD after running entrance_session_run > > > forked the X session, which does a ecore_main_loop_quit() now > > > - adding a _logged=EINA_FALSE to entrance_session_shutdown, because the > > > entrance shutdown code got stuck there. > > > - added a -d parameter to change the path to executables so they are > > drawn > > > from the src directory instead of from installed PACKAGE_DIR for testing > > with > > > xephyr. > > > > > > The result is that now entrance quits immediately after session logout. > > > No idea if this solves too many problems there, but I have attached the > > git > > > diff output in case anyone is interested. > > > > ummm entrance shouldn't quit - it should loop and start up another login > > session > > without quitting... ? > > > > > > -- > > ------------- Codito, ergo sum - "I code, therefore I am" -------------- > > The Rasterman (Carsten Haitzler) ras...@rasterman.com > > > > > > > > ------------------------------------------------------------------------------ > > What NetFlow Analyzer can do for you? Monitors network bandwidth and > > traffic > > patterns at an interface-level. Reveals which users, apps, and protocols > > are > > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > > J-Flow, sFlow and other flows. Make informed decisions using capacity > > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > _______________________________________________ > > enlightenment-users mailing list > > enlightenment-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > > > > > > -- > Michaël Bouchaud (yoz) <y...@efl.so> > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
