rich@eddie.MIT.EDU (Richard Caloggero) (07/12/88)
Ok all you UUCP wizards, here's one for you! I know you're out
there ...
Until we obtain our ethernet software, we are using UUCP to do
file transfers between our Domain ring and our Alliant Fx8. Since
we are only communicating with one remote sise (actually, it ain't so
remote) and its our own machine, I have set things up a bit differently
than one might otherwise. Essentially, we only allow requests to be
initiated from the Apollo net, since we don't have enough resources to
dedicate an sio port on an Apollo. We define 2 operations: get_file
(get file(s) from Fx8), and send_file (Apollo -> Fx8). Both use the
uucp command to queue the specified set of files, then the program
creates a process on the Apollo node which contains the sio port used
to communicate with the Alliant, and starts uucico to do the transfer.
When uucico has successfuly started, {get,send}_file returns to the
shell. When uucico finishes, it uses write(1) to send a message to the
user who started it.
Now, the fun begins ... I want to be able to use uux to set up
remote command execution. The problem is, I can't seem to get the
command to start on the Alliant. I can set up the command with uux,
and uucico seems to send the correct files over to the Alliant, but
nothing happens on the Alliant, and I can't find the data which was
suposedly sent to the Alliant. I thought I found something when I
discovered that a core dump was being left in "/usr/spool/uucp/XTMP" on
the Alliant. I checked the permissions on this directory, and found
that world didn't have "w" rights. When I gave world "w" rights, the
core dump didn't happen, but then again, nothing else did either! Any
Idea as to what's gone wrong? ( I keep seeing references to a
directory called "/usr/spool/uucp/X.apolloX", but its not their on
either machine, and I can't seem to find anything in the manual that
would indicate a need for that directory. )
Thanx for your help. Please mail responses to me. I'll re-post a
summary if it seems appropriate.
--
-- Rich (rich@eddie.mit.edu).
The circle is open, but unbroken.
Merry meet, merry part,
and merry meet again.rich@mit-eddie.UUCP (07/13/88)
Ok all you UUCP wizards, here's one for you! I know you're out
there ...
Until we obtain our ethernet software, we are using UUCP to do
file transfers between our Domain ring and our Alliant Fx8. Since
we are only communicating with one remote sise (actually, it ain't so
remote) and its our own machine, I have set things up a bit differently
than one might otherwise. Essentially, we only allow requests to be
initiated from the Apollo net, since we don't have enough resources to
dedicate an sio port on an Apollo. We define 2 operations: get_file
(get file(s) from Fx8), and send_file (Apollo -> Fx8). Both use the
uucp command to queue the specified set of files, then the program
creates a process on the Apollo node which contains the sio port used
to communicate with the Alliant, and starts uucico to do the transfer.
When uucico has successfuly started, {get,send}_file returns to the
shell. When uucico finishes, it uses write(1) to send a message to the
user who started it.
Now, the fun begins ... I want to be able to use uux to set up
remote command execution. The problem is, I can't seem to get the
command to start on the Alliant. I can set up the command with uux,
and uucico seems to send the correct files over to the Alliant, but
nothing happens on the Alliant, and I can't find the data which was
suposedly sent to the Alliant. I thought I found something when I
discovered that a core dump was being left in "/usr/spool/uucp/XTMP" on
the Alliant. I checked the permissions on this directory, and found
that world didn't have "w" rights. When I gave world "w" rights, the
core dump didn't happen, but then again, nothing else did either! Any
Idea as to what's gone wrong? ( I keep seeing references to a
directory called "/usr/spool/uucp/X.apolloX", but its not their on
either machine, and I can't seem to find anything in the manual that
would indicate a need for that directory. )
-- -- -- -- -- -- -- -- -- --
Ok, this is realy frustrating! As far as I can tell, everything
is being set up properly for remote command execution, but nothing
hapens. Also, I keep getting "xqt denied" messages is "LOGFILE". I
checked "L.cmds", and the "who" command is definately in that file.
The command "uux 'sun!who >/users/rich/who.sun'" doesn't execute on sun
(the Fx8). Help!!!!!!!!!!
-- -- -- -- -- -- -- -- -- --
Thanx for your help. Please mail responses to me. I'll re-post a
summary if it seems appropriate.
--
-- Rich (rich@eddie.mit.edu).
The circle is open, but unbroken.
Merry meet, merry part,
and merry meet again.rroot@edm.UUCP (Stephen Samuel) (07/14/88)
From article <9661@eddie.MIT.EDU>, by rich@eddie.MIT.EDU (Richard Caloggero): > > Until we obtain our ethernet software, we are using UUCP to do > file transfers between our Domain ring and our Alliant Fx8. Since > > Now, the fun begins ... I want to be able to use uux to set up > remote command execution. The problem is, I can't seem to get the > command to start on the Alliant. I can set up the command with uux, One thing you have to do is allow the apollo to execute the commands from uux. In theory, this means you have to have an entry in your L.sys (or Permissions) file for each legal command. The other way around the problem would be to enable sh and csh. Your uux command would then be: uux apollo!csh '<' command.list.file Things get reall fun, though, if you want to use other files... You'd have to uucp (put) them over first. File space allocation (another article..) No: disk space is all global within a file system. If you have 4 file systems mounted as / , /usr , /usr/dept , and /mnt. removing a file from /mnt/a would make it's file space available anywhere in /mnt (but not, for ex. in /usr). Similarly: removing something in /usr/dept/x/y would make space avalable anywhere in /usr/dept/... , but NOT in /usr/lib (which is on the /usr filesystem). -- ------------- Stephen Samuel {ihnp4,ubc-vision,vax135}!alberta!edm!steve or userzxcv@uofamts.bitnet
mindel@netwrx1.UUCP (Joshua L Mindel) (06/16/90)
Initial part of question:
-------------------------
Does anyone have experience with setting up uucp (AT&T BNU) files on
AT&T 3B2s for a STREAMS-based network? In particular, for AT&T Enhanced
TCP/IP WIN/3B Release 3.0 over Ethernet and X.25.
Background:
-----------
I'd like to configure BNU files (on AT&T 3B2s with UNIX System V Release 3.2.2)
so that uucp and cu requests both go through login to connect over an Ethernet
and X.25 network.
Section 9.6 of the AT&T 3B2 Computer UNIX System V Release 3 Sys Admin guide
provides guidelines for setting up uucp on a STREAMS-based network. An example
procedure is included for uucp on the AT&T STARLAN network, with the qualifier
that a similar procedure could be applied for setting up uucp to run on a
transport provider that is compatible with the AT&T Transport Interface (TLI).
The WIN/3B TCP/IP Release 3.0 product is a transport provider compatible with
TLI.
After scouring the AT&T Sys Admin guide, WIN/3B docs, and talking with
Wollongong, I came to realize that there is one critical piece missing from
this picture; the STREAMS module(s) providing the interface between the TTY
server and TCP. Using AT&T's terminology for describing the software
components of a uucp-over-STARLAN configuration, these STREAMS modules are
called Remote Login Modules. For uucp over STARLAN, these STREAMS modules are
called LDO and NTTY.
Final part of question:
-----------------------
Do these remote login modules exist for TCP/IP? If yes, how and where can
I obtain them?
Further clarification of question:
----------------------------------
Leaning heavily on the definition used within the STARLAN environment, I presume
the precise function of these missing modules can be stated as follows:
The remote login modules are the software modules that act as an interface
between the TCP modules and the remote login services provided by the TTY
server. These modules provide the UNIX character processing and read/write
interface of the standard TTY driver. This allows existing UNIX TTY
services ("sh", "cu", etc.) to operate over the TCP/IP network.
Paper references for this note:
-------------------------------
WIN/3B TCP/IP Install/Admin Guide : pages 1-20 to 1-23
AT&T STARLAN User's Guide : pages 4-3 to 4-4
------------------------------
Thanks in advance.
--
-------------------------------------------------------------------------------
Joshua L Mindel, Senior Analyst Internet: mindel%netwrx1@uunet.uu.net
NetWorks One Usenet: uunet!netwrx1!mindel
Vienna, VA Phone: (703) 827-7767