Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  System / Utilities  |  OS Updates  |  Apple Security Update  |  so far, so good!

Apple Security Update

Apple Security Update

for PPC OS X 10.4.11

Version:  2008-008

   [ Views: 905 ]

so far, so good!

Feedback Type:  Review

Contributed by: jirene Tuesday, January 25 2005 @ 06:48 PM PST

Product Platform: MacOSX

Used Product For: Less than a month

Recommend Product: YES

Downloaded via SU, install went smoothly. Ran repair permissions after install, & along with usual notes, the following which I have not seen before & have no idea what it means:
We are using a special uid for the file or directory ./private/var/at/jobs. New uid is 1
We are using a special uid for the file or directory ./private/var/at/spool. New uid is 1
Any suggestions?   

2 of 3 users found this helpful.

Rate this Review

Was this Review helpful? Yes | No

Comments

3 comments |

so far, so good! - mnb

I've seen similar log messages for other files/directories during a permissions check/repair. I'll bet a change to 'at' was made. It's a unix utility that allows you to specify when a command is run. Sort of like cron, but cron is for a repeating cycle.

Reply to This

Tuesday, January 25 2005 @ 07:09 PM PST


so far, so good! - MacJuanC

at is the user version of "cron": a Unix utility that helps you schedule tasks to be carried out automatically by the system in your stead sometime in the future. Cron needs special privileges to run and you have to modify the crontab file to set things up, whereas "at" is configured with the command-line.

Regarding the change of the /private/var/at/jobs/ directory ownership, what Apple apparently did is make it belong to the "daemon" service account, instead of root (the privileged superuser account). This is clearly a security issue so a sneaky regular user cannot use the "at" command to gain superuser privileges. Not a big deal if you're the only person to use your portable, but an issue on public or multiuser machines.

Reply to This

Wednesday, January 26 2005 @ 12:12 AM PST


so far, so good! - brandonedling

Isn't at disabled by default? According to the man pages:

at, batch, atq, atrm are all disabled by default on Mac OS X. Each of
these commands depend on the execution of atrun(8) which has been dis-
abled due to power management concerns. Those who would like to use
these commands, must first re-enable /usr/libexec/atrun by removing the
leading '#' from the line.

Reply to This

Wednesday, January 26 2005 @ 05:14 AM PST