Of course, but why bother when the correct solution is to just run the tool once each time an LXDE session is started.
On 27/03/11 01:57 AM, Dan Muresan wrote: >> Jonathan, the "no X session involved" part with cron is actually more >> correct than you might have guessed. Not only is cron launched before >> X-related environment variables are set, I think I remember reading that >> most cron implementations actually limit the environment passed to >> cronjobs for security reasons. > > You could always save the relevant variables ($DISPLAY, $XAUTHORITY, > $XDG_SESSION_COOKIE, $DBUS_SESSION_BUS_ADDRESS -- depends on what you > need) in a file at X session startup, and load that file from your > cronjob. Doesn't work if you might have multiple Xs running (then > again most window / desktop managers don't support that either). > > So that would not be an obstacle... > ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
