Re: at command stopped working
On 08.08.06 08:44, Mike Polyakov wrote: > I guess I missed the fact that 'at' still worked with non graphical > applications, and the above solution for X applications now works too! > I wonder why the DISPLAY is not set while 'at' executes, I thought it > inherited environment of the current shell. But I guess writing > DISPLAY=:0.0 is not too bad. Thank you for your help! the "at command" of course inherits variables from current shell. However it does not export all of them, so when the command is executed by "atd" daemon, commands will not get the DISPLAY variable. For executing X applications at given time, try different command. kalarm - KDE alarm message and command scheduler ktimer - KDE timer plan - X/Motif day planner (dynamically compiled with LessTif) wmtimer - A dockable alarm clock for WindowMaker -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I intend to live forever - so far so good. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: at command stopped working
[EMAIL PROTECTED] ~ > at 0720 warning: commands will be executed using /bin/sh at> DISPLAY=:0.0 gvim at> job 125 at Tue Aug 8 07:20:00 2006 I guess I missed the fact that 'at' still worked with non graphical applications, and the above solution for X applications now works too! I wonder why the DISPLAY is not set while 'at' executes, I thought it inherited environment of the current shell. But I guess writing DISPLAY=:0.0 is not too bad. Thank you for your help! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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: > > [EMAIL PROTECTED]:~ > > $ at 14:00 > > warning: commands will be executed using /bin/sh > > at> gvim > > at> > > 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= " before your command at the at prompt, like this: [EMAIL PROTECTED] ~ > echo $DISPLAY :0.0 [EMAIL PROTECTED] ~ > at 0720 warning: commands will be executed using /bin/sh at> DISPLAY=:0.0 gvim at> 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) signature.asc Description: Digital signature
Re: at command stopped working
On Mon, Aug 07, 2006 at 02:08:18PM -0400, Mike Polyakov wrote: > Yes, the job shows up when I run "atq". I also checked the syslog file > and it doesn't seem to contain anything relevant to "at" command. Here > is output from my shell: > > [EMAIL PROTECTED]:~ > $ date > Mon Aug 7 13:59:11 EDT 2006 > > [EMAIL PROTECTED]:~ > $ at 14:00 > warning: commands will be executed using /bin/sh > at> gvim > at> > 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. Try something like at> date > /tmp/at_test to see if atd is working. 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) signature.asc Description: Digital signature
Re: at command stopped working
Yes, the job shows up when I run "atq". I also checked the syslog file and it doesn't seem to contain anything relevant to "at" command. Here is output from my shell: [EMAIL PROTECTED]:~ $ date Mon Aug 7 13:59:11 EDT 2006 [EMAIL PROTECTED]:~ $ at 14:00 warning: commands will be executed using /bin/sh at> gvim at> job 21 at Mon Aug 7 14:00:00 2006 [EMAIL PROTECTED]:~ $ atq 21 Mon Aug 7 14:00:00 2006 a mike [EMAIL PROTECTED]:~ $ date Mon Aug 7 14:00:38 EDT 2006 [EMAIL PROTECTED]:~ $ atq [EMAIL PROTECTED]:/home/mike root# tail /var/log/syslog Aug 7 13:59:12 localhost kernel: parport0: FIFO is stuck Aug 7 13:59:12 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 13:59:22 localhost kernel: FIFO write timed out Aug 7 14:00:01 localhost /USR/SBIN/CRON[17397]: (root) CMD (test -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1) Aug 7 14:00:33 localhost kernel: parport0: FIFO is stuck Aug 7 14:00:33 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 14:00:43 localhost kernel: FIFO write timed out Aug 7 14:01:53 localhost kernel: parport0: FIFO is stuck Aug 7 14:01:53 localhost kernel: parport0: BUSY timeout (1) in compat_write_block_pio Aug 7 14:02:03 localhost kernel: FIFO write timed out Thanks. On 8/6/06, Florian Kulzer <[EMAIL PROTECTED]> wrote: On Fri, Aug 04, 2006 at 22:25:07 -0400, Mike Polyakov wrote: > Hi everyone, > My 'at' command stopped worked after kernel upgrade. Nothing seems to > be executing at the specified time. I tried to do it as root and still > no results. I checked that my atd daemon is running and that > /etc/at.deny does not contain users running 'at'. Does anybody know > why its not working? After you schedule a job, does it show up in the queue when you run "atq"? After a scheduled job fails to run, are there any error messages in /var/log/syslog? -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: at command stopped working
On Fri, Aug 04, 2006 at 22:25:07 -0400, Mike Polyakov wrote: > Hi everyone, > My 'at' command stopped worked after kernel upgrade. Nothing seems to > be executing at the specified time. I tried to do it as root and still > no results. I checked that my atd daemon is running and that > /etc/at.deny does not contain users running 'at'. Does anybody know > why its not working? After you schedule a job, does it show up in the queue when you run "atq"? After a scheduled job fails to run, are there any error messages in /var/log/syslog? -- Regards, Florian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: "at" command?
On Tue, Sep 12, 2000 at 01:55:37AM -0700, Krzys Majewski ([EMAIL PROTECTED]) wrote: > Where do I find the "at" command, or equivalent, which is like > a command-line crontab that says: execute such-and-such > command and such-and-such date and time. A search for "at", as > you can imagine, is not very helpful. -chris /usr/bin/at $ apt-get install at -- Karsten M. Self http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of "Gestalt" don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgpc35y21xSzy.pgp Description: PGP signature
Re: 'at' command/ Apology
First an apology. Some of us, at least myself, don't like to be confronted with our stupidity. Why I choose to advertize it, then, is another question. On Tue, 18 Feb 1997, Siggy Brentrup wrote: > I apologize if you took my citing of the man page as RTFM. Please attribute it > to my poor English. No, your reply was my first, and answered my question directly. Thank you. I have also recieved some very helpful, more lengthy responses. > > hmm does Red Hat have a mailing list or newsgroup? > > I think so, but why are you asking - some sort of (not so) subtle threat? > That doesn't look like good style either. > > -- Siggy Agreed. I regret saying it. It would be my loss. Mike. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 'at' command
On Tue, Feb 18 1997, Mike Miller wrote: > > Thanks to those that replied with a working answer. > bash$ at 10:30 > cdplay > C-d (I did at least know this much). > > I was disappointed by the flood of RTFM, however. I couldn't find an > example in the man pages, or Running Linux, or Unix in a Nutshell, where > the command actually did anything. Just something like > 'at now + 5 minute' > without anything below. I shouldn't be surprised, but I thought a debian > list would be different. I'll return to lurk mode. I apologize if you took my citing of the man page as RTFM. Please attribute it to my poor English. Both replies appearing on the list gave you working examples, pure RTFMs must have been in private email. I'd be embarrassed if any of those came from project members. > Mike. > > hmm does Red Hat have a mailing list or newsgroup? I think so, but why are you asking - some sort of (not so) subtle threat? That doesn't look like good style either. -- Siggy -- Siggy Brentrup <[EMAIL PROTECTED]> aka: [EMAIL PROTECTED] PGP fingerprint = C8 95 66 8C 75 7E 10 A2 05 61 C7 7F 05 B6 A4 DF -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 'at' command
Thanks to those that replied with a working answer. bash$ at 10:30 cdplay C-d (I did at least know this much). I was disappointed by the flood of RTFM, however. I couldn't find an example in the man pages, or Running Linux, or Unix in a Nutshell, where the command actually did anything. Just something like 'at now + 5 minute' without anything below. I shouldn't be surprised, but I thought a debian list would be different. I'll return to lurk mode. Mike. hmm does Red Hat have a mailing list or newsgroup? On Mon, 17 Feb 1997, Mike Miller wrote: > > I'm sure this is trivial, but can someone give me an example of an at > command that works? > I tried at 10:30 cdplay > It queued, and left the queue, but did not play. Thinking it was a path > problem, I tried > at 10:30 /usr/bin/cdplay > and got backat: incomplete time > Thanks, > Mike. > -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
Re: 'at' command
On Mon, 17 Feb 1997 10:22:54 MST Mike Miller ([EMAIL PROTECTED]) wrote: > I'm sure this is trivial, but can someone give me an example of an at > command that works? > > I tried at 10:30 cdplay > It queued, and left the queue, but did not play. Thinking it was a path > problem, I tried It should be: bash$ at 10:30 cdplay or: bash$ at 10:30 < sh-script Phil. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
