HDTenEightyP/NetNews huggingface dataset:
From: peter@ski.austin.ibm.com (Peter Jeffe 512.838.4019)
Newsgroups: comp.unix.aix
Subject: Re: Named spinning wheels
Date: 13 Aug 92 02:25:11 GMT
Organization: The Kernel Group, Inc.

In article <1992Aug3.183040.29775@olaf.wellesley.edu> kwolters@olaf.wellesley.edu (Keith Wolters) writes:
>I just installed AIX 3.2.2 on our model 520 which happens to be the
>nameserver for our campus.  named is now doing strange things.  It is
>running but appears to be spinning its wheels.  If I do a
>
>kill -USR1 pid
>
>to turn on debugging, the named.run file grows by 10Kbytes per second.
>The file caontains the following message over and over.
>
>resp: no addrs found for NS's

This is a bug that is present in all versions of BIND that I have seen.
It occurs when there is an NS record to forward a query to, but there
is no corresponding A record for the NS; ns_forw() doesn't handle this,
and goes into a loop.  This typically only happens when the A record
goes stale before the NS record.

But in AIX 3.2 an enhancement to implement caching of temporary failures
(as per rfc-1123 section 6.1.3.3) has caused this bug to surface much more
frequently.  This is because a server that times out or errors out is
marked as unavailable for 5 minutes; this causes the A record search in
nslookup() to fail, which produces the loop.

The fix for this is apar ix23937, which has been packaged for 3.2 in
ptf U406316, which should be available very soon.  For 3.1, emergency
fixes are currently available.

-- 
peter jeffe  peter@aixwiz.austin.ibm.com
Newsgroups: comp.unix.aix
Subject: Arc-Info/Arc-View Inquiry
From: nuessle@vax1.umkc.edu
Date: Tue, 18 Aug 1992 04:22:15 GMT
Organization: University of Missouri - Kansas City

Net-Master:

	Finding myself interacting with and beginning to support Arc-Info
and Arc-View.  Running on RS/6K:AIX networked interactive with MVS & VTAM
to Windowed PCs.

	Comments on these packages solicited.  Particularly interested in
operating concerns in the AIX environment.  Please respond privately or via
Net according to importance for the Net.

*		*	*				*		      *
Nick Nuessle	*  PE	*   nuessle@vax1.umkc.edu	*   Only my viewpoints
Student		*KA0ZAP	*   nuessle@umkcvax1.bitnet	*   unless noted.
	UMKC:  Pushing back the Frontiers of Ignorance in the Fly-Over Zone

*    English:  Where "slim chance" and "fat chance" have identical meanings   *
From: dkf@chem.ucsd.edu (David K. French)
Newsgroups: comp.unix.aix
Subject: Re: Problems with tar
Date: 13 Aug 1992 05:11:58 GMT
Organization: University of California San Diego, Chemistry
NNTP-Posting-Host: chedccf0.ucsd.edu

In article <BIS.92Aug12161845@maud.ifi.uio.no> bis@ifi.uio.no (Bjorn Ivar Stark) writes:
>Before I used this command when I e.g. moved a user from
>one machine to another. 
>
>   root@obelix /u/obelix/d: tar cvfb - 20 sigurd |\
>   maestria "cd /u/maestria/c; tar xfBp -" 
>
>Now it stops half way trough with the messages "broken pipe".
>Any idea to what can be wrong.
>--
>-----------
>Oystein Fosli, B240
>Norsk Hydro a.s           Ph.: (472) 739660       
>Postboks 200		  Fax: (472) 739555
>1321 STABEKK	     internet: bis@ifi.uio.no
>Norway


	Interesting.  We are running v3.1.8 and get a similiar error
	while running dump across a pipe to an IRIS.  It has something
	to do with stdout being the file and using a network connection.
	I was able to do dumps into pipes with no problems, as long as
	the pipe didn't access the network.  

	I don't know if you will see this, but we usually have a runaway
	process lurking in the background around the same time that the
	dump gets run.  So far, I think every time we've gotten the 
	broken pipe error, there was one running in the background.

