HDTenEightyP/NetNews huggingface dataset:
From: prs9k@brain.med.virginia.edu (Phil Scarr)
Subject: Why doesn't the hpterm have resizable text?
Organization: Neuroclinical Trials Center, University of Virginia
Date: Fri, 13 Nov 1992 14:46:39 GMT

Why can't I resize the text in my hpterms like I can with my xterms or
aixterms?

	-Phil
-- 
PHIL SCARR        \      We are Microsoft...     /          (o) 804.243.0229
 University of    /     OS/2 is irrelevant.      \          (f) 804.243.0290
 Virginia,        \     UNIX is irrelevant.      /        prs9k@Virginia.EDU
 Neurosurgery     /     Openness is futile.      \     prs9k@Virginia.BITNET
 HP-UX is my life!\ Prepare to be assimilated... /   ...uunet!virginia!prs9k
From: navarro@pereiii.uji.es (Enrique Navarro Sanchis)
Newsgroups: comp.sys.hp
Subject: Re: Entry in /etc/disktab for HP 97558
Date: 5 Nov 92 12:16:47 GMT
Organization: Universitat Jaume I
X-Useragent: Nuntius v1.1

In article <28510344@hpuamsa.neth.hp.com> Frank Slootweg CRC,
franks@hpuamsa.neth.hp.com writes:
>Enrique Navarro Sanchis <navarro@pereiii.uji.es> writes:
>
>>	I'm an HP user.Is there any people buying a SCSI disk HP 97758 ?
>>	I have one and there is not an entry in the file /etc/disktab for
>>	that model.
>>	The CRC of HP said me : HP does not support this disk.
>>	Well, I make a disk and I not support this disk.
>
>  Welcome to the world of open systems:
>
>  We indeed make this disk, but we do not sell it to end-users. We sell
>it to OEMs, distributors, etc.. Those third parties sell the disk to you
>and should provide the support.
>
>Frank Slootweg, HP, Dutch Customer Response Center

First, sorry for my english.

Well, there is not the  first "third party disk" I have buyed..
I had buyed  some IBM disks to an OEM in Spain.
I had a trouble with the synchronous or asynchronous character of
this disk.I talk with the OEM and the OEM talk with IBM.Immediately
IBM send me a FAX with the solution.
When I do the same with an HP disk the responese is null.
I think that if HP makes the disk , it know the adecuate entry in
/etc/disktab
for this disk.I think the disk is checked by HP before sell it to OEM.
I have calculate the adecuate ns,nt and nc with the help of an
application in
my Macintosh and with the help of manuals, and th disk is working nicely.

HP could have saved me a lot of time.
However, thanks for all.
Newsgroups: comp.sys.hp,comp.mail.sendmail
From: linneman@rulcvx.LeidenUniv.nl (Stefan Linnemann)
Subject: Re: What sendmail do when quota exceeds ?
Organization: CRI, institute for telecommunication and computerservices.
Date: Fri, 13 Nov 92 09:42:09 GMT

In article <BxM299.E5q@news.cso.uiuc.edu> Paul-Pomes@uiuc.edu writes:
>a866700@hp9000.csc.cuhk.hk (Wong Siu To) writes:

>>I'd like to know what sendmail will do if user's quota is exceeded.
>>I've enabled quota on /usr/mail to limit the user mail box's size.  I
>>wonder the mail will be requeued, bounced back, or stored as usual when
>>the user's quota is exceeded.  If sendmail bypasses the quota checking,
>>how can I queue up the mail (but not delivered to user) in the mail
>>queue until the user files are cleared up ?

[...]

>At UIUC we don't have the time or interest to monitor quotas on student
>accounts (8900 on uxa, 5400 on ux4).  Our experience has been that if a
>student is over quota, it's usually because they belong to active mailing
>lists and haven't been reading their mail.  Storing mail in /usr/spool/mqueue
>for this kind of user waiting for them to clean up their act is a fast way
>to fill up /usr/spool/mqueue.

You should both check out the mailclean package, that was sent to one
of the sources newsgroups some time ago.  It's a neat little package
that allows you to control the use of /usr/spool/mail pretty neatly.
Large mailboxes will be truncated, the truncated part gets moved to
another directory, which I clean of files older than ten days.  This
gives the owner ten days to clean up their act.

