"Open" shell command not working in StartupItems

The "test_script" is build from Standard Tool project in Xcode.
This tool fork and the child process execl the shell script
"shell_script_test" below.

!/bin/sh

echo `date` >> /Users/alain/Desktop/file_test
open -e /Users/alain/Desktop/shell_script_test

When the tool "test_script" is called from the Terminal, "file_test"
is updated with the right date and TextEdit is launched (with the text of
"shell_script_test").

But when the tool "test_script" is called by the SystemStarter (in
/Library/StartupItems/test_script/test_script)
"file_test" is updated with the right date but TextEdit is never launched.

Building "test_script" as Fondation, CoreDervices or CoreFondation Tool
doesn't change anything.

The code for "test_script" is below.

Since it is the same tool, why TextEdit is launched from Terminal but not
from StartupItems ?
(the tool is called since "file_test" is updated)
Changing environment variables and/or files permission seem does not
change anything.

Any suggestion will be greatly appreciate...



#include <CoreFoundation/CoreFoundation.h>

#include <unistd.h>

void test();

static char script_name[] = "/Users/alain/Desktop/shell_script_test";

int main (int argc, const char * argv[])
{

test();

// CFShow(CFSTR("Hello, World!\n"));
return 0;
}

void test()
{
int err;
pid_t ret;

ret = fork();
switch (ret)
{
case -1:
break;
case 0:
// sleep(60);
err = execl(script_name, script_name, NULL);
break;
default:
break;
}
}

In article <abz-0812031014450001.DeleteThis@192.168.1.100>,
abz.DeleteThis@videotron.ca (Alain Birtz) wrote:

> The "test_script" is build from Standard Tool project in Xcode.
> This tool fork and the child process execl the shell script
> "shell_script_test" below.
>
> !/bin/sh
>
> echo `date` >> /Users/alain/Desktop/file_test
> open -e /Users/alain/Desktop/shell_script_test
>
> When the tool "test_script" is called from the Terminal, "file_test"
> is updated with the right date and TextEdit is launched (with the text of
> "shell_script_test").
>
> But when the tool "test_script" is called by the SystemStarter (in
> /Library/StartupItems/test_script/test_script)
> "file_test" is updated with the right date but TextEdit is never launched.
>
> Building "test_script" as Fondation, CoreDervices or CoreFondation Tool
> doesn't change anything.
>
> The code for "test_script" is below.
>
> Since it is the same tool, why TextEdit is launched from Terminal but not
> from StartupItems ?

Because "open" is designed to be the command-line equivalent of
double-clicking on something in the Finder. It cannot work unless a
user is logged in and running the Finder.

--
Tom "Tom" Harrington
Macaroni, Automated System Maintenance for Mac OS X.
Version 1.4: Best cleanup yet, gets files other tools miss.
See http://www.atomicbird.com/