Rush 102.42a9d and 103.x both work fine on Apple's latest release
of OSX; 10.9 "Mavericks".
Everything seems normal for Rush 102.42a9d, no caveats.
That's the best release to run on all Macs.
For Rush 103.x, all works fine as well.
The only odd thing in Rush 103 are some benign "performance note"
warning messages printed to stderr when any of the rush GUIs pop open:
2013-10-30 11:14:04.104 irush[1638:507] CoreText performance note: Client called CTFontCreateWithName() using name "Arial" and got font with PostScript name "ArialMT". For best performance, only use PostScript names when calling this API.
2013-10-30 11:14:04.181 irush[1638:507] CoreText performance note: Client called CTFontCreateWithName() using name "Courier New Bold" and got font with PostScript name "CourierNewPS-BoldMT". For best performance, only use PostScript names when calling this API.
[..about 10 lines of similar text..]
So irush, onrush, rushtop, rushadmin, and the submit scripts that present
GUI's using the 'input' program will do this.
It seems Maverick wants Cocoa apps to use PostScript names for fonts
instead of Apple's regular font names, as apparently they are 'more efficient'.
(Rush 103 uses the Cocoa API, which is why these messages appear only in 103,
and not Rush 102; the older Rush 102 releases uses the older Carbon interface,
which doesn't trigger these performance warnings).
This was noticed in 103.00, 103.01, 103.02 and 103.03.
A free update will be provided for 103.03 that fixes these benign messages;
watch this space for details.
Rush 102.42a9d doesn't need any changes; it works fine.
If you're running anything older than 102.42a9d on Macs, you
should at *least* upgrade to 102.42a9d; ever since Snow Leopard,
that release has been needed to work properly on macs.
NOTES ABOUT OSX 10.9 MAVERICKS
It is still recommended to edit the /etc/hostconfig file and add
HOSTNAME=your-hostname to ensure the machine's hostname is set on boot
This avoids the default behavior of getting weird hostnames like
"John-Smiths-Mac" and the ".local" suffix that triggers the undesirable
Rendezvous/Bonjour/zeroconf protocols which can introduce unreliable
network behavior, which you should avoid in favor of *static*
hostname/DNS and IP assignments for network stability during rendering.
IF YOU FIND PROBLEMS WITH RUSH 102.42a9d OR RUSH 103.XX..
If you encounter issues with Rush + Mavericks not listed above,
feel free to follow up to this thread, being sure to include
the Rush version number you're using in your post, and replication
details, error messages, etc.