at on 10.4.11, 10.5.2 client and 10.5.2 server

At is not working.  On 10.4.11, the jobs get queued correctly, but do
not get executed or removed.  On both versions of 10.5.2 they get queued
with weird, seemingly random, dates and the sequence numbers are all the
same at over 600000.  Has anybody else seen this?  Is there a solution I
am missing?

--
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]

Robert Peirce wrote:
> At is not working.  On 10.4.11, the jobs get queued correctly, but do
> not get executed or removed.  On both versions of 10.5.2 they get queued
> with weird, seemingly random, dates and the sequence numbers are all the
> same at over 600000.  Has anybody else seen this?  Is there a solution I
> am missing?
>
at, cron have been deprecated since Tiger and superseded completely by
launchd in Leopard.  Some at and cron functionality is simulated by one
or more launchd items.

Good reference:
<[url]http://www.macgery.com/tips/ all_about_launchd_items_and_how_to_make_
one_yourse
lf[/url]>

There might be a bug in there somewhere, but you will be better off
learning to use launchd.
--
clvrmnky <mailto:spamtrap@clevermonkey.org>

Direct replies to this address will be blacklisted.  Replace "spamtrap"
with my name to contact me directly.

In article <fsu9o1$njv$1@aioe.org>,
Clever Monkey <spamtrap@clevermonkey.org.INVALID> wrote:

> Robert Peirce wrote: 
> at, cron have been deprecated since Tiger and superseded completely by
> launchd in Leopard.  Some at and cron functionality is simulated by one
> or more launchd items.
>
> Good reference:
> <[url]http://www.macgery.com/tips/ all_about_launchd_items_and_how_to_make_
one_yo[/
url]
> urself>
>
> There might be a bug in there somewhere, but you will be better off
> learning to use launchd.

I am not talking about com.apple.atrun.plist, or at least I don't think
I am.  However, I note that Disabled is Yes.  I am going to try changing
it to No.  Hmm.  I can't do that as me.  I guess this may be one case
where I have to log on as root, or maybe I should not touch it at all.
We'll see.

--
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]

I RTFM for at but somehow missed that it doesn't run unless you start
it!!  I started it in 10.4.11 per the instructions in the man page,
rebooted just to be safe and gave it a try and it worked.

Now I have to try the same in 10.5.2.

Sorry to have troubled everybody.

--
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]

In article <bob-85EAA1.20175101042008@[199.45.49.11]>,
Robert Peirce <bob@peirce-family.com.invalid> wrote:

> I RTFM for at but somehow missed that it doesn't run unless you start
> it!!  I started it in 10.4.11 per the instructions in the man page,
> rebooted just to be safe and gave it a try and it worked.
>
> Now I have to try the same in 10.5.2.

Well, that didn't work.  The at program, run twice for the same time,
2025 (8:25PM), produced the following at queue:

688128 Mon Dec 12 01:18:00 2033
688128 Sun Sep 29 15:05:44 1929

This is pretty much what it was doing before and about the same (maybe
identical) as what was happening on 10.5.2 server.

I also notice that the man page for at on 10.5.2 did not mention the
need to turn at on, which may be why I missed it the first time.
Nevertheless, I still did the load -w and checked service --list to make
sure it was running.

If I had to guess, I would say atrun may be working okay, but at isn't.
I now have at running on 10.4.11.  What do I need to do to get it to run
correctly on 10.5.2?

The command I entered was:

at 2025
mailx -s AtTest rbp
^D

This worked on 10.4.11 and failed on 10.5.2 client.

--
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]

Robert Peirce wrote:
> In article <fsu9o1$njv$1@aioe.org>,
>  Clever Monkey <spamtrap@clevermonkey.org.INVALID> wrote:
> 
>
> I am not talking about com.apple.atrun.plist, or at least I don't think
> I am.  However, I note that Disabled is Yes.  I am going to try changing
> it to No.  Hmm.  I can't do that as me.  I guess this may be one case
> where I have to log on as root, or maybe I should not touch it at all.
> We'll see.
>
*shrug*  My understanding is that traditional "at" is no longer
supported, and that a launchd process simulates it from now on.
--
clvrmnky <mailto:spamtrap@clevermonkey.org>

Direct replies to this address will be blacklisted.  Replace "spamtrap"
with my name to contact me directly.

In article <ft0ddd$qe0$1@aioe.org>,
Clever Monkey <spamtrap@clevermonkey.org.INVALID> wrote:

> *shrug*  My understanding is that traditional "at" is no longer
> supported, and that a launchd process simulates it from now on.

Here's the deal.  There is a LaunchDaemon called com.apple.atrun.plist.
It is delivered disabled.  The man page for 10.4.11 tells you how to
turn it on.  The man page for 10.5.2 does not.  However, it is simple

cd /System/Library/LaunchDaemons
launchctl load -w com.apple.atrun.plist

Here's the problem.  At on 10.4.11 works; at on 10.5.2 is broken. Atq
and atrm work properly.  However, 10.4.11's at can be installed on
10.5.2 and does work.  That's what I did.  Now I have at working on all
my machines.

I figured this out at the office so I had my consultant file a bug
report with Apple on 10.5.2's at.  I am surprised they let this get out.
The only thing I can figure is that with at disabled, nobody bothered to
check it.  For that reason it may never be fixed.  I don't know what
Apple does with this kind of stuff.

--
Robert B. Peirce, Venetia, PA  724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]