glowell@portia.Stanford.EDU (gary lowell) (09/27/90)
Greetings -
We received our first RS 6000 a week ago. I've managed to configure
most things the way that I want, but some things still elude me. Our
local IBM support has been cheerfully ineffectual. Maybe someone with
more experience with AIX can comment. We have the July updates
installed.
1. Configuring serial ports.
I am trying to set up a port for logins and UUCP. The modem is a
TB+ with the interface locked at 19200 and rts/cts flow control.
I can cu out ok. But dialing in, only 1 in three times do I get
a login herald. The other two times it disconnects immediatly,
or displays garbage and hangs. I should like the port to always
answer at 19200. Info explorer implies I should be looking at
/etc/ports but dosn't tell me anything about /etc/ports.
For login I enable the port with pdelay, which says that a herald
should not display until a character is received. It dosn't wait.
For bi-directional use, info explorer seems to indicate that pshare
or pdelay will do the right thing, but I have to disable the port to
dial out, and I have to be superuser or change the mode of the
port to successfully dial out. Wasn't all this supposed to be fixed
with the july updates ?
2. User Logins.
I've set up a number of user logins that seem to work fine logging
in at the console. If I try to log in over a serial line, if the
ID does not have a password I can login fine, if the ID has a
password I get an incorrect login message right away, it never
prompts for the password. I set terminals to ALL when I set them
up. Is there another security feature that I've overlooked ?
3. Escape in csh and ksh
I'm probably missing something very obvious here, but how do I enable
escape for file name completion in csh, and command mode in ksh. At
the moment Escape is treated as an ordinary character. This is at
the HFT without windows, or in aixterm when windows is running.
The profiles are the shipped defaults.
Any help would be greatly appreciated. I would be happy to compile
a trouble shooting guide for AIX if people would send me their favorite
tips and techniques. Such a guide has been floating around the HP-UX
community and I've found it very helpful in the past.
Thanks,
Gary Lowell
Allegro Consultants, Inc.
ron@woan (Ronald S. Woan) (10/01/90)
In article <1990Sep27.030149.13622@portia.Stanford.EDU>, glowell@portia.Stanford.EDU (gary lowell) writes: Gary> 3. Escape in csh and ksh Gary> I'm probably missing something very obvious here, but how do Gary> I enable escape for file name completion in csh, and command Gary> mode in ksh. At the moment Escape is treated as an ordinary Gary> character. This is at the HFT without windows, or in Gary> aixterm when windows is running. The profiles are the Gary> shipped defaults. I am not sure for csh, but for ksh, you need to have a "set -o gmacs" or "set -o vi" to get completion and editing stuff to work, if I remember correctly (I may not since it has always worked for me). You may also want to pick up tcsh from tesla.ee.cornell.edu, as it supports the terminal cursor keys and such, along with the spelling/completion stuff that has always made it popular, especially with novices... Gary> Any help would be greatly appreciated. I would be happy to Gary> compile a trouble shooting guide for AIX if people would send me Gary> their favorite tips and techniques. Such a guide has been Gary> floating around the HP-UX community and I've found it very Gary> helpful in the past. Or perhaps, we should have a bi-weekly Frequently Asked Questions posting with the some of the answers that we have come up with over the past few months, i.e. 1. Make sure that root doesn't belong in too many groups when using NFS across non AIX 3.1 (NFS 4.0 or whatnot) machines. 2. Where to find the BSD porting/administration documents. 3. Where to find patches and how to compile kermit, elm, GNU EMACS, etc... 4. How much and how to get X11R4 running. 5. X.desktop mailing list info. 6. Known bugs and workarounds..... . . + Ronald S. Woan (IBM VNET)WOAN AT AUSTIN, (AUSTIN)ron@woan.austin.ibm.com +
robin@pensoft.UUCP (Robin Wilson ) (10/08/90)
In article <1990Sep27.030149.13622@portia.Stanford.EDU> glowell@portia.Stanford.EDU (gary lowell) writes: >1. Configuring serial ports. > The problem here is likely to be with the Telebit setup. Given the 2 suggested methods of setting up a tty for bi-directional use, there are a number of possible problems that can arise from mis-understanding what transpires in the login/terminal use attempt. 1) PDELAY (or just delay) -- can be used for bi-directional serial port usage (or any port for that matter... including /dev/hft/0 -- the console). In this mode, the port starts a getty process on the tty and tells getty to 'wait for a character to arrive on the input buffer'. When getty starts DTR is raised, and the modem should be able to go into 'autoanswer' mode. However, if the modem is set with DTR strapped high (AT&Dx -- hayes command set, or one of the 'S' registers on the Telebit enhanced command set) (forgive me if I am not precise about some of this, I am not at work right now where I have all of the docs in front of me for the TB+) it will already be in autoanswer mode, so having our getty raise DTR will accomplish nothing (assuming S0<=001). Also, if the 'incoming call response' is set to echo call activity to the DTE (in this case the RS/6000) (hayes command set 'Q' register -- TB extended command set '??' register (probably Q as well)), then incoming calls will echo "RING" everytime a call is received. This will cause getty to fire up a login process and issue a login herald. IF THE LOGIN HERALD BEGINS ECHOING TO THE MODEM BEFORE CARRIER IS ACHIVED, THE MODEM WILL GO ON HOOK because it thinks someone is attempting to issue a command locally. The solution is to set the command response to 'Q6' on the hayes command set, and the equivalent for the extended command set. 2) PSHARE (or just SHARE) -- is intended for bi-directional tty usage as well. However, the getty running on this process works a little differently than PDELAY. Getty on a shared port waits to see carrier come high on the tty it is watching (EIA standards define pin 8 of a DB-25 connector to be used for carrier). The telebit signals carrier by either turning on the fast or slow connection lights, depending on the connection speed. When getty sees carrier come high it issues a login process, and herald. If the TB has carrier strapped high (hayes command set &C0, extended command set S52=000 (I think, but you better check)) then getty will always see carrier, and immediately send a herald. You should set carrier signalling to follow true carrier (hayes - &C1, TB - ?? can't remember... just look in the quick setup guide). 3) PENABLE (ENABLED) -- is intended for all other terminal usage. getty starts up and issues a login process immediately, and the corresponding herald. You will also want to set your modem up with DTR to follow EIA standards (hayes - &D2, extended ??) and DSR to follow standards (hayes - &S1, extended ??). This will insure that the port can properly disconnect when the process running on it terminates. The tty will also probably need to have 'stty attributes at LOGIN' include 'hupcl,'. This will insure that the port disconnects after getty terminates on 3 incorrect logins. The game is different if you are using the tty for a slip connection, so I won't touch that here. see if this stuff helps any for now. > >2. User Logins. > I'm not real sure, but I believe that there is a security feature on the USERS side of SMIT that you will need to double check... I just can't think of it right now. It is best to double-check the "change" user screen on smit, and get to know each field of the user entry. Also, make sure that the users don't have a password of "*" in /etc/security/passwd. Just because "su" works doesn't mean that the account is useable as a login account (this is just a hunch, but by saying that the accounts work OK on the hft, do you mean you can "su" to them?? please don't take this the wrong way, I >3. Escape in csh and ksh > I don't know about "csh" (since I never use it), but for "ksh" to use ESC for things like command line editing, you must first define an EDITOR environment variable. This can be accomplished with: "export EDITOR=<your favorite editor here -- mine is /usr/bin/vi>" or "set -o /usr/bin/vi". I imagine the "set -o" will also work on "csh". Robin D. Wilson.. Working for, but not officially representing to USENET IBM Level 2 Field Support.