On Sun, Sep 1, 2013 at 2:28 PM, James May <[email protected]> wrote: > On 1 September 2013 01:16, Mantas Mikulėnas <[email protected]> wrote: >> >> On Sat, Aug 31, 2013 at 4:35 PM, Jan Engelhardt <[email protected]> wrote: >> > >> > On Saturday 2013-08-31 14:28, killermoehre wrote: >> >>Doesn't Amarok starts if you prefix it with the right DISPLAY variable? >> >>Like »DISPLAY=:0 amarok«. This should work from cron, too. >> > >> > Normally, you also need to set XAUTHORITY= to the right path -- >> > since you do not want just anybody to be able to connect to your :0. >> >> And then there are sessions /not/ on :0. Like when the display >> manager's login screen is on :0 (although this mostly happens in weird >> situations like startx'ing when a DM is running), or when Xorg crashes >> and doesn't delete the lockfile for :0 so the next session gets :1, or >> – what heresy – when there's a second user logged in, with /their/ >> session on :0. >> >> ...sometimes I think Xorg should start at :1 instead, and reserve :0 >> for annoying cronjobs and services that have DISPLAY=":0" hardcoded, >> to remind everyone that they're using a multi-user OS. >>[..] > > Welcome to Windows circa 2006 ;P > > http://blogs.msdn.com/b/oldnewthing/archive/2007/05/08/2470754.aspx
Exactly my point. -- Mantas Mikulėnas <[email protected]> _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
