Author: christop
Posted: 21 Nov 2012 09:06:56 pm (GMT -5)
cron has no idea what the "current" user session is (indeed, multiple sessions may be active simultaneously, or even no user session may be active at any given time), so it cannot open a terminal in an active user session. cron is not particularly useful for interactive tasks like the one you're trying to do.
_________________
Christopher Williams
Posted: 21 Nov 2012 09:06:56 pm (GMT -5)
cron has no idea what the "current" user session is (indeed, multiple sessions may be active simultaneously, or even no user session may be active at any given time), so it cannot open a terminal in an active user session. cron is not particularly useful for interactive tasks like the one you're trying to do.
_________________
Christopher Williams