Re: custom, network install server
From: Rob (rob_at_nottobefoundhere.com)
Date: 11/25/05
- Previous message: Rob: "Re: OT HP Netserver Hardware Issue"
- In reply to: Brian K. White: "custom, network install server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Nov 2005 13:30:23 +0100
Brian K. White wrote:
> Has anyone ever managed to use the theoretical install from host to host
> over network in custom?
>
> The only docs I can find, all they say to do is, on the install serevr,
> (which must be a sco box of course) create a user named "swadmin" and assign
> it a password.
> Then, by other instructions it's implied that networking must basically be
> up between the two hosts. routable both ways, hostnames that resolve both
> ways and agree with each other etc..
> I have that. I have a new 506 box that needs lots of things an existing 506
> box already has.
> Both boxes have /etc/hosts and resolv.conf that cause all parties to agree
> on what the hostnames of the ips are.
> Both boxes are on a lan and no firewalls or nat translation going on between
> them.
> Both boxes even have .rhosts such that I can rlogin and rcp either way at
> will.
> Both boses are OSR 5.0.6
> Both boxes have rs506a
> Both boxes have the original stock ftp server
>
>
> On the old box, I did:
> useradd -m swadmin
> passwd swadmin
>
> On the new box I can ftp oldbox and log in as swadmin no problems
>
> On the new box, when I do that, it shows:
> # ftp unixa0
> Connected to unixa0.
> 220-
> 220 unixa0 FTP server (Version wu-2.6.1(1) Mon Feb 26 23:48:24 PST 2001)
> ready.
> Name (unixa0:root): swadmin
> 331 Password required for swadmin.
> Password:
> 230 User swadmin logged in.
> Remote system type is UNIX.
> Using binary mode to transfer files.
> ftp>
>
>
> however when I go into custom on the new box (note, rs506a has been
> installed so custom has been updated by that)
> and try the install from other host option, I can select the other host from
> the list, or I can type in the short hostname, or the full hostname, or the
> ip address, (they all work in general outside of custom)
> and the password (and the password has no strange characters in it, just to
> eliminate one more possible source of problems)
>
> I just get this:
>
> ------- Error Details ------
> Unable to connect to host "10.0.0.200"
> Error connecting to host "10.0.0.200"
> Host system is not running the required version of
> Error while executing command "HELP SITE EXEC"
> Error while sending request to ftpd
>
>
> And yet, manually I can do this from the new box:
> # ftp unixa0
> Connected to unixa0.
> 220-
> 220 unixa0 FTP server (Version wu-2.6.1(1) Mon Feb 26 23:48:24 PST 2001)
> ready.
> Name (unixa0:root): swadmin
> 331 Password required for swadmin.
> Password:
> 230 User swadmin logged in.
> Remote system type is UNIX.
> Using binary mode to transfer files.
> ftp> quot HELP SITE EXEC
> 214 Syntax: SITE EXEC <sp> command [ <sp> arguments ]
> ftp>
> ftp> quot SITE EXEC ls
> 200-ls
> 200 (end of 'ls')
> ftp> quit
> 221-You have transferred 0 bytes in 0 files.
> 221-Total traffic for this session was 483 bytes in 0 transfers.
> 221-Thank you for using the FTP service on unixa0.
> 221 Goodbye.
> #
>
> OK looks like it works just fine as far as I can see. What does custom
> want???
>
> Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
>
Hi Brian.
I don't have a couple of OS5 boxes to play with at the minute and as far
as I remember "scoadmin" is a collection of VTCL scripts which can be
modified/hacked by hand (supposing you know how to do that but I'm
pretty sure you do :-).
Since scoadmin is a rather large amount of VTCL works, I'd start by
identifying the script/module which takes care of the "install server"
setup/operations.
The /usr/lib/sysadm might be a good start.
Assuming the above module actually tries to perform an "help site exec"
operationg, try by locating the module by making use of the find utility
such as follows (I don't care about optimitations so I won't use xargs):
find . -type f -exec grep -i "site exec" {} \;
Once you're there, you can visually inspect the script to find out what
it's going to parse from the server as a result of the above operation.
Also, you should be able to debug VCTL scripts by adding the following
statements along the lines of the script itself:
mdtrace on [ open "/tmp/script.log" a+ ]
This is from http://wdb1.sco.com/kb/showta?taid=104921 .
Last, you can enable the debugging function of your FTP server as to
find out what the client is actually trying to perform; alternatively,
"tcpdump" (or another network sniffer) might be of help.
Best,
Rob
--
Roberto Zini - r.zini<@AT@>strhold.it
---------------------------------------------------------------------
"Has anybody around here seen an aircraft carrier?"
(Pete "Maverick" Mitchell - Top Gun)
- Previous message: Rob: "Re: OT HP Netserver Hardware Issue"
- In reply to: Brian K. White: "custom, network install server"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|