Hi all,

I 've generated the jobname.exe.batch file within prostar. But when I try to start it with nohup jobname.exe.batch & nothing happens. I work with bash as standard shell.

Any idea what could be wrong??

Thanks

Remove the "timex" command in the batch file or replace it with "time".

I've tried this but it doesn't work. I use Suse 8.0 Linux with standard installation.

what happens if you leave prostar and run the starlink from the command line, i've nerver started a job from prostar

Inside the script does it say ./star-casen ... or just star-casen ... ?

If its the second then it is possible that you might need to add "." to your path or edit the script maybe? I can't look at a typical script right now since I'm at home.

Maybe there's a "y" missing in the fourth line in your startup-script? Star-CD asks if it should re-compute the wall-distances, but the batch-script does not account for it.

The shell script generated with prostar is shown in the following lines:

#!bin/sh timex ./job.exe > job.exe log 2>&1 <<EOD job EOD

The starlink command executed directly from a shell generates the same script.

So any idea why this script doesn't run the case job under Suse 8.0 with bash as standard shell???

Thanks

#!bin/sh

timex ./job.exe > job.exe log 2>&1 <<EOD

job

EOD

My startscript looks like this: note the "y" in line four.

#!/bin/sh time ./star-foo.exe > star-foo.exe.log 2>&1 <<EOD foo y EOD

Sorry but it is not possible to post the script. Some symbols can't not be displayed

The "timex" command does not exists in Linux. Thats why the script does not work. You just have to edit the script and remove the word "timex".

Another way would be to create a symbolically link or an alias.