| idl_lmgrd and Suse linux 9.1 [message #40647] |
Thu, 19 August 2004 12:38 |
Rick Towler
Messages: 821
Registered: August 1998
|
Senior Member |
|
|
It's upgrade time around here and that means the resident sysadmin has a
headache. It never goes as smooth as you would like...
We abandoned our windows/slowlaris combo and have switch to Suse linux
9.1 on x86. One of the services the old combo provided was serving IDL
licenses with lmgrd and out of the box, lmgrd doesn't run on Suse 9.1.
Here are a few tips to get it working (IDL version 6.0, web download tar
ball).
The first hurdle was installing *only* idl_lmgrd. Last time I checked
the only way to officially install the license manager was to install
IDL. Since the machine in question has no user shell accounts that
seemed rather wasteful. Luckily this turned out to be pretty easy.
First off, don't read the instructions, you'll ruin the fun. Untar the
IDL 6.0 package someplace convenient. The new directory, idl_6.0 in
this case, is laid out just like a normal $IDL_DIR.
Create directories where you wish to install the license server. In
order to keep it simple I chose the default IDL install dir
/usr/local/rsi. If you wish to put it someplace else you'll need to
modify the scripts (probably just sys5_idl_lmgrd?) but you're on your
own if you go that route.
# mkdir /usr/local/rsi /usr/local/rsi/idl_6.0 /usr/local/rsi/license \
/usr/local/rsi/idl_6.0/bin /usr/local/rsi/idl_6.0/bin/bin.linux.x86
Now return to where you untarred the IDL package and make your way to
the bin directory. Copy idl_lmgrd, the lm* files and sys5_idl_lmgrd to
your install bin directory:
# cp idl_lmgrd lm* sys5_idl_lmgrd /usr/local/rsi/idl_6.0/bin
Now cd to the bin.linux.x86 directory of your untarred IDL package and
copy the binary idl_lmgrd:
# cd bin.linux.x86
# cp idl_lmgrd /usr/local/rsi/idl_6.0/bin/bin.linux.x86
Point your web browser at:
http://www.macrovision.com/services/support/flexlm/lmgrd.sht ml#unixdownload
(or http://tinyurl.com/534sg)
and download the latest lmgrd and lmutil binaries. For Suse 9.1 I chose
the Suse 8 enterprise binaries. Uncompress and save these to
/usr/local/rsi/idl_6.0/bin/bin.linux.x86
cd to your the bin.linux.x86 install directory and either link or copy
lmutil to the other lm* files (*Except for lmgrd*, the other files,
lmdiag, lmhostid, etc are all the same lmutil binary. They are just
called by the lm* scripts with different switches)
# cp lmutil lmcksum
# cp lmutil lmdiag
# cp lmutil lmdown
# cp lmutil lmhostid
# cp lmutil lmremove
# cp lmutil lmstat
Now would be a good time to copy your license file to
/usr/local/rsi/license.
And you can delete the idl tar ball and the untarred idl package. there
is nothing else you will need from it.
Now cd to /usr/local/rsi/idl_6.0/bin and bring up sys5_idl_lmgrd in your
favorite editor. Edit the script definitions to suit your install. If
you followed the default IDL layout these should be o.k. except you may
want to send the logging to a file.
At this point if you were to save the script and try to start the
license manager you would get this error:
/usr/local/rsi/idl_6.0/bin/bin.linux.x86/idl_lmgrd: relocation error:
/usr/local/rsi/idl_6.0/bin/bin.linux.x86/idl_lmgrd: symbol errno,
version GLIBC_2.0 not defined in file libc.so.6 with link time reference
We have one more edit to make. Add the following two lines to the
startup script:
LD_ASSUME_KERNEL=2.4.1
export LD_ASSUME_KERNEL
Save your script. Copy it to /etc/init.d/idl_lmgrd and configure your
runlevels as you see fit. If you are using the Yast runlevel editor
you'll want to source /etc/rc.status up near the top and call rc_status
-v in your script after your start and stop the lmgrd daemon. Otherwise
the script doesn't return what Yast is expecting on exit and it will
hang when you try to start the script (this is just a Yast thing. If
you don't use Yast to configure this then don't worry about it).
Lastly, don't forget to configure your firewall. Default
lmgrd/idl_lmgrd ports are TCP 1700/1701. These can be changed in the
startup script and the license file respectively.
Another tidbit of information: As long as the MAC address doesn't
change, you can edit your server name in your license file as needed.
This is helpful when for instance your license server is on a network
using IP masquerading and its internal IP/name is different from its
external IP/name.
HTH,
-Rick
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
