-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mike Noyes wrote:
> On Thu, 2006-03-30 at 13:47, Charles Steinkuehler wrote:
>> A lockfile as used by your shell script is just a normal file in our SF
>>  project space, removable by anyone with rights to delete the file
>>  (should at least be any project admins, and could safely be any
>>  project developer, IMHO).  Normal *nix file permission rules apply,
>>  and no SF staff intervention is required if something goes wrong.
> 
> Ok. If I place the doc-build.sh script in our project shell space (say
> in /home/groups/l/le/leaf/admin/), where will the lockfile be created
> when run from cron? My home directory, or the location of the shell
> script (leaf/admin/)? From your description above, I gather it gets
> created in the shell script location unless otherwise specified.

The lockfile is the file you specify to the lockfile command.  If you
use an absolute path, that's the location.  Otherwise, it's relative to
the current working directory.  Since you're changing directories within
the script, you'll probably want to make sure you use an absolute path
when specifying the lockfile.

I'd put the lockfile in the same temporary directory you're using to
create the documentation.

- --
Charles Steinkuehler
[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFELHHGLywbqEHdNFwRAlrFAJ40Ruf5IIa1QorCD4oKO1IXokg2YwCfYcnl
23EsQeM1DlCM6I5CfIDPvbg=
=oiB8
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to