home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.admin
- Path: sparky!uunet!spool.mu.edu!umn.edu!umeecs!nova!ellis
- From: ellis@nova.gmi.edu (Stew Ellis)
- Subject: Re: rlogin - how to pass data to
- Message-ID: <ellis.725899274@nova>
- Keywords: rlogin
- Sender: news@zip.eecs.umich.edu (Mr. News)
- Organization: GMI Engineering&Management Institute, Flint, MI
- References: <1992Dec31.233038.10090@uunet!fdls!agdept>
- Date: Fri, 1 Jan 1993 14:41:14 GMT
- Lines: 52
-
- walker@uunet!fdls!agdept (Walker) writes:
-
- >We are setting up a remote machine that will be limited to data base
- >applications. All users will login through a host and will operate from a
- >menu on the host. If the menu item selected is not data base related, such as
- >Word Processing, they will execute the application on the host. But, if
- >they select a data base application, such as SANITARIAN INSPECTION
- >SCHEDULING, then we want to have them do a transparent rlogin to the remote
- >machine
- >and execute the data base application. Since there will be several different
- >data base applications on the remote machine, data must somehow be passed to
- >the rlogin so a decision can be made about which data base application to
- >execute.
-
- >As far as I can tell, environmental variables on the host are not passed to
- >the remote machine during the rlogin process. So, I'm seeking advice from
- >the net on how to get data about which data base application to select
- >passed to the remote login.
-
- >Both the host machine and the remote machine are running Unix V, Release 3.
-
- >Thanks.
-
- > . . . Doug Walker
- >
- >--
- >-----------------------------------------------------------------------------
-
- >Doug Walker uunet!agdept!walker -or- walker@agdept.odag.or.gov
- >Oregon Department of Agriculture, Salem, Oregon (503) 378-5869
-
- I am a little unclear concerning your parameters. You could simply set up a
- series of "users" on the database machine, each of which would have a simple
- C or perl program or shell script as its "shell". This "shell" would then
- exec your database application with the proper arguments. It is important
- to exec so that when the user exits the DB they are not left with a login
- shell on the remote machine. The switch in your host menu would then have a
- series of statements of the sort:
- rlogin database.machine -l database.user
-
-
- There are a lot of issues that need to be clarified to tell whether this
- will work. There are also some security issues that need to be addressed.
-
- Hope this points in the right direction.
-
-
- --
- ___________________
- R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765 / _____ ______
- Humanities & Social Science, GMI Eng.& Mgmt. Inst. / / / / / /
- Flint, MI 48504 ellis@nova.gmi.edu /________/ / / / /
-