On Apr 30, 2010, at 2:19 PM, Drew Tomlinson wrote:
On 4/30/2010 10:11 AM, Allie Daneman wrote:
Read the man page...that should shed light on the issue.
Sent from my electronic slavery device.
[snip]
I've read the man page over and over.
Thanks for your reply.
I started there but guess
On 4/30/2010 10:11 AM, Allie Daneman wrote:
Read the man page...that should shed light on the issue.
Sent from my electronic slavery device.
[snip]
I've read the man page over and over.
Thanks for your reply.
I started there but guess I am dense. However Thomas' post told me that
I have
Read the man page...that should shed light on the issue.
Sent from my electronic slavery device.
On Apr 30, 2010, at 12:52, Drew Tomlinson
wrote:
I'm am unable to figure out the proper syntax of the 'at' command.
I've read the man page over and over. I've attempted Google
searches but
On Fri, Apr 30, 2010 at 09:52:26AM -0700, Drew Tomlinson wrote:
Hi Drew,
at reads its job from standard input, so basically you have to
$ echo '$yourcommand' | at noon
An alternative is to save you command in a small text file, and either
$ cat $file | at noon
or
$ at -f $file noon
Hope th
I'm am unable to figure out the proper syntax of the 'at' command. I've
read the man page over and over. I've attempted Google searches but
there is a lot of 'at' in the world. Can someone please point out
what's wrong with this syntax?
at noon '/usr/local/bin/curl -u user:pass -d status="