--
-- 
David Knight French		Email Addresses:		Phone:	
UCSD - Dept of Chemistry	INTERNET: dkfrench@ucsd.edu	  (voice/fax)
9500 Gilman Drive		UUCP:     ucsd!dkfrench		(619)534-4193 /
San Diego, CA  92093-0314	BITNET:   dkfrench@ucsd.bitnet	(619)534-6255
From: derek@watson.ibm.com (Derek Lieber)
Subject: Re: xcdb on aix 3.2
Date: Wed, 12 Aug 1992 19:58:58 GMT
Reply-To: derek@watson.ibm.com (Derek Lieber)
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: IBM T.J. Watson Research Center

In article <1992Aug12.191337.23921@watson.ibm.com> jonms@pi.watson.ibm.com () writes:

>Has anyone else experienced problems using xcdb on AIX 3.2?

Ptrace / debugger  problems were introduced by operating
system update U402846. APAR is IX27609 was assigned to
the problem and a PTF was recently issued to correct it.
-- 
Derek Lieber
derek@watson.ibm.com
Newsgroups: comp.unix.aix
From: sangster@news.ans.net (Paul Sangster)
Subject: Anyone debugged AIX before?
Summary: Interested in using printfs in TCP/IP code
Date: Fri, 21 Aug 1992 14:44:48 GMT
Organization: Advanced Network & Services - Reston, VA

Greetings,

I am trying to do alittle kernel hacking on the TCP/IP
component of AIX.  My question is of someone who had done
this ... how did you getting debugging info printed out
on the console?  I see lots of printfs floating around in
the code, but they don't seem to do anything when compiled
into the netinet.  Is their a special kernel library
with its own printf (or does it just use libc)?

Please direct follow ups via e-mail.

Thanx,

Paul


-- 
_______________________________________________________________________
Paul Sangster                        Snail mail: 1895 Preston White Dr. 
Advanced Network & Services                      Suite 310
Information & Applications Services Group        Reston, Va 22091
From: terry@phoenix.ocf.llnl.gov (Terry Heidelberg x24154)
Newsgroups: comp.unix.aix
Subject: Re: Vi is still broken.
Date: 19 Aug 92 01:07:13 GMT
Organization: LLNL

In article <1992Aug17.163739.29534@APS.Atex.Kodak.COM>, 
root@stimpy.rus.uni-stuttgart.de (Bob Mayotte) writes:
|> We have had problems with vi hanging on systems running 3.2.1.
|> We have ordered and applied the "fixes" 
|> 
|> ix24895 pty device driver (processes hung on output)
|> ix24329 posix line discipline (processes hung on input, w/ input available)
|> 
|> But vi still occasionally hangs. 
|> Does anyone else still have this problem.
|> 
|> By the way, Control-C "unhangs" vi and puts you in command mode.

We don't see hangs; what we see is an occasional interactive program
looping to beat the band.     Since upgrading to 3.2.1 (later to 3.2.2)
we have seen the following programs looping:
    vi aixterm less info_ascii 
and maybe a few more I forget.   The typical scenario is the user 
telnet's in, works away, and for some reason has the session broken
(who knows, maybe after something hangs) after which s/he logs in
again, or goes to some other work, unaware that one of his/her processes
is running amok.    Since we have 18 550 cycle servers to
look after, some of these runaways chew up quite a bit of cpu time
before they get killed by a system administrator.      I have vague
suspicions of (a) the telnetd, (b) something in the way these programs
handle signals or system-call errors, (c) [the ever popular] AIX.

Anyone have similar experiences, or ideas about the cause?  Are the
above fixes likely to help us?

Thanks.
From: king@lisa.usbm-ccn.gov (Paul King)
Newsgroups: comp.unix.aix
Subject: Memory and paging space on RS/6000
Date: 12 Aug 92 16:15:36 GMT
Organization: U.S. Bureau of Mines, Albany Research Center

Thanks in advance

Paul E. King
king@wolfie.usbm-ccn.gov
Newsgroups: comp.unix.aix
From: scotte@cdsac.uucp (L. Scott Emmons)
Subject: Re: Reducing filesystem size
NntpPostingHost: cdsac
Date: 20 Aug 1992 23:24:32 GMT
Organization: Cable Data (U.S. Computer Services), Sacramento, CA

