From: jance <powerjance@(email surpressed)>
Subject: lwsn on os x
   Date: Mon, 31 Oct 2005 19:34:56 -0800

Hello.  Us again.

Now we've got Lightwave mostly working with Rush, except for errors on 
the Mac.  We're not sure if this needs the equivalent of setting 
Environment Variables/System Paths for OSX?  Or how to do it if so.

Log is attached below.  We'll dig around, but if you have a clue for us, 
we'd be very grateful!

Thanks.

- Jance and Dennis





###
### forworkone.12: 0120
###
--------------- Rush 102.42a --------------
--      Host: forworkone
--       Pid: 6174
--     Title: lightwave_rush_test_4a
--     Jobid: forworkone.12
--     Frame: 0120
--     Tries: 0
--     Owner: dennisw (501/501)
-- RunningAs: dennisw (501/501)
--  Priority: 1
--      Nice: 10
--    Tmpdir: /var/tmp/.RUSH_TMP.312
--   LogFile: 
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws.log/0120
--   Command: perl //forworkone/jobs/rushscripts/submit-lightwave.pl 
-render //forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 
//forworkone/jobs/_lightwave/_config_pc //forworkone/jobs/_lightwave 0 
off 1 0 3 Fail
--   Started: Mon Oct 31 18:58:43 2005
------------------------------------------

      SCENEFILE: 
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws
      CONFIGDIR: //forworkone/jobs/_lightwave/_config_pc
     CONTENTDIR: //forworkone/jobs/_lightwave
    RENDERFLAGS: 
    BATCHFRAMES: 1 (120-120)
        RETRIES: 3 (Fail after 3 retries)
     MAXLOGSIZE: 0
           PATH: 
/usr/local/rush/bin:/usr/local/rush/bin:/usr/local/rush/bin:/usr/libexec:
/bin:/sbin:/usr/bin:/usr/sbin:/usr/libexec:/System/Library/CoreServices


Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc 
-d//forworkone/jobs/_lightwave  
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at 
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory

--- RETRY #2 of 3
[forworkone.12] 0120: retry#2 of 3

Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc 
-d//forworkone/jobs/_lightwave  
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at 
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory

--- RETRY #3 of 3
[forworkone.12] 0120: retry#3 of 3

Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc 
-d//forworkone/jobs/_lightwave  
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at 
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory
--- LWSN FAILED

Hi Jance,

L8r,

Luke

On 01/11/2005, at 2:34 PM, jance wrote:

[posted to rush.general]

Hello.  Us again.

Now we've got Lightwave mostly working with Rush, except for errors on
the Mac.  We're not sure if this needs the equivalent of setting
Environment Variables/System Paths for OSX?  Or how to do it if so.

Log is attached below. We'll dig around, but if you have a clue for us,

we'd be very grateful!

Thanks.

- Jance and Dennis





###
### forworkone.12: 0120
###
--------------- Rush 102.42a --------------
--      Host: forworkone
--       Pid: 6174
--     Title: lightwave_rush_test_4a
--     Jobid: forworkone.12
--     Frame: 0120
--     Tries: 0
--     Owner: dennisw (501/501)
-- RunningAs: dennisw (501/501)
--  Priority: 1
--      Nice: 10
--    Tmpdir: /var/tmp/.RUSH_TMP.312

-- LogFile: //forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws.log/0120 -- Command: perl //forworkone/jobs/rushscripts/submit-lightwave.pl -render //forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws

//forworkone/jobs/_lightwave/_config_pc //forworkone/jobs/_lightwave 0
off 1 0 3 Fail
--   Started: Mon Oct 31 18:58:43 2005
------------------------------------------

      SCENEFILE:
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws
      CONFIGDIR: //forworkone/jobs/_lightwave/_config_pc
     CONTENTDIR: //forworkone/jobs/_lightwave
    RENDERFLAGS:
    BATCHFRAMES: 1 (120-120)
        RETRIES: 3 (Fail after 3 retries)
     MAXLOGSIZE: 0
           PATH:

/usr/local/rush/bin:/usr/local/rush/bin:/usr/local/rush/bin:/usr/ libexec: /bin:/sbin:/usr/bin:/usr/sbin:/usr/libexec:/System/Library/ CoreServices

Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc
-d//forworkone/jobs/_lightwave
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory

--- RETRY #2 of 3
[forworkone.12] 0120: retry#2 of 3

Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc
-d//forworkone/jobs/_lightwave
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory

--- RETRY #3 of 3
[forworkone.12] 0120: retry#3 of 3

Executing: lwsn -3 -c//forworkone/jobs/_lightwave/_config_pc
-d//forworkone/jobs/_lightwave
//forworkone/jobs/_lightwave/scenes/balls_rush_test_04a.lws 120 120 1
Can't exec "lwsn": No such file or directory at
/jobs/rushscripts/.common.pl line 224.
--- lwsn: No such file or directory
--- LWSN FAILED

---
Luke Cole
Systems Administrator / TD

FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042

Luke Cole wrote:

Hi Jance,

We tried setting up Lightwave on OSX with rush a little while ago, but did not meet with success.

It would seem that the "lswn" executable is a Cocoa/Carbon only application that cannot be invoked from the BSD subsystem.

	Right -- if that's /still/ the case, that's a show stopper
	as Rush then can't control it for rendering.. it has to be
	a command line oriented tool.. by that, meaning:

             o The program can be invoked from the Terminal with options for the scene, frame range, etc
             o The program must not open a GUI at all
	      o The program must not background itself, and return an exit code on completion
	      o If the command line is killed (^C, SIGKILL, etc) all rendering should stop
             o All error messages during rendering go to stdout/error (no GUI dialogs)

	Probably first, refer to the [NewTek] folks for enlightenment, as
	we know they have this capability under Windows and Linux, IIRC.

	If they currently do not have a way to invoke the renderer from a command
	line or script similar to the Windows/DOS approach, then definitely appeal
	for this in a future release. Until then, there's really no way to realistically
	manage rendering from scripts using their current technique.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

jance wrote:

Can't exec "lwsn": No such file or directory at /jobs/rushscripts/.common.pl line 224.

	Sounds like the 'lwsn' executable is not in the path.

	If you know the path to the lwsn executable, eg. "/Applications/Lightwave/bin/lwsn",
	then add just the directory part of the pathname to the 'OSX' section at the top of the script:

elsif ( $G::ismac )
{
    # OSX
    $ENV{PATH} = "/Applications/Lightwave/bin:$ENV{PATH}";
}

	..so that it can find the path to the executable.

	This is, of course, assuming that Lightwave for MacOSX has a
	command line tool for rendering; I've never tested this.

	Try testing the 'lwsn' from the command line first.
	If you're unable to get 'lwsn' to work from the command line,
	check [NewTek's] docs regarding lwsn setup, or with [NewTek's]
	tech support regarding how to get lwsn to work from the OSX unix shell.


--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

About 5 months ago when I tried this I gave up after a day as I couldn't run
the lwsn binary from the shell. It appears to only be able to run as a GUI
app as Luke said, so I'm 99% sure you can't render OSX lightwave from
renders from rush. It's a huge oversight in my eyes, although I'm sure
Newtek have a good enough reason to force you into using their far inferior
render utility.

Jance if you find anything diference please let us know ;)

Dylan 

|-----Original Message-----
|From: Greg Ercolano [mailto:erco@(email surpressed)] 
|Sent: Tuesday, 1 November 2005 5:39 PM
|To: void@(email surpressed)
|Subject: Re: lwsn on osx
|
|[posted to rush.general]
|
|jance wrote:
|> Can't exec "lwsn": No such file or directory at 
|/jobs/rushscripts/.common.pl line 224.
|
|	Sounds like the 'lwsn' executable is not in the path.
|
|	If you know the path to the lwsn executable, eg. 
|"/Applications/Lightwave/bin/lwsn",
|	then add just the directory part of the pathname to the 
|'OSX' section at the top of the script:
|
|elsif ( $G::ismac )
|{
|     # OSX
|     $ENV{PATH} = "/Applications/Lightwave/bin:$ENV{PATH}";
|}
|
|	..so that it can find the path to the executable.
|
|	This is, of course, assuming that Lightwave for MacOSX has a
|	command line tool for rendering; I've never tested this.
|
|	Try testing the 'lwsn' from the command line first.
|	If you're unable to get 'lwsn' to work from the command line,
|	check [NewTek's] docs regarding lwsn setup, or with [NewTek's]
|	tech support regarding how to get lwsn to work from the 
|OSX unix shell.
|
|
|--
|Greg Ercolano, erco@(email surpressed)
|Rush Render Queue, http://seriss.com/rush/
|Tel: (Tel# suppressed)
|Cel: (Tel# suppressed)
|Fax: (Tel# suppressed)
|

Dylan Penhale wrote:

About 5 months ago when I tried this I gave up after a day as I couldn't run
the lwsn binary from the shell. It appears to only be able to run as a GUI..

	Right -- I do remember trying to help you with this, Dylan.

	When you tried invoking the LWSN executable from the command line,
	you got [paraphrasing your posting from April 2005]:

# cd '/Applications/LightWave [8]/programs'

# ./lwsn
./lwsn: cannot execute binary file

# ls -la
[..]
-rwxrwxrwx   1 root   admin   343461 21 Apr 16:44 LSid
-rwxrwxrwx   1 root   admin   599653 21 Apr 16:44 LWSN		<--
-rw-rw-rw-   1 root   admin        0 21 Apr 16:44 LWSN cmdLine
[..]

# file ./LWSN
./LWSN: header for PowerPC PEF executable

	So even though it was executable (rwx), it couldn't be invoked
	from the unix shell. (Macs aren't case sensitive, so ./lwsn == ./LWSN)
	
	FWIW, whenever a software vendor that already has a product working
	on OS9, or is new to OSX, they seem to take a few revs before they
	get their command line stuff working.

	It took a few revs of Maya on OSX before things work working smoothly.
	It wasn't until 6.0.1 that it was truly 'stable'.

Jance if you find anything diference please let us know ;)

	I think NewTek is still on version 8.x, and you and I tested
	with 8.2 I think it was. So my guess is this might still be
	an issue under OSX.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

In article <1080-rush decimal general at seriss decimal com>,
 Greg Ercolano <erco@(email surpressed)> wrote:

> 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA17HuFH028536
> 
> 	for <rush decimal general at seriss decimal com>; Mon, 31 Oct 2005 23:17:57 -0800
> Received: (qmail 30881 invoked from network); 1 Nov 2005 07:18:47 -0000
> Received: from unknown (HELO ?192.168.0.9?) (unknown)
> 
>   by unknown with SMTP; 1 Nov 2005 07:18:47 -0000
> X-pair-Authenticated: 24.205.66.40
> Organization: Seriss Inc.
> User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
> X-Accept-Language: en-us, en
> MIME-Version: 1.0
> To: rush decimal general at seriss decimal com
> In-Reply-To: <1078-rush decimal general at seriss decimal com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> Path: 3dsite.com
> Xref: 3dsite.com rush.general:1080
> NNTP-Posting-Host: localhost
> 
> Dylan Penhale wrote:
> > About 5 months ago when I tried this I gave up after a day as I couldn't run
> > the lwsn binary from the shell. It appears to only be able to run as a GUI..
> 
> 	Right -- I do remember trying to help you with this, Dylan.
> 
> 	When you tried invoking the LWSN executable from the command line,
> 	you got [paraphrasing your posting from April 2005]:
> 
> # cd '/Applications/LightWave [8]/programs'
> 
> # ./lwsn
> ./lwsn: cannot execute binary file
> 
> # ls -la
> [..]
> -rwxrwxrwx   1 root   admin   343461 21 Apr 16:44 LSid
> -rwxrwxrwx   1 root   admin   599653 21 Apr 16:44 LWSN		<--
> -rw-rw-rw-   1 root   admin        0 21 Apr 16:44 LWSN cmdLine
> [..]
> 
> # file ./LWSN
> ./LWSN: header for PowerPC PEF executable
> 
> 	So even though it was executable (rwx), it couldn't be invoked
> 	from the unix shell. (Macs aren't case sensitive, so ./lwsn == ./LWSN)
> 	
> 	FWIW, whenever a software vendor that already has a product working
> 	on OS9, or is new to OSX, they seem to take a few revs before they
> 	get their command line stuff working.
> 
> 	It took a few revs of Maya on OSX before things work working smoothly.
> 	It wasn't until 6.0.1 that it was truly 'stable'.
> 
> > Jance if you find anything diference please let us know ;)
> 
> 	I think NewTek is still on version 8.x, and you and I tested
> 	with 8.2 I think it was. So my guess is this might still be
> 	an issue under OSX.

Thanks for the info, guys.  Dennis is going to get on the phone with 
NewTek and see what's up.  If we learn anything, we'll let you know!

- Jance

In article <1081-rush decimal general at seriss decimal com>,
 jance <powerjance@(email surpressed)> wrote:

> In article <1080-rush decimal general at seriss decimal com>,
>  Greg Ercolano <erco@(email surpressed)> wrote:
> 
> > 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA17HuFH028536
> > 
> > 	for <rush decimal general at seriss decimal com>; Mon, 31 Oct 2005 23:17:57 -0800
> > Received: (qmail 30881 invoked from network); 1 Nov 2005 07:18:47 -0000
> > Received: from unknown (HELO ?192.168.0.9?) (unknown)
> > 
> >   by unknown with SMTP; 1 Nov 2005 07:18:47 -0000
> > X-pair-Authenticated: 24.205.66.40
> > Organization: Seriss Inc.
> > User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
> > X-Accept-Language: en-us, en
> > MIME-Version: 1.0
> > To: rush decimal general at seriss decimal com
> > In-Reply-To: <1078-rush decimal general at seriss decimal com>
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > Content-Transfer-Encoding: 7bit
> > Path: 3dsite.com
> > Xref: 3dsite.com rush.general:1080
> > NNTP-Posting-Host: localhost
> > 
> > Dylan Penhale wrote:
> > > About 5 months ago when I tried this I gave up after a day as I couldn't 
> > > run
> > > the lwsn binary from the shell. It appears to only be able to run as a 
> > > GUI..
> > 
> > 	Right -- I do remember trying to help you with this, Dylan.
> > 
> > 	When you tried invoking the LWSN executable from the command line,
> > 	you got [paraphrasing your posting from April 2005]:
> > 
> > # cd '/Applications/LightWave [8]/programs'
> > 
> > # ./lwsn
> > ./lwsn: cannot execute binary file
> > 
> > # ls -la
> > [..]
> > -rwxrwxrwx   1 root   admin   343461 21 Apr 16:44 LSid
> > -rwxrwxrwx   1 root   admin   599653 21 Apr 16:44 LWSN		<--
> > -rw-rw-rw-   1 root   admin        0 21 Apr 16:44 LWSN cmdLine
> > [..]
> > 
> > # file ./LWSN
> > ./LWSN: header for PowerPC PEF executable
> > 
> > 	So even though it was executable (rwx), it couldn't be invoked
> > 	from the unix shell. (Macs aren't case sensitive, so ./lwsn == ./LWSN)
> > 	
> > 	FWIW, whenever a software vendor that already has a product working
> > 	on OS9, or is new to OSX, they seem to take a few revs before they
> > 	get their command line stuff working.
> > 
> > 	It took a few revs of Maya on OSX before things work working smoothly.
> > 	It wasn't until 6.0.1 that it was truly 'stable'.
> > 
> > > Jance if you find anything diference please let us know ;)
> > 
> > 	I think NewTek is still on version 8.x, and you and I tested
> > 	with 8.2 I think it was. So my guess is this might still be
> > 	an issue under OSX.
> 
> Thanks for the info, guys.  Dennis is going to get on the phone with 
> NewTek and see what's up.  If we learn anything, we'll let you know!
> 
> - Jance

Well, NewTek support was of no use.  But we did figure out that you can 
go to an os x terminal and type this:  open "lwsn cmdline" and it seems 
to run lwsn.  We just need to figure out how to incorporate that 
correctly so the pc's keep working and the macs start working.

Any ideas?

- Jance

Hi Jance,

Well, NewTek support was of no use. But we did figure out that you can go to an os x terminal and type this: open "lwsn cmdline" and it seems

to run lwsn.  We just need to figure out how to incorporate that
correctly so the pc's keep working and the macs start working.

L8r,

---
Luke Cole
Systems Administrator / TD

FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042

In article <1083-rush decimal general at seriss decimal com>,
 Luke Cole <luke@(email surpressed).au> wrote:

> 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA1MgKFH005311
> 
> 	for <rush decimal general at seriss decimal com>; Tue, 1 Nov 2005 14:42:21 -0800
> Received: (qmail 30635 invoked by uid 0); 1 Nov 2005 23:31:18 -0000
> Received: from unknown (HELO stingray.fuel) (203.82.100.218)
> 
>   by mx1.vertel.net.au with SMTP; 1 Nov 2005 23:31:18 -0000
> Received: from [100.100.100.220] (manta.fuel [100.100.100.220])
> 
> 	by stingray.fuel (Postfix) with ESMTP id A39A08A46D3
> 
> 	for <rush decimal general at seriss decimal com>; Wed,  2 Nov 2005 09:43:20 +1100 (EST)
> Mime-Version: 1.0 (Apple Message framework v734)
> In-Reply-To: <1082-rush decimal general at seriss decimal com>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> Content-Transfer-Encoding: 7bit
> To: rush decimal general at seriss decimal com
> X-Mailer: Apple Mail (2.734)
> Path: 3dsite.com
> Xref: 3dsite.com rush.general:1083
> NNTP-Posting-Host: localhost
> 
> Hi Jance,
> 
> > Well, NewTek support was of no use.  But we did figure out that you  
> > can
> > go to an os x terminal and type this:  open "lwsn cmdline" and it  
> > seems
> > to run lwsn.  We just need to figure out how to incorporate that
> > correctly so the pc's keep working and the macs start working.
> 
> I too tried out the "open" thing - if I remember correctly, with it  
> you can get rush to launch lwsn, but after that you loose control of  
> the render, there is no simple way to detect whether the frame has  
> finished rendering, or if any errors occurred, etc.
> 
> L8r,
> 
> ---
> Luke Cole
> Systems Administrator / TD
> 
> FUEL International
> 65 King St., Newtown, Sydney NSW, Australia 2042

Do you remember if you did open "lwsn" or open "lwsn cmdline"? open lwsn 
opens an interface window asking for agruments and stuff.  We're hoping 
that open "lwsn cmdline" is something more useful, but we're not sure.

- Jance

In article <1084-rush decimal general at seriss decimal com>,
 jance <powerjance@(email surpressed)> wrote:

> In article <1083-rush decimal general at seriss decimal com>,
>  Luke Cole <luke@(email surpressed).au> wrote:
> 
> > 	by www.3dsite.com (8.12.8/8.12.8) with SMTP id jA1MgKFH005311
> > 
> > 	for <rush decimal general at seriss decimal com>; Tue, 1 Nov 2005 14:42:21 -0800
> > Received: (qmail 30635 invoked by uid 0); 1 Nov 2005 23:31:18 -0000
> > Received: from unknown (HELO stingray.fuel) (203.82.100.218)
> > 
> >   by mx1.vertel.net.au with SMTP; 1 Nov 2005 23:31:18 -0000
> > Received: from [100.100.100.220] (manta.fuel [100.100.100.220])
> > 
> > 	by stingray.fuel (Postfix) with ESMTP id A39A08A46D3
> > 
> > 	for <rush decimal general at seriss decimal com>; Wed,  2 Nov 2005 09:43:20 +1100 (EST)
> > Mime-Version: 1.0 (Apple Message framework v734)
> > In-Reply-To: <1082-rush decimal general at seriss decimal com>
> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> > Content-Transfer-Encoding: 7bit
> > To: rush decimal general at seriss decimal com
> > X-Mailer: Apple Mail (2.734)
> > Path: 3dsite.com
> > Xref: 3dsite.com rush.general:1083
> > NNTP-Posting-Host: localhost
> > 
> > Hi Jance,
> > 
> > > Well, NewTek support was of no use.  But we did figure out that you  
> > > can
> > > go to an os x terminal and type this:  open "lwsn cmdline" and it  
> > > seems
> > > to run lwsn.  We just need to figure out how to incorporate that
> > > correctly so the pc's keep working and the macs start working.
> > 
> > I too tried out the "open" thing - if I remember correctly, with it  
> > you can get rush to launch lwsn, but after that you loose control of  
> > the render, there is no simple way to detect whether the frame has  
> > finished rendering, or if any errors occurred, etc.
> > 
> > L8r,
> > 
> > ---
> > Luke Cole
> > Systems Administrator / TD
> > 
> > FUEL International
> > 65 King St., Newtown, Sydney NSW, Australia 2042
> 
> Do you remember if you did open "lwsn" or open "lwsn cmdline"? open lwsn 
> opens an interface window asking for agruments and stuff.  We're hoping 
> that open "lwsn cmdline" is something more useful, but we're not sure.
> 
> - Jance

And actually, it looks like open "lwsn cmdline" opens SimpleText.  Hmm.

Hi Jance,

And actually, it looks like open "lwsn cmdline" opens SimpleText. Hmm.

open -a /Applications/LWSN/LWSN

L8r,
---
Luke Cole
Systems Administrator / TD

FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042

open -a /Applications/LWSN/LWSN
open "lwsn cmdline"

	I dunno -- anything that involves using open(1) is probably not going
	to yield satisfaction; at best you'll be able to start the application,
	but control over the app will be lost.

	AFAIK, once open(1) is used to run an application, the shell and the app
	go their separate ways; the app 'forks off and away', becoming parented
	to the WindowServer.

	At that point the shell/rush will no longer have control over the process,
	and the process pretty much becomes managed by the window manager.

	Both reparenting and involving the window manager are two deal breakers;
	command line apps should do neither to be apps managable by shell scripts.

	In my experience, if an app can't be run from the command line unless
	open(1) is used, it's not really a command line app, and shouldn't be
	considered for use in shell scripts where controlled, serial execution
	of programs is needed.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

On 02/11/2005, at 10:58 AM, Greg Ercolano wrote:

[posted to rush.general]

open -a /Applications/LWSN/LWSN
open "lwsn cmdline"

I dunno -- anything that involves using open(1) is probably not going to yield satisfaction; at best you'll be able to start the application,

    but control over the app will be lost.

AFAIK, once open(1) is used to run an application, the shell and the app go their separate ways; the app 'forks off and away', becoming parented

    to the WindowServer.

At that point the shell/rush will no longer have control over the process,

    and the process pretty much becomes managed by the window manager.

Both reparenting and involving the window manager are two deal breakers; command line apps should do neither to be apps managable by shell scripts.

In my experience, if an app can't be run from the command line unless open(1) is used, it's not really a command line app, and shouldn't be considered for use in shell scripts where controlled, serial execution

    of programs is needed.

--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)

---
Luke Cole
Systems Administrator / TD

FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042

Do you remember if you did open "lwsn" or open "lwsn cmdline"? open lwsn opens an interface window asking for agruments and stuff. We're hoping

that open "lwsn cmdline" is something more useful, but we're not sure.

---
Luke Cole
Systems Administrator / TD

FUEL International
65 King St., Newtown, Sydney NSW, Australia 2042