Re: [WDSCI-L] RSE server on a Linux box

[David McKnight <dmcknigh@xxxxxxxxxx>]

Hi Jim,

In regards to 1), I'm pasting text from another note that I sent to someone
a little while back, describing how one should setup the deamon:


Here's some information on how to setup the daemon to run at startup on
Linux.  The information here comes courtesy of Don Yantzi who has set up a
couple linux daemons for our team.  There are three ways to set up a
service.  The first is the easiest, the second is a better way, and the
third...well, probably won't work at this time (so you might want to
disregard that for now).

1. Append Call to Daemon from startup script

The easiest way to do this is to add the call to daemon.linux to one of the
Linux startup scripts.  Add the following lines to the bottom of the
/etc/rc.d/rc.local file:

cd /opt/rseserver51
./daemon.linux &


2. Start Daemon via a new Runlevel script

The slightly harder but better (more correct) way is to create an entry
like the following in one of the /etc/rc.d/rc#.d directories (where #
refers the runlevel of the system, as the system boots up and goes through
the various run levels the scripts in the corresponding directory are run.
On one of our servers, we have a file called S22rseserver in /etc/rc5.d
that links to the file /etc/rc.d/rseserver (by convention you create links
from the rc#.d directories so it is easy to change which runlevel scripts
get called in.)  The file /etc/rc.d/rseserver contains:

#! /bin/sh
# Copyright (c) IBM Corporation 2003
#
#
# /etc/init.d/rseserver
#
### BEGIN INIT INFO
# Provides:
# Required-Start:
# Required-Stop:
# Default-Start:     3 5
# Default-Stop:
# Description:       Start the Remote System Explorer Daemon
### END INIT INFO

. /etc/rc.status
rc_reset

case "$1" in
    start)
        echo "Running RSEServer"
        cd /opt/rseserver
        /opt/rseserver/daemon.linux > /tmp/rseserver.log &
        rc_status -v
        ;;

    stop|restart|reload|status|probe)
        rc_failed 3
        ;;

    *)
        echo "Usage: $0 start"
        exit 1
        ;;
esac
rc_exit


3. Use the xinetd super-daemon
The third way (and probably the most correct) would be to run it using the
xinetd super-daemon. However we haven't tried this and it would probably
require some changes in our code to get it to work.


In regards to 2), the daemon works in the following way.  Whenever a user
requests a session via the daemon (on port 4035), it launches a RSE remote
server under requresting user's ID.  That server picks an available port to
listen to and passes that back to the daemon, which relays the information
back to the client.  Then, on the client, side an attempt to connect to the
server is made using the port that came back.  The user can choose the
server port by specifying it in the subsystem properties.  Then you'll need
to make sure the firewall allows that port out.


I hope this helps.

____________________________________
David McKnight
Phone:   905-413-3902 , T/L:  969-3902
Internet: dmcknigh@xxxxxxxxxx
Mail:       D1/643/8200/TOR
____________________________________



                                                                           
             JOberholtzer@comp                                             
             ures.com                                                      
             Sent by:                                                   To 
             wdsci-l-bounces@m         wdsci-l@xxxxxxxxxxxx                
             idrange.com                                                cc 
                                                                           
                                                                   Subject 
             05/02/2004 11:39          Re: [WDSCI-L] RSE server on a Linux 
             AM                        box                                 
                                                                           
                                                                           
             Please respond to                                             
                 Websphere                                                 
                Development                                                
             Studio Client for                                             
                  iSeries                                                  
                                                                           
                                                                           









Don,

Running the dos2unix and setting chmod at 755 allowed the server to start
running.

Point of interest, the Linux server is running remotely and has a VPN
connection to my office with limited ports open for SSH, VNC and now 4035.

Question 1) Since the JAVA is called with the "system" command, should it
not run the background?  My session stays active and I get start/stop
messages occasionally.  How would I make it run in the background?

Question 2)  My firewall opened up the port (4035 is the default) for
inbound traffic.  the Linux server shows messages like:

Daemon running on: Linux, port: 4035
launched new server on 38470
Server running on: Linux
finished on port 38470

when it starts, and a connection attempt is made, but the connection will
not finish and I get an error.  Do I have to open up additional ports other
than 4035?

Thanks for your help.  This is going to be real way cool if I get it
running.

Jim Oberholtzer

_______________________________________________
This is the Websphere Development Studio Client for iSeries  (WDSCI-L)
mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/wdsci-l.