BUG: StartupItems not working on Tiger

[jlevitsk@…]

I built Anacron with a target of pkg. I installed the pkg on a machine running 10.4 and then also on a machine running a seed of 10.4.1. On bootup on either system I see "An item in the Startup Items folder ("/Library/StartupItems/Anacron") does not have the proper security settings." There is an option to Fix but it doesn't change any permissions.. I believe this is because a symbolic link is actually what is in / Library/StartupItems and perhaps Apple didn't consider this.. or perhaps they did and this is a security issue.

This happened with anacron but it seems there is a standard startup item script that every port uses? I'm new to this but that's what I think so I would guess this would happen with any port that makes a startup item. I will also file a bug on the Apple side of the house and see if perhaps this is not how it should be working.

[jlevitsk@…]

postflight fix for Tiger to show issue

[jlevitsk@…]

I ran "sudo SystemStarter -v start Anacron" and I got an error...

Checking disks lockfile: Sorry, giving up on "/var/run/NFS.StartupItem"

So I removed the NFS requirement in the StartupParameters.plist and it seemed to elminate the errors.

[jlevitsk@…]

Next you have to add ANACRON=-YES- to /etc/hostconfig and you run in to the next problem.

/opt/local/etc/anacrontab: No such file or directory

[jlevitsk@…]

Once I copied the anacrontab-dist to anacrontab and ran SystemStarter again it seems Anacron is working under Tiger.

[jmpp@…]

Assigning bug to maintainer of port. Also adding James Berry to the Cc list as he's been working on startup itemes support for dp lately, he might be interested in this discussion.

-jmpp

[jberry@…]

I can confirm (both from testing and from looking at the SystemStarter source) that SystemStarter in Tiger requires now requires that the StartupItem is not a symlink. Each directory (and each file within the directory) must be a directory/regular file.

We should probably alter the startupitem behavior to generate the files in /Library/StartupItems, rather than simply symlinking from there. Ironcially, launchd doesn't seem to have the same restriction (yet) though it may in the future ;)

[jberry@…]

I've fixed this bug in cvs HEAD. Two changes are relevent:

(1) Create plist and script as root:wheel (2) Create entire startup item directory in /Library/StartupItems (if we just symlink to a copy of the directory then systemstarter still complains about security issues).

This fix has been checked in, but the bug will remain open until the fix has been migrated to the release branch, probably in conjunction with launchd support.