[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: at command stopped working



On Tue, Aug 08, 2006 at 07:12:48AM +0200, Frank Blendinger wrote:
> On Mon, Aug 07, 2006 at 02:08:18PM -0400, Mike Polyakov wrote:
> > mike@myp:~
> > $ at 14:00
> > warning: commands will be executed using /bin/sh
> > at> gvim
> > at> <EOT>
> > job 21 at Mon Aug  7 14:00:00 2006
> 
> I guess gvim won't work, because it can't attach to your current X
> session - atd doesn't know about it. The commands launched by atd don't
> have the same environment as your regular shell user.

I just tried for myself - it is the $DISPLAY environment variable that
is not set for commands executed by atd. You can sort of solve this
problem by putting a "DISPLAY=<your-x-display-here> " before your
command at the at prompt, like this:

yogan@snowflake ~ > echo $DISPLAY
:0.0
yogan@snowflake ~ > at 0720
warning: commands will be executed using /bin/sh
at> DISPLAY=:0.0 gvim
at> <EOT>
job 125 at Tue Aug  8 07:20:00 2006

And huzzah - it works!


HTH,
Frank

-- 
Frank Blendinger | fb(at)intoxicatedmind.net | GPG: 0x0BF2FE7A
Fingerprint: BB64 F2B8 DFD8 BF90 0F2E 892B 72CF 7A41 0BF2 FE7A
   "Just because I don't care doesn't mean I don't undestand."
                                               (Homer Simpson)

Attachment: signature.asc
Description: Digital signature


Reply to: