From LightWiki

The following was posted by NewTek forum member "John the Geek" who has graciously permitted me to reproduce it here.

The LWSN application is now just called ScreamerNet, probably for the better, but it's taken me some getting used to.

Before, in PPC ScreamerNet, you would invoke the ScreamerNet process by launching it and the app would get its command line flags from the text file accompanying it. Now that ScreamerNet is a true command line process, you will need to send those flags at the time you invoke it, similar to how you would in the Windows version. However, in Windows, you could make a shortcut and add your flags to the path there. In Mac OS X you can pass them to ScreamerNet easily with a simple AppleScript.

Here is an example command to launch a ScreamerNet node:

/Applications/LightWave3D\ 9/ScreamerNet -2 -c/Volumes/LightWave/Configs/Quad -d/Volumes/LightWave/Content /Volumes/LightWave/Commands/job1 /Volumes/LightWave/Commands/ack1

Note: there is a \ before the space after LightWave3D. In the command line you must always warn the system when a space is not separating two commands, but instead is just part of the folder name as it is here.

• Type of Render: Just like before, you used either a -2 or -3 switch to tell ScreamerNet which render mode you were going to use. I usually use -2 myself, so that's what I'll demo for you today.
• Config Directory Location: You need to tell ScreamerNet where your Config files are located with the -c flag, immediately followed by the path to them. Mine looks like this: -c/Volumes/LightWave/Configs/Quad
  As you can see here in my example, on my LightWave volume, in my Configs folder, you can see I have a folder just for Quad-threaded renders. I also have folders for Dual-threaded, and in the odd case I get a Mactopus Pro to play with, an 8-threaded config folder. =) I can set them accordingly when I launch the node.

• Content Directory for the Scene: You use the -d flag to tell Screamernet where your Content directory is located, again immediately followed by the path to that folder. Mine looks like this: -d/Volumes/LightWave/Content
  Just as before, I placed my content folder on my LightWave volume.

• Commands and Responses: Here you tell Screamernet where to get it's orders and where to report back to when it's done. This is accomplished with the job and ack files, both with their full paths. Mine both look like this for node 1: /Volumes/LightWave/Commands/job1 and /Volumes/LightWave/Commands/ack1
  I have a folder on my LightWave volume called Commands and that is where all of my nodes sent their correspondence while rendering. In case you hadn't figured it out, my LightWave volume is a shared network volume accessible on all Screamernet nodes.

However, you don't have to type that every time you want to run ScreamerNet, you could just write an AppleScript, then save it as an application so you can just double-click it, and then it's easy going from there on out. My AppleScript looks like this:

tell application "Terminal"¶
do script "/Applications/LightWave3D\\ 9/ScreamerNet -2 -c/Volumes/LightWave/Configs/Quad -d/Volumes/LightWave/Content /Volumes/LightWave/Commands/job1 /Volumes/LightWave/Commands/ack1"¶
end tell¶

Another note: You must escape the space twice in AppleScript, once for AppleScript, and once for the command line.

And that little script launches ScreamerNet UB clocked in as node #1 on your ScreamerNet network.