Re: PfInit Error

New Message Reply Date view Thread view Subject view Author view

Rob Jenkins (robj++at++quid)
Fri, 12 Sep 1997 08:45:03 -0700


The script Scott mentions was done by Don Hatch and is attached.

Cheers
Rob

-- 
________________________________________________________________
Rob Jenkins mailto:robj++at++sgi.com
Silicon Graphics, Mtn View, California, USA

#!/bin/sh

# # perf12xfs $Revision: 1.5 $ # # Script to patch a statically linked Performer1.2 application # to allow it to run when PFTMPDIR is an XFS file system # (getting rid of the bogus fatal "cannot create semaphore arena via NFS" # error). # # Run this script on the executable (but make a backup first!) # # So far, it has been tested on the following files: # ~src/trees/demo/GL/perfly/perfly # /usr/demos/Impact/data/GIS/terrain/perfly.ptu # /usr/demos/Impact/MaxImpact/SGI/site/perfly # /usr/demos/Impact/MaxImpact/SGI/realitycenter/perpath # If you have an executable for which it doesn't work, # please let me know (hatch++at++sgi.com). #

if [ $# -ne 1 ] then echo Usage: `basename $0` executablename >&2 exit 1 fi

perl -p -i.bak \ -e '$/ = 0777;' \ -e "s/pfInit: cannot create semaphore arena via NFS \(%s\). Change PFTMPDIR./pfInit: semaphore arena dir (%s) is not EFS. Use PFTMPDIR to change./;" \ -e "s/(\ \217\274\000\040\ \000\000\000\000\ \217\231..\ \047\244..\ \003\040\370\011\ \047\245..\ \217\274\000\040\ \047\244..\ \217\231..\ \044\005\000\057\ \003\040\370\011\ \000\000\000\000\ \217\274\000\040\ \020\100\000\002\ \047\244..\ \240\100\000\000\ \217\231..\ \047\245..\ \044\006\000\050\ \003\040\370\011\ \000\000\070\045\ \217\274\000\040\ \004\101\000\013\ \207\256..\ \217\206..\ \217\231..\ \044\004\000\001\ \044\005\000\003\ \047\247..\ \003\040\370\011\ \044\306..\ \217\274\000\040\ \000\000\000\000\ \207\256..\ \044\001\000\001\ \025\301\000\012\ \000\000\000\000\ \217\206..\ \217\231..\ \044\004\000)\001\ /"'$1'"\005/g;" \ -e "s/(\ \047\244..\ \003\040\370\011\ \044\245..\ \217\274\000\040\ \000\000\000\000\ \217\231..\ \047\244..\ \003\040\370\011\ \047\245..\ \217\274\000\040\ \047\244..\ \217\231..\ \044\005\000\057\ \003\040\370\011\ \000\000\000\000\ \217\274\000\040\ \020\100\000\002\ \047\244..\ \240\100\000\000\ \217\231..\ \047\245..\ \044\006\000\050\ \003\040\370\011\ \000\000\070\045\ \217\274\000\040\ \004\101\000\013\ \207\257..\ \217\206..\ \217\231..\ \044\004\000\001\ \044\005\000\003\ \047\247..\ \003\040\370\011\ \044\306..\ \217\274\000\040\ \000\000\000\000\ \207\257..\ \044\001\000\001\ \025\341\000\011\ \044\004\000)\001\ /"'$1'"\005/g;" \ $1 exit 0

======================================================================= List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/ Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:55:56 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.