In article <1992Aug19.203658.23130@godzilla.quotron.com> greg@godzilla.quotron.com (Greg "Maddog" Knauss) writes:
>How, exactly, do you reducing the size of /usr?  The normal method of
>shrinking a filesystem is to copy it to tape, remove it, recreate it at
>the new size and move the files back.  But /usr has libc.a and if you
>remove that, the machine staggers around a little and then dies.  Anybody
>have any ideas?  (THAT'S the last time I do a full installation of Info
>Explorer...)

We have done this on our machines. What we do is create an "mksysb"
tape with an altered ".fs.size" file, and then boot off the tape and
restore the system.

The procedure for doing this: (as root)

o run 'mkszfile' to generate the .fs.size file.

o (generally a good idea to do an 'mksysb' here just in case an error
   occurs and the system is unrecoverable from the altered tape.)

o edit "/.fs.size". The format of this file is:

  volume_group megs_per_part dev_name mnt_point num_parts lv_megs fs_type

 for example, on one of our systems:

  rootvg 4 hd2 /usr / 40 160 jfs

 The fields you are interested in are the num_parts and lv_megs
 fields. Change these to the appropriate values:

	lv_megs	  is the logical volume size in Megabytes

	num_parts is the number of partitions for the LV. Just use
	          lv_megs / megs_per_part to get this value.

o run 'mksysb' to back the system up to tape.

o Now, follow the instructions in the installation guide for restoring
  from a "mksysb" backup. If you have logical volumes outside the
  'rootvg' volume group, you will have to import them back into the
  system. This can be done from "smit lvm"...


It's neither an easy nor a pleasant task, but it's the only way I know
of to free up that valuable disk space...
 
			   L. Scott Emmons
		     csusac.csus.edu!cdsac!scotte
From: curt@ekhadafi.austin.ibm.com (Curt Finch 903 2F021 curt@aixwiz.austin.ibm.com 512-838-2806)
Newsgroups: comp.unix.aix
Subject: Re: gdb crashes AIX 3.2.2
Keywords: AIX 3.2.2 gdb gnu debugger slac slack
Date: 21 Aug 92 21:04:44 GMT
Organization: IBM AWD, Austin

engberg@raven.SLAC.Stanford.EDU (daVe) writes:
>unfortunately, gnu's gdb debugger seems to completely crash the
>system whenever a program is run from within it.  (i've tried
>several times, with different programs)