Check archie for a ftp site or mail me for more info.

Happy administrating,
Stefan.
-- 
Stefan M. Linnemann		Internet: Stefan.Linnemann@CRI.LeidenUniv.NL
System Programmer UNIX		CRI, Leiden University, the Netherlands.
"Twenty push-ups a day and you'll never have to be afflicted with women again."
-- Daryl van Horne (sp?) [Jack Nicholson] in _the Witches of Eastwick_.

Xref: sparky comp.sys.hp:12634 comp.unix.questions:13045
From: daves@hpcvusd.cv.hp.com (Dave Serisky)
Newsgroups: comp.sys.hp,comp.unix.questions
Subject: Re: Resetting the /etc/utmp, wtmp files after crashed logins
Date: 6 Nov 92 17:35:04 GMT
Article-I.D.: hpcvusn.1992Nov6.173504.22054
Organization: Hewlett-Packard Co., Corvallis, OR, USA

In article <1992Nov5.143413.1956@rz.uni-karlsruhe.de>, chris@rz.uni-karlsruhe.de (Christian Finger) writes:
|> In article <1992Nov3.013718.15982@murdoch.acc.Virginia.EDU>, prs9k@brain.med.virginia.edu (Phil Scarr) writes:
|> | After a recent power failure, several PCs which were logged into our
|> | HP9000 system crashed but their logins still show up with the w command.
|> | There are no associated processes for these logins, they are just
|> | phantoms.  Is there any way to reset these ptys?  I would assume you
|> | could reset the /etc/utmp and wtmp files to do this, but I don't know
|> | how.  Help!
|> | 
|> | 	-Phil
|> 
|> The following program will do the job for you:
|> 
|> /*
|>  * this code is in the public domain.  do with it as you
|>  * please.  - jfh. 12/19/90
|>  */
|> ...

There are a few potential problems with the posted program.  The
/etc/utmp file contains entries of types other then USER_PROCESS or
DEAD_PROCESS.  The program will probably mess up the utmp entries for
the various system entries.  Also, I think there are a few other fields
that need to be set or cleared in order to make a "legal" DEAD_PROCESS.

Casual mucking with the /etc/utmp file can cause problems with your
system.  Problems can range from growing /etc/utmp files to duplicate
/etc/utmp entries for a single tty/pty (which can confuse applications)
to corruption that can prevent you from logging into your system and
will require a reboot to fix.

[BTW, take a look at the getutent(3C) man page for some convenient
functions for working with the /etc/utmp file.]

-- Dave Serisky
From: cpearce@nemesis.acs.unt.edu
Newsgroups: comp.sys.hp
Subject: Problems with regcomp() and regexec()
Date: 9 Nov 92 16:58:16 GMT
Organization: University of North Texas

HPUX 8.0, HP 9000/425

I'm currently trying to use the regular expression routines newly provided
in HPUX 8.0. As far as I can tell, I'm using the routines properly, but

    * I'm never able to get a full-line match and
    * Subexpressions don't seem to be behaving properly.

But it could just be a stupid mistake on my part also. :)

Here's the structure of my program...

#include <regex.h>

regex_t r1, r2;

void init()
{
    regcomp (&r1, "^ *#keyword *$", REG_EXTENDED);
    regcomp (&r2, "^ *#keyword +([^ ]+) *$", REG_EXTENDED);
}

