On 1/27/09 12:04 PM, "Eric F Crist" <ecrist at secure-computing.net> wrote: > On Jan 27, 2009, at 1:21 PM, Dean Suhr wrote: > >> Greetings all, >> >> I¹m making my first dive into launchd. I want to schedule a script >> and am using Lingon <http://tuppis.com/lingon/> to help me a bit. >> The script has permissions of 777 for debug purposes. >> >> The terminal command that works is: >>> . /somedirectory/poll-blogs-script.sh (with a space between the >>> period and the first slash) >>> >> That command in Lingon/launchd gives me a ³posix_spawnp(³.², ...): >> Permission denied² error >> >> I am suspecting this is a basic syntax issue ... Can you help? > > Different subject, but have a look here: > > http://www.secure-computing.net/wiki/index.php/Leopard_Static_Routes > --- > Eric Crist > Thanks Eric ... But I am still stumped. What I noticed from the example you gave was ... 1) The shell script filename had no period or extension. I made that change to no avail. 2) I changed the first line of my script from #!/bin/shell to #!/bin/sh (I told you I was new at this!) 2) The example shell script was is /System/Library/StartupItems and was called by its "unpathed" name without a path. My script is in its own folder, somefolder, at the root level with 755 permissions. As a result I called the shell script by /somefolder/scriptname using the same syntax as the plist (no leading period). I still get the same permissions error as described above. Dean