All crashes are bugs.  (Now there's an absolute.)

Problem is probably already solved by this apar:

59702: ix27609 WHEN USING XDE AND AIX 320 WITH SELECTIVE FIX: U402846
PMR: 4x964,148,000 created  92/05/22
  Product bos320
    1.39 delta R2/sys/ldr/ld_memory.c

The following apars and defects are included in U405614:
     ix28355 33009
     ix28357 45819
     ix23007 47058
     ix28367 48987
     ix25587 49817
     ix25588 49818
     ix25651 50641
     ix26022 51188
     ix28370 51968
     ix26441 52944
     ix26834 55952
     ix26818 56057
     ix25928 56058
     ix26699 57481
     ix27609 59702

PTF Status -CLOSED means orderable-: U405614:  STAT=CLOSED


In the LPP bos, PTF U405614 shipped the following files:
     /unix
-------------------------------------------

-- 
curt@aixwiz.austin.ibm.com (Curt L. Finch) | AIX NFS/NIS Field Quality 
My views are unrelated to those of IBM     |        Austin, TX
FICA is a massive wealth transfer from young middle class to old middle class.
From: losburn@teal.csn.org (Lynn Osburn)
Newsgroups: comp.unix.aix
Subject: Re: uucp and getty on a shared tty - anybody done it ?
Date: 12 Aug 92 14:47:24 GMT
Organization: Colorado SuperNet, Inc.

>uucp can't work unless permissions grant it read access to the port. So far,
>the solution that I have come up with is to put a "chmod 666 /dev/tty1" into 
>the root cron file, and this works, but is hardly elegant.  What is the 
>solution to this problem ?  Is there some way to set the default permissions
>that getty configures a port with ?
>

Use pdelay instead of pshare.  In enable or share mode, getty grabs the port,
waiting for a login.  In delay mode, there is no getty until CD goes high,
indicating a connection, and then after a short time (~3 sec?), or if 
characters are recieved, a getty is spawned to handle the (implied) login.

Since getty hasn't locked the port till CD changes state, uucp can grab it
for outgoing calls.  When he gets a Carrier Detect, getty can't start because
uucp has a lock on the port...

oz
Newsgroups: comp.unix.aix
From: bruce@ncs.com (bruce parkin)
Subject: Re: AIX3.2 and uucp/cu across rs232 lines
Organization: National Computer Systems, Inc.
Distribution: usa
Date: Mon, 17 Aug 1992 16:29:24 GMT
Keywords: news, email, uucp

For purposes of News and E-mail I would like to be able
to configure a port as bidirectional, so that I can dial
out thru the same port as someone else dials into. 

I have tried a shared port (pshare) and delayed (pdelay),
but I can seem to get nothing to allow bidirectional
access. Has anyone got this to succeed, and how?

Thanks for any help you can give.


-- 

Bruce E. Parkin
bruce@ncs.com
uunet!ncsys!bruce
Newsgroups: comp.unix.aix
From: rahner@iscnvx.lmsc.lockheed.com (Mark Rahner)
Subject: Re: xterm: no available ptys
Organization: Lockheed Missiles and Space Co.
X-Newsreader: Tin 1.1 PL4
Date: Fri, 14 Aug 92 22:39:14 GMT

bis@ifi.uio.no (Bjorn Ivar Stark) writes:
: When I try to start more than a certain limit of xterms I get
: this error-message:
:     fosli@asterix: xterm
:     xterm: no available ptys

This has given us massive headaches.  Our system administrator has
increased one of our RS/6000s to what he says is the limit of 64.
Sorry, but I don't know how.

When we first reported this to IBM, IBM said "Xterm is provided on the
RISC/6000 as a binary sample only and is unsupported."  (More on this in
a minute.)  After explaining to the #!%&*s that the problem wasn't with
xterm, but with their system chewing up ptys, they reexamined the problem
and determined that the software that controls our many X Stations was
not properly releasing the ptys when the X Stations were being turned
off.  As yet, this has not been fixed.

A resonable solution might be to run xdm.  Unfortunately, our ex-MVS
system administration can't bring themselves to run this unsupported
program either.  If only IBM shipped systems running xdm out of the box...
At least we can start xterms ourselves.  Anyway, when our system admin-
istration remembers, our system gets rebootted every couple of days.
When they don't, we live with confused users without ptys.

Now more as promised above...  When is IBM going to learn that support
for standards means more than just lip service?  If they had to log into
six different architectures on a daily basis as I sometimes do, then maybe
they would understand the value of xterm.  We did not buy IBM hardware to
run IBM's custom X clients.  We bought it to run core clients like xterm
so that the IBM systems would integrate gracefully with our other hardware
so our users would be less confused so that they would be more productive.
We want our users to run xterm so that, in the future, they will require
less retraining.  Vendor independence and portability of user knowledge
are the two big payoffs of open systems.  Until recently, it has been in
IBM's interest to resist open systems.  IBM may not (want to) understand
the motivation behind open systems, but we must.  IBM may want to dictate
the way that we use their hardware, but that's just not going to happen.
We must work together to demand the support we need, not the support IBM
thinks we need.  They make excellent hardware but they've got to start
cooperating.

Support X core clients or lose customers!
-- 
Mark V. Rahner   rahner@lmsc.lockheed.com
From: delvecch@cmf.nrl.navy.mil (Vincent Del Vecchio)
Newsgroups: comp.unix.aix
Subject: Sendmail 5.67
Date: 19 Aug 92 17:23:42 GMT
Distribution: comp
Organization: Connection Machine Facility, NRL

I am trying to port this latest release of Berkeley sendmail to AIX 3.1.5
and have run into (so far) one major problem.  At link time, I get an
undefined symbol "edata".  Presumably this is somewhat related to the
fact that IBM doesn't use a.out format (or any standard format) binaries,
nor any standard kind of linker.  Is there a way to work around this?
I suppose I could always hack out the code that does configuration file
freezing.
From: tim@osiris.usi.utah.edu (Tim Burns)
Newsgroups: comp.unix.aix
Subject: Problem with "vi"
Date: 18 Aug 92 22:31:00 GMT
Reply-To: tim@osiris.usi.utah.edu (Tim Burns)
Organization: School of Engineering and Applied Sciences, UCLA
Originator: chmjpn@osiris.usi.utah.edu