void match()
{
    f = fopen (args...)

    while (!feof (f)) {
        fgets (str, 255, f);
        if (regexec (&r1, str, r1.re_nsub, rm, NULL))
            printf ("Mathced.\n");
        if (regexec (&r2, str, r2.re_nsub, rm, NULL))
            printf (Matched. sp = %x; ep = %x\n", rm [1].sp, rm [2].ep);
    }
}

main ()
{
    init ();
    match ();
}

I stripped all the error code out... I also forgot to declare some variables
above. str is char [255]. rm is regmatch_t [2].

If I use full-line matching (where the regexp is "^...$" I never return any
matches. By removing the full-line matching, I begin to get matches, but
rm [1].sp and rm [1].ep are equal -- no subexpression is returned.

The regular expressions themselves are supposed to match a keyword or
a keyword and an argument. Whitespace is ignored.

Am I making a fundamental error somewhere?
--
Chris Pearce, cpearce@nemesis.acs.unt.edu
Newsgroups: comp.sys.hp
From: mcm@gorgon.unx.sas.com (Mike Mitchell)
Subject: 'Cannot unlink' error from 'mv'
Date: Fri, 6 Nov 1992 21:46:35 GMT
Organization: SAS Institute Inc.

Can anyone tell me under what circumstances the following error
message is generated?

    mv: /xxx/yyy/zzz: Cannot unlink: No such file or directory

The command we are executing is 'mv zzz /xxx/yyy/zzz', and it
fails with the above error message.  We are running HPUX 8.07 on
720's and 750's.

The target is in an AFS volume, and we suspect that the error message
is caused by AFS.  However, it is very difficult for us to track this
problem down unless we know why 'mv' can't unlink the target.  I've
run strings on the 'mv' binary, and the error message is there.
I don't see that error message in other vendor's version of 'mv', so
I'd like to know what HP did.

If you have any idea why the 'mv' command would care about the
unlink failing in this manner, please send me mail.

-- 
------------------------------------------------------------------------------
Mike Mitchell			"There's laughter where I used to see a tear.
mcm@unx.sas.com			 It's all done with mirrors, have no fear."
(919) 677-8000 X6793			-- Blue Oyster Cult
From: b_kondalski@trwvssi.vssi.trw.com (Brian J. Kondalski)
Newsgroups: comp.sys.hp
Subject: Re: New HP Workstations
Date: 12 Nov 1992 14:37:57 GMT
Organization: TRW Vehicle Safety Systems, Inc.
Distribution: world
NNTP-Posting-Host: trwvssi.vssi.trw.com

Actually I'd like to see someone compile a list of all the current workstations
and show their performance relative to each other (maybe even with the list
prices for a similar configuration).  I'd be willing to do it if someone would
mail me the specs for the various platforms.

-- 
Brian J. Kondalski                                     b_kondalski@vssi.trw.com
TRW Vehicle Safety Systems Inc.                           Voice: (313) 781-7382
4505 West 26 Mile Road                                      Fax: (313) 786-7702
Washington, MI  48094                          "Views expressed here are MINE!"
     "Listen to the pictures flow; across the room into your mind they go."
From: franks@hpuamsa.neth.hp.com (Frank Slootweg CRC)
Date: Mon, 9 Nov 1992 12:15:34 GMT
Subject: Re: Entry in /etc/disktab for HP 97558
Organization: Hewlett-Packard, The Netherlands
Newsgroups: comp.sys.hp

Enrique Navarro Sanchis <navarro@pereiii.uji.es> writes:

>In article <28510344@hpuamsa.neth.hp.com> Frank Slootweg CRC,
>franks@hpuamsa.neth.hp.com writes:
>>Enrique Navarro Sanchis <navarro@pereiii.uji.es> writes:
>>
>>>	I'm an HP user.Is there any people buying a SCSI disk HP 97758 ?
>>>	I have one and there is not an entry in the file /etc/disktab for
>>>	that model.
>>>	The CRC of HP said me : HP does not support this disk.
>>>	Well, I make a disk and I not support this disk.
>>
>>  Welcome to the world of open systems:
>>
>>  We indeed make this disk, but we do not sell it to end-users. We sell
>>it to OEMs, distributors, etc.. Those third parties sell the disk to you
>>and should provide the support.
>>
>>Frank Slootweg, HP, Dutch Customer Response Center
>
>First, sorry for my english.
>
>Well, there is not the  first "third party disk" I have buyed..
>I had buyed  some IBM disks to an OEM in Spain.
>I had a trouble with the synchronous or asynchronous character of
>this disk.I talk with the OEM and the OEM talk with IBM.Immediately
>IBM send me a FAX with the solution.
>When I do the same with an HP disk the responese is null.

  So when you buy an IBM disk from an OEM you call the OEM for support,
but when you buy an HP disk from an OEM you call HP for support. Not
very consistent.
  This is exactly what I meant: You should call the OEM for support.
*If* the OEM needs support from HP then the OEM can contact HP. That,
like for IBM, the end result might be direct communication between HP
and you is not the issue.

>I think that if HP makes the disk , it know the adecuate entry in
>/etc/disktab
>for this disk.I think the disk is checked by HP before sell it to OEM.

  I do not know what you mean by "I think the disk is checked by HP
before sell it to OEM.", but if you mean "The disk is checked for proper
operation on HP9000 UNIX systems." then that is exactly what is *not*
done. If it was done, and we could guarantee proper operation at all
times, then we would support the disk on the mentioned systems, which we
do not.
  Believe me, there is no such thing as a general purpose disk. We make
different disks which are optimized for different platforms and our OEM
customers want us to manufacture yet several other types of disks.

> However, thanks for all.

  You are welcome. And no offense. I only want to make the picture clear
to you.

Frank Slootweg, HP, Dutch Customer Response Center
Newsgroups: comp.sys.hp
From: Will Allen <willa@vcd.hp.com>
Subject: Re: Problems with Deskwriter driver ver. 2.2 for Mac under 7.0.1?
X-Useragent: Nuntius v1.1a5
Date: Thu, 12 Nov 1992 00:45:44 GMT
Organization: Hewlett-Packard

Problems with Deskwriter driver ver. 2.2 for Mac under 7.0.1?

Try version 3.1 of the DeskWriter driver.  You can get it by calling HP
Driver 
Distribution at 303/353-7650.  Be sure and use the installer, don't just
drag
the new driver into your system folder.  If you still have trouble, call
the
HP Customer Service Center at 208/323-2551.

. . .Will

Will Allen
HP Vancouver "Home of DeskWriter" Division
willa@vcd.hp.com
Newsgroups: comp.sys.hp,comp.unix.admin
From: M.Enderby@daresbury.ac.uk
Subject: Re: HP9000/750 can't remap SCSI disk bad blocks
Keywords: SCSI disks, bad blocks, surface analysis, formatting
Reply-To: ufe@dlva.dl.ac.uk ()
Organization: SERC Daresbury
Date: Wed, 11 Nov 1992 11:14:27 GMT

We have seen similar problems. I believe that this is due to HP 
"enhancements" which do verification over and above the straight-
forward SCSI init command.
However, we have recently had chance to try out a format of a bad
WREN 7 on a 720 running HP-UX 9.0 and it successfully mediainited.
But ...
We saw another problem. The disk disappears after being hit by the
first SCSI command and has to be powered off/on for it to reappear.
It then disappears again. ie you can init it but you can't use it
again :-{. 
This may be a pre-release problem, or poss a hardware problem and we
are currently looking to do more extensive tests on a V9 system.
Cheers,
	Mark
========================================================================
Mark Enderby			   JANET - ENDERBY@UK.AC.DARESBURY
Systems Manager		  	   EARN/Bitnet - ENDERBY@DARESBURY.AC.UK
SERC Daresbury Laboratory
Keckwick Lane						
Daresbury
Warrington	tel:   0925-603353
WA4 4AD		Int:+44-925-603353
UK		fax:   0925-603174
From: myers@hpfcso.FC.HP.COM (Bob Myers)
Date: Fri, 6 Nov 1992 20:35:23 GMT
Subject: Re: Should HP 720 monitors be left on when not in use?
Organization: Hewlett-Packard, Fort Collins, CO, USA
Newsgroups: comp.sys.hp


While Clarke already posted a pretty good response, I thought I'd add a
few words.  Again, the standard disclaimer - the following does NOT
constitute an "official" statement by HP.  But I am working on displays
here, and when pressed will admit to knowing a few of the more common
answers.

First, I always recommend turning the display off when leaving for extended
periods - which includes turning it off overnight.  To be sure, *excessive*
power cycling can result in reliability problems (from thermal shock, for
one reason), but turning off for overnight or longer prevents both energy
waste and reliability problems of another type: the aging of the CRT.

The CRT is, on average, the shortest-lived component of any CRT display,
and unfortunately continues to age whenever powered up, as the cathode is
generally *always* active.  "Screen-savers" do not help all that much -
they will prevent patterns from "burning into" the phosphor, but the
cathode will continue to age as long as the tube is powered up and
biased.  Even when blanked, the cathode ages.  Actually, for most tubes,
the aging is slightly MORE rapid when the screen is blanked, due to the
"cloud" of electrons from the cathode being forced to stay in the cathode
region and thus increasing the rate of cathode "poisoning."  Turning the
display OFF is the only way to stop this (since most display don't allow
you to turn down the heater voltage!). 

An additional question came up having to do with the "wavering" of nearby
screens.  This can be caused by a number of things:

1. The line transient caused by power-cycling a display on the same AC
   circuit (which Clarke mentioned),

2. The degaussing action at power up (on color displays only), as was also
   mentioned by another respondent, and

3. The interaction or "beat" between the magnetic fields from the vertical
   deflection coils of the two monitors.  No two monitors, even those at the
   same nominal refresh rate, are exactly in sync, and their deflection
   fields can interact to produce "swimming" or "jitter."  This problem
   is greatly reduced in the most recent monitors which conform to various
   standards for magnetic field emissions (such as MPR-II), although you
   may still have a problem if the *affected* monitor is overly susceptible
   to external fields.  (The most recent HP workstation monitors - A1097C/D,
   A2088A, and A2094A - are all MPR-compliant, and so should emit much lower-
   intensity fields than earlier products - EXCEPT during the power-up degauss,
   as mentioned above.)


Bob Myers  KC0EW   Hewlett-Packard Co.      |Opinions expressed here are not
                   User Interface Tech. Div.|those of my employer or any other
myers@fc.hp.com    Fort Collins, Colorado   |sentient life-form on this planet.
Newsgroups: comp.sys.hp
From: harlan@cms-stl.com (Harlan Stenn (PFCS Corporation))
Subject: ~/.Xdefaults ignored by X11R4 and X11R5 under HPUX 08.07 ?
Organization: Computerized Medical Systems, Inc.
Date: Tue, 10 Nov 1992 17:47:15 GMT

On our 9000/7xx machines running HPUX 08.07 using the stock X11R4 as
well as the X11R5 stuff (from iworks) we have noticed that the
~/.Xdefaults file seems to be ignored.

Has anybody else noticed this?

Is a fix available?

Thanks...

Harlan
Newsgroups: comp.sys.hp,news.answers
From: geomagic@seismo.do.usbr.gov (Dan O'Connell)
Subject: Re: Life In Hell -- The Freeze Goes On
Organization: Seismotectonics Group, U.S. Bureau of Reclamation.
Date: Mon, 9 Nov 1992 16:33:22 GMT

In article <1992Nov8.204903.5303@news.media.mit.edu> floyd@media.mit.edu (Bob Sabiston) writes:

>   I also get those freezes--the heartbeat light
>   stops and everything.   Is this a common problem with the 720?
>   What is the best thing to do about it?  I have always hit the
>   TOC switch to reset... I always assumed the machine was hung,
>   so I never waited for 9 minutes to see if it would come back.

I started to see this problem 2 weeks ago when I connected a terminal
to the serial port for the first time. I had the problem on and off
for a week, then I disconnected the serial connection, and have not
had the problem since. Someone mentioned a patch related to serial
terminal connections and system hangs. Here is an excerpt.

Patch Name: PHNE_0686

Patch Description: S700/Newest update to the tty subsystem for HP-UX 8.07.

    4701-057356 : When writing to a port on which bi-directional data
                  flow is taking place, the port transmission may stop,
                  the writing process will be blocked and cannot be killed,
                  and the system must be rebooted.

    4701-061135 : Heavy use of the serial ports on a series 700 may cause a
                  system panic.  This problem has only been seen using slip
                  to do high speed data transfers.  The panic is a trap type
                  15 which apears as below:

                  trap type 15, pcsq.pcoq = 0.11a1f8, isr.ior = 0.40
                  @(#)B2352A HP-UX (sys.A.B8.07) #1: Thu Jun 27 18:34:09
                  MDT 1991 panic: (display==0xbf00, flags==0x0) Data
                  segmentation fault

I haven't tried it. I will be loading 9.0 soon so I thought I would
see if that takes care of it. In the mean time, serial connects are
not a frequent need, anyway ;).

Good Luck,
Dan
-- 
Dan O'Connell
geomagic@seismo.do.usbr.gov
Seismotectonics Group, U.S. Bureau of Reclamation
From: ajs@hpfcso.FC.HP.COM (Alan Silverstein)
Newsgroups: comp.sys.hp
Subject: Re: Re: hpterm's cut and paste - why local ?
Date: 10 Nov 92 18:54:57 GMT
Organization: Hewlett-Packard, Fort Collins, CO, USA

> ...why does cut and paste only work inside an hpterm, rather than
> between hpterms (as is case with xterms).

It does work between hpterms -- try bringing up the target window by
boinking on the frame and not the content (assuming you don't use
autofocus, dunno what effect that has).  Or try boinking the "focus" key
(left button usually) once in the content of the target window, without
moving the mouse while the button is down, before doing the paste.

The cut and paste interface model changed in some bizarre way for 8.0,
probably to match some external standard ("is better than better").  I
still don't understand or like it myself.  There are multiple buffers
(local and remote?), but since you get no feedback about what's in
which, and which is current, you can only use the feature with caution
and trepidation when going between windows.

Not speaking for HP, etc...
Newsgroups: comp.sys.hp,comp.mail.sendmail
From: paul@uxc.cso.uiuc.edu (Paul Pomes - UofIllinois CSO)
Subject: Re: What sendmail do when quota exceeds ?
Reply-To: Paul-Pomes@uiuc.edu
Organization: University of Illinois at Urbana
Date: Fri, 13 Nov 1992 15:51:12 GMT

viljanen@klaava.Helsinki.FI (Lea Viljanen) writes:

>Never! What happens if a user's mailbox is just under the treshold
>size and the user leaves for a vacation/conference/whatever? Right,
>goodbye new mail... Ten days isn't really very much.
>
>I think valid mail should never ever be removed by the adminstration.
>Moved perhaps, but never removed.

When you develop an automated method of handling the problem that scales
to 12,000 users, be sure to let me know.  Just to set the record straight,
we don't remove mail at UIUC, we bounce it to the sender.

/pbp
-- 
"A well-schooled electorate, being necessary to the security of a free State,
the right of the People to keep and read Books shall not be infringed."
	-- J. Neil Schulman
From: rjn@FC.HP.COM (Bob Niland)
Newsgroups: comp.sys.hp
Subject: Re: Configuring QIC150 SCSI on hp9k705
Date: 5 Nov 92 19:57:43 GMT
Article-I.D.: fc.Bx9E48.FIx
Reply-To: rjn@FC.HP.COM
Organization: Hewlett-Packard/WSY Ft.Collins,CO,USA
X-Newsreader: TIN [version 1.1.8 PL6]

Thad P Floryan (thad@cup.portal.com) wrote:

>> drives are NOT supported

> Does this mean:
> a) they used to be supported, and/or
> b) they are just not supported in HP-UX 8.0x, and/or
> c) they will be supported in a future release of HP-UX?

"Not supported" in HP parlance means:
 - "Not known to not work".
 - We have no reason to suspect that there is any danger in trying it.
 - But we don't recommend trying it unless you already own all the parts.

If we know something won't work, or has nasty side effects, we'll always
tell you.  Of course, knowledge of any problems may not be widely available,
so "unsupported" means "you're on your own".

"Supported" means:
 - We have tested the configuration and have reasonable confidence that
   problems will not arise.
 - The configuration is within regulatory, environmental and power limits.
 - The configuration in question is documented.
 - Response Centers will answer questions and provide assistance.
 - HP commits to resolve problems.
 - Lingering problems can be escalated.

Regards,                                              Hewlett-Packard
Bob Niland      Internet: rjn@FC.HP.COM               3404 East Harmony Road
                CompuServe:  71044,2124               Ft Collins CO 80525-9599

This article represents only the opinion[s] of its author, and is not an
official or unofficial position of, or statement by, the Hewlett-Packard
Company.  The text is provided for informational purposes only.  It is
supplied without warranty of any kind.
From: prgammel@hpindda.cup.hp.com (Preben Gammelmark)
Date: Thu, 5 Nov 1992 11:37:11 GMT
Subject: Looking for reference site HP3000/iX, LU6.2 to Tandem
Organization: HP Information Networks, Cupertino, CA