On 08/31/2015 09:44 AM, Michele Calgaro wrote:
> Ran from /etc/init.d/tdm-trinity

Michele,

   Would you be so kind as to post how tde is launched from tdm-trinity? If 
you are still using init scripts, then you will probably find in lines 7-10 
you are calling tdm directly:

      7     start)
      8        #Check for running tdm, start when not running
      9        stat_busy "Starting TDE Desktop Manager (tdm)"
     10        [ -z "$PID" ] && /opt/trinity/bin/tdm &> /dev/null

   Different distros handle init scrip wrappers with systemd in different 
ways. I've looked at the debian wiki and can't tell how they are doing it. 
This is where the session management issue comes up. In a pure-systemd 
environment, there are no init scripts -- period. For example, on arch:

13:44 valkyrie:~> ls -al /etc/init.d
ls: cannot access /etc/init.d: No such file or directory

   systemd handles all processes directly through a service file. I would 
wager that debian has an additional layer between tdm and systemd that 
provides what ConsoleKit did in the past. Can you check to see how debian 
handles init-script/systemd integration.


-- 
David C. Rankin, J.D.,P.E.