Hello,

Does anyone know of any fixes or updates which would keep "vi" from
hanging.  I have tried using "aixterm" instead of "xterm", resizing
the window, all sorts of hacks, and none seem to work.  Does anyone
know why this is happening?  Is IBM doing anything to fix it?

Thanks,

Tim Burns


-- 
     *__T__*               No matter how deeply I go down into myself
       _i_                 my God is dark, and like a webbing made
      */m\*                of a hundred roots that drink in silence.
                           		--Ranier Maria Rilke 
Newsgroups: comp.unix.aix,comp.protools.tcp-ip
From: block@ief.itg.ti.com (Bucky Block)
Subject: Re: HELP with tftpd daemon on AIX, please
Date: Fri, 21 Aug 1992 15:04:37 GMT
Organization: IEF Developement, Texas Instruments Inc., Plano Texas
X-Disclaimer: This message was written by a user at Texas Instruments Inc.
              The opinions expressed within are those of the user and not
              necessarily those of Texas Instruments.

In article <1992Aug20.191704.14074@interlan.Interlan.COM> wieder@interlan.Interlan.COM (Scott Wieder) writes:

   I need help configuring the tftpd daemon on an RS6000 running
   AIX.  According to someone from IBM, AIX does not support a
   default directory.

   Can someone tell me how to set up tftp boot on an RS6000 running
   AIX?  I am specifically interested in knowing what is the default
   directory or how to specify a home directory for the tftpd
   daemon.


From the tftpd man page: (AIX 3.2)

Access Control

  The /etc/tftpaccess.ctl file is searched for lines that start
  with allow: or deny:.

  Other  lines  are  ignored.  If the file doesn't exist, access is
  allowed.   The allowed directories and  files  minus  the  denied
  directories and files can be accessed.  For example, the /usr
  directory might be allowed and the /usr/ucb directory might be
  denied.  This means that any directory or file in the /usr direc-
  tory, except the /usr/ucb directory, can be accessed.  The en-
  tries in the /etc/tftpaccess.ctl file must be absolute path
  names.  The /etc/tftpaccess.ctl file should be write-only by the
  root user.

  The search algorithm assumes that the local path name used in the
  tftp command is an absolute path name.  It searches the
  /etc/tftpaccess.ctl file looking for allow:/.  It repeatedly
  searches for allowed path names with each partial path  name con-
  structed by adding the next component  from  the  file path name.
  The  longest path name matched is the one allowed.  It then  does
  the  same  with  denied  names, starting with the longest allowed
  path name matched.

  For example, if the file path name were /a/b/c and the
  /etc/tftpaccess.ctl file contained allow:/a/b and deny:/a, one
  allowed match would be made (/a/b) and no denied match starting
  with /a/b would be made, and access would be allowed.

  If the /etc/tftpaccess.ctl file contained allow:/a and deny:/a/b,
  one allowed match would be made (/a) and one denied match start-
  ing with /a (/a/b) would be made, and access would be denied.  If
  the /etc/tftpaccess.ctl file contained allow:/a/b and also con-

--

Bucky Block                         |     block@ief.itg.ti.com
IEF Development                     |     TIMSG: BLOC
Texas Instruments, Plano Texas      |     (214) 575-4732

-- 

Bucky Block                         |     block@ief.itg.ti.com
IEF Development                     |     TIMSG: BLOC
Texas Instruments, Plano Texas      |     (214) 575-4732
From: shaggy@malone.austin.ibm.com (David J. Kleikamp)
Newsgroups: comp.unix.aix
Subject: Re: Help: Can't get lex to work ???
Date: 17 Aug 92 16:51:40 GMT
Organization: IBM, Austin

In article <1992Aug4.182637.22839@unixg.ubc.ca> lindholm@ucs.ubc.ca (George Lindholm) writes:
>I can't get lex to work on our RS6000 560 3.2 system. Here's what happens:
>lindholm@numeric2$ make lex.c
>        lex lex.l
>99: (Error) Invalid character
>The error code from the last failed command is 1.
>
>Make Quitting.
>
>
>where line 99 is the very last line of the file (I get the same result if do
>"lex /dev/null").

I think this is addressed by APAR IX27619.  A fix should be available at this
time.

Sorry it took so long to respond.  It's hard to keep up with this newsgroup.

Shaggy
-- 
---------------------------------------------------------------------------
David J. "Shaggy" Kleikamp	shaggy@malone.austin.ibm.com
The content of this posting is independent of official IBM position.
From: shair@barolo.cso.uiuc.edu (Bob Shair)
Newsgroups: comp.unix.aix
Subject: Re: Two new 220 installs: what can I delete?
Date: 13 Aug 92 14:51:36 GMT
Reply-To: rmshair@chgvmic1.vnet.ibm.com
Organization: IBM Champaign

You can begin throwing away the contents of /usr/lpp/info/En_US and /usr/sys
(after first installing all the products you want from /usr/sys, and backing
up everything to tape or disk).  

That should get you enough to get started. 
--

Bob Shair                          shair@chgvmic1.vnet.ibm.com
Scientific Computing Specialist    SHAIR@UIUCVMD (bitnet)
IBM Champaign
Newsgroups: comp.unix.aix
From: grund@pyrite.SOM.CWRU.edu (Victor Grund)
Subject: Re: UPS for RS6000 52H
Organization: International Business Machines, Cleveland, Ohio, USA
Date: 13 Aug 92 21:42:39

In article <qb4mqj9#@aix01.rz.fht-mannheim.de> roesch@aix01.rz.fht-mannheim.de (Friedrich Roesch) writes:

     We want to connect our RS6000 52H with an UPS. Did this somebody before
     us, who could give us some hints for automatic shutdown in case of
     power failure?


I have worked with a Best Power Technology UPS and a RISC System/6000
model 520.  The UPS came with source code for several Unix variants,
but nothing specifically for AIX 3.x.  The generic system v code
worked like a charm without modifications.  Basically it is a
background process that constantly checks a serial port.  When the UPS
signals that it has switched to internal power, a shell script runs
which informs all users of imminent shutdown within x minutes... then
runs the shutdown command.  All very simple and easy to customize for
your particular setup by altering the shell script that the UPS
process calls.  The particular UPS from Best that I installed was very
feature-laden.  It keeps a history of power fluctuations, voltage
histograms, and other related data internally, which can be recovered
by sending commands through the serial port, much like communicating
with modem control features.

Check the Third Party Hardware List for a list of UPS vendors for the
RISC System/6000.

Cheers,
Victor
--
Victor D. Grund        | grund@pyrite.som.cwru.edu 
IBM Cleveland Mktg Ops | grund@vnet.ibm.com
RISC System/6000 & AIX | DETVMIC6(VGRUND)
(216) 664-7381         | FAX: (216) 664-7348
Xref: sparky comp.unix.aix:8957 comp.windows.x:15449
From: jern@visual1.jhuapl.edu (Bob Jernigan)
Newsgroups: comp.unix.aix,comp.windows.x
Subject: Re: Hanging X11R4 server under AIX3.2.1
Date: 20 Aug 92 17:09:09 GMT
Reply-To: jern@visual1.jhuapl.edu (Bob Jernigan)
Organization: Johns Hopkins University

In article <1992Aug20.121336.10998@email.tuwien.ac.at>, jf@edv6000.tuwien.ac.at (Josef Fritscher) writes:
|> In article <1992Aug20.085303.23888@fwi.uva.nl>, wijkstra@fwi.uva.nl (Marcel Wijkstra (AIO)) writes:
|> |> tom@bim.itc.univie.ac.at (Tom Kovar) writes:
|> |> 
|> |> #  I am running AIX3.2.1 on more RS6000's (550's and 220's). In some cases
|> |> #(not quite reproducible), when the Xserver exits, the console keeps hanging.
|> |> #That means, that the Xserver process really exits, but the background with
|> |> #traces of some of the windows stays on the screen, and the console + keyboard
|> |> #are dead. The only help I know is reboot :(
|> 
|> This problem is known since AIX 3.1.3 and it's nice to see some workarounds
|> here, but the real question is, when will IBM will fix it ...
|> 

I hate to reboot - try logging as root from another terminal & killing the
offending process.  Works for me.

bob