HDTenEightyP/NetNews huggingface dataset:
From: brown@ftms.UUCP (Vidiot)
Newsgroups: comp.sys.sun.hardware
Subject: Re: QIC-XX tape question
Date: 22 Jul 92 15:23:36 GMT
Reply-To: brown@ftms.UUCP (Vidiot)
Organization: Vidiot's Other Hangout

In article <55590003@hpcc01.corp.hp.com> derekd@hpcc01.corp.hp.com (Derek Dang) writes:
<
<    Does anyone know whether a QIC-150 drive can be forced to write in 
<QIC-24 format?  The man page indicates that QIC-24 format will be written
<if it is detected that the tape is using that format.  My question is
<whether one can force a QIC-150 drive to write QIC-24 without having
<a QIC-24 tape first.

NO!  The track density is different between the two QIC types.  QIC-150 can
read QIC-24 tapes, but it cannot write it.
-- 
harvard\
  ucbvax!uwvax!astroatc!ftms!brown  or  uu2.psi.com!ftms!brown
rutgers/
INTERNET: brown@wi.extrel.com  or  ftms!brown%astroatc.UUCP@cs.wisc.edu
Newsgroups: comp.sys.sun.hardware
From: mike@Turing.ORG (Michael M. Chapman)
Subject: Re: HELP!!
Organization: The Turing Project, Charlottesville Virginia.
Date: Sun, 26 Jul 1992 21:03:45 GMT


I've now gotten it to the point where the sun recognises my SCSI drive, but
says "Waiting for disk to spin up..."
"Please start it, if nececary, -OR- press any key to quit."

Any ideas? Why wouldn't the SCSI controller think the disk was spun up?

-- 
   +------------------------------------------------------------+
   |  mike@turing.org (Mike Chapman) aka FourDee aka Sidhe      |
   |  fourdee@rever.nmsu.edu (if mail bounces at above address) |
   +--------------------------------+---------------------------+
   |                                | The above message was not |
   |  Just say NO to Perot in '92.  | proofread, so an obscene  | 
   |                                | comments are accidental.  | 
   +--------------------------------+---------------------------+
From: cudep@warwick.ac.uk (Ian Dickinson)
Newsgroups: comp.sys.sun.hardware
Subject: Re: QIC-XX tape question
Date: 22 Jul 92 11:39:00 GMT
Organization: Team Limpid's Meathead With Aptitude - Kunst und Wahnsinn

In article <1992Jul21.023909.6655@kpc.com> mjacob@kpc.COM (Matt Jacob) writes:
>|>     Does anyone know whether a QIC-150 drive can be forced to write in 
>|> QIC-24 format?
>No. Be glad it even *reads* QIC-24 or 9trk QIC-11.

I am.

How come SGI get their QIC-150 drive to write QIC-24 as well?
(Or is this an exaggerated rumour?)

>QIC-150 is 18 tracks, and QIC-120 (which the Viper silently
>uses if the tape is a DC600A) is 15 tracks.

Hmm.

Cheers,
-- 
\/ato - Ian Dickinson - NIC handle: ID17                              Yo! Bum 
vato@csv.warwick.ac.uk  ...!mcsun!uknet!warwick!vato                     rush
/I=I/S=Dickinson/OU=CSV/O=Warwick/PRMD=UK.AC/ADMD= /C=GB/                 the
@c=GB@o=University of Warwick@ou=Computing Services@cn=Ian Dickinson     show
From: jc@raven.bu.edu (James Cameron)
Newsgroups: comp.sys.sun.admin
Subject: Re: How to properly call rcp.yppasswdd.
Date: 28 Jul 92 21:38:00 GMT
Organization: What do you mean 'That *can't* be done????'
In-reply-to: jc@raven.bu.edu's message of 28 Jul 92 16:18:13 GMT

>>>>> "Me" == James Cameron <jc@raven.bu.edu> writes:


  Me> System: Running SunOS 4.1.1

  Me> Problem: rpc.passwdd does not correctly update NIS information.
  Me> I recall someone mentioning that there was a bug and you simply
  Me> needed to do somthing trivial.  What might this be?

  Me> Thanks for the info!

  Me> --


The "solution" is to call it with an invalid argument which is simply
ignored: 

if [ -f /usr/etc/rpc.yppasswdd ]; then
        /usr/etc/rpc.yppasswdd /etc/passwd -x -m passwd ; echo " yppasswdd "
fi

[...This is located in /etc/rc.local...]

Thanks goes out to:

 Hannu Visti <visti@cs.hut.fi>

and the many more I am sure to receive before this gets circulated. *8-)

--
			-- James Cameron  (jc@raven.bu.edu) (617) 353-2879
					  
    System Manager, Signal Processing and Interpretation Lab.  Boston, Mass  
------------------------------------------------------------------------------
"But to risk we must, for the greatest hazard in life is to risk nothing.  For
the man or woman who risks nothing, has nothing, does nothing, is nothing."
	(Quote from the eulogy for the late Christa McAuliffe.)
Newsgroups: comp.sys.sun.admin
From: anselmo-ed@cs.yale.edu (Ed Anselmo)
Subject: Re: popper - Post Office Protocol Server
Organization: Yale University, Dept. of Computer Science, New Haven, CT
	<CKD.92Jul23164330@loiosh.eff.org>
	<1992Jul24.163427.28213@blaze.cs.jhu.edu>
Date: Fri, 24 Jul 1992 19:23:31 GMT

The version of popper I grabbed ("1.831beta") compiles with the SunOS
4.1.1 libresov.a (based on BIND 4.8.1 I believe) as well as with the
BIND 4.8.3 libresolv.a.

The original poster probably defined BIND43 but didn't link against
libresolv.a (or do the libc.so modification thang).

cc  pop_dele.o pop_dropcopy.o pop_dropinfo.o  pop_get_command.o pop_get_subcommand.o pop_init.o  pop_last.o pop_list.o pop_log.o pop_lower.o  pop_msg.o pop_parse.o pop_pass.o pop_quit.o  pop_rset.o pop_send.o pop_stat.o pop_updt.o  pop_user.o pop_xtnd.o pop_xmit.o popper.o -o popper
ld: Undefined symbol
   __res
Compilation failed
*** Error code 2
make: Fatal error: Command failed for target `popper'
-- 
Ed Anselmo   anselmo-ed@cs.yale.edu   {harvard,cmcl2}!yale!anselmo-ed
From: spxpmf@thor.cf.ac.uk (Phillip Fayers)
Newsgroups: comp.sys.sun.admin
Subject: Re: ATTENTION: A problem with dump under 4.1.1
Keywords: tape, cleaning
Date: 24 Jul 92 09:20:05 GMT
Organization: Physics Dept. University of Wales, Cardiff
X-Mailer: Cardiff Computing Maths PP Mail Open News Gateway

In article <1992Jul23.132034.6025@csc.canterbury.ac.nz> agw@math.canterbury.ac.nz (Allen Witt) writes:
|
| billq@fnal.gov (William R. Quayle) write
|>In article <1992Jul21.195006.112389@zeus.calpoly.edu>, etsiao@joule (Eddie Tsiao) writes:
|>|> In article <1992Jul20.073110.20195@aristo.tau.ac.il> shani@GENIUS.TAU.AC.IL (Oren Shani) writes:
|>|> We have had (are having?) similar problems.  We occationally get an error:
|>|> 
|>|>   DUMP: Tape write error 753 feet into tape 1
|>|>   DUMP: fopen on /dev/tty fails
|>|>   DUMP: The ENTIRE dump is aborted.
|>|> 
|>Sorry if I've missed this in an earlier followup, but has the drive been
|>cleaned?  I realize that 8mm cleaning is a sensitive issue (you don't want
|>to overdo it or *ever* use video cleaners!), but I encountered these same
|>errors on our servers.  After a cleaning with an Excabyte 8mm cleaning
|>cartridge, the problems subsided.
|
stuff deleted
|  DUMP: write: I/O error
|
|  DUMP: write: I/O error
|
|  DUMP: Tape write error 4 feet into tape 1
|  DUMP: fopen on /dev/tty fails
|  DUMP: The ENTIRE dump is aborted.
|****************************************************************
|*********** Dump has failed, aborting rest of dump.*************
|****************************************************************
|Bad tape? Faulty hardware? perhaps.
stuff deleted
|	The question to be answered is - Is this a hardware problem or
|a software problem or a firmware problem or an interaction between all
|or any two of these? 
|	Do sun know of this problem? Have they a patch for it? Is this
|why they are promoting upgrades to Exabyte 8500 units ( ours is an 8200)?
|
I've been having very simlar problems, last nights dump failed with-
  DUMP: dumping (Pass IV) [regular files]
  DUMP: Tape write error 10 feet into tape 1
  DUMP: fopen on /dev/tty fails
  DUMP: The ENTIRE dump is aborted.

I've had this happen before (oddly enough its usually 10 feet into the
tape) so I usually redo the dump by hand when I arrive in the morning
and it works! I've tried cleaning the drive but it doesn't seem to do
anything.
I'm about to rewrite the dump scripts so that they reposition the tape
and have another go if they fail.
I also see occasional errors logged to the console:

Jul 24 03:05:42 orion vmunix: st1:  I/O request timeout
Jul 24 03:05:42 orion vmunix: sm0:  target 5 reverting to async operation
Jul 24 03:05:42 orion vmunix: sm0:  resetting scsi bus
.......

although this last one is the first to actually coincide with a tape
error.
I'll probably contact our tape drive supplier to see if he has any
clues.

-- 

Phillip Fayers                      email: fayers@cardiff.ac.uk
Sun admin/support/programming       phone: 0222 874000 x 5282 (UK)
Newsgroups: comp.sys.sun.admin
From: akonstam@Alex.Engr.Trinity.Edu (aaron konstam)
Newsgroups: comp.sys.sun.admin,info.sun.managers,alt.sys.sun
Subject: (Repeat) Query on fix for bad disk block.
Date: 29 Jul 92 16:18:24 GMT
Distribution: usa
Organization: Trinity University, San Antonio TX. USA

----------------------------------------------
Several weeks ago tried to repair a block on my disk without
having to format the disk and reload the software.
I used the repair option of the format command.
But lo and behold the same block keeps failing again.
This leaves me with the following questions:
1. What does repair actually do?
2. After you repair do you have as a separate operation add
the block to the defect list using defect option of format?
3. The defective block is in the root partition and it must
    be in a program that is used often enough to cause frequent
   failure. What will happen to that program if I add the block to
   the defect list?
4. Is there a way to tell what program includes that block?

-- 
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Aaron Konstam - Computer Science Department
Trinity University , San Antonio, TX 78212
email: akonstam@trinity.edu
Xref: sparky comp.sys.sun.admin:5093 comp.unix.admin:4382 comp.unix.solaris:124
From: gs26@prism.gatech.EDU (Glenn R. Stone)
Newsgroups: comp.sys.sun.admin,comp.unix.admin,comp.unix.solaris
Subject: Re: AT&T vs. BSDI --> 4.3BSD-NET2 distribution requires AT&T license!!!
Keywords: AT&T 'Death Star' rises over BSDI's horizon [Tel. 1-800-800-4BSD
Date: 30 Jul 92 14:48:49 GMT
Reply-To: glenns@eas.gatech.edu
Followup-To: comp.sys.sun.admin
Distribution: usa
Organization: The Group W Bench

In <1992Jul29.193240.434@digibd.com> rhealey@dellr4.digibd.com (Rob Healey) writes:

(edited for brevity, I hope the flavour remains)
>In article <1992Jul21.134305.13151@bnr.uk>, agc@bnr.ca (Alan Carter) writes:
>[Heinlein sez] that it is not the job of the court to ensure the [..] profits
>of large corporations. I hope that this [..] remains, or AT+T['s] [..] size
>will [be] the justification as well as the means for its litigation tactics.

>If AT&T continues on this litigation rather than innovation course then
>maybe it's time for the industry to say "Fine, keep your UNIX(tm),
>we'll go off and buy NT or Mach based systems."

Even better.  Given that UC Regents are being sued, I think the State of
California should drop all AT&T contracts immediately/ASAP.  And perhaps
that other states should follow suit (pun unintentional).  Hit Deathstarco
in their bread and butter and see what happens.  

Given, however, the copyright notice someone else quoted (giving 
Berkeley credit in something distributed by AT&T), methinks
our benighted business behemoth has beshat themselves with 
the present proprietary petition, and will probably perish without
an influx of insight from innovative people with an intolerance
for immovable institutions.  

That's right, Death of AT&T As We Know It predicted.  
Film at 11.

(and good riddance, IMHO.)

Glenn R. Stone (glenns@eas.gatech.edu)
I don't speak for Tech; I wouldn't dream of letting them speak for me.
From: jneher@darkwing.uoregon.edu (Jumpin Jon)
Newsgroups: comp.sys.sun.admin
Subject: Weird automounter messages
Date: 23 Jul 92 23:04:39 GMT
Organization: University of Oregon Network Services

Hello,

Does anyone know what my automounter is complaining about?
Functionality seems just fine but my console is flooded with these
messages:

Jul 23 15:42:24 darkwing automount[5669]: pathok: couldn't find devid 820e(0700) for /tmp_mnt/net/phloem/disk1/network-services
Jul 23 15:42:24 darkwing automount[5669]: pathok: couldn't find devid 820d(0700) for /tmp_mnt/net/phloem/var/spool/news
Jul 23 15:42:24 darkwing automount[5669]: pathok: couldn't find devid 820c(0700) for /tmp_mnt/net/phloem/disk1/config
Jul 23 15:42:24 darkwing automount[5669]: pathok: couldn't find devid 8212(0700) for /tmp_mnt/net/phloem/disk1/home

Any ideas?

thanks,

Jon
Newsgroups: comp.sys.sun.admin
From: hemmer@procyon.cern.ch (Frederic Hemmer ATD10)
Subject: Re: Exabyte 8500 - Dump parameters
Organization: CERN - European Laboratory for Particle Physics
Date: Fri, 31 Jul 1992 12:31:18 GMT

In article <BRTMAC.92Jul27094933@maverick.ksu.ksu.edu>, brtmac@maverick.ksu.ksu.edu (Brett McCoy) writes:
> In article <1992Jul27.084023.22925@ericsson.se> etxorst@eos.ericsson.se (Torsten Lif) writes:
> 
> >>I just got off the phone to our Exabyte drive suppliers technical
> >>department, according to them using /dev/rstn+8 for 5GB density is fine,
> >>as long as the tape is new. If your tape has been used on an Exabyte
> >>8200 unit the new 8500 drive will continue to use the tape as a 2.3 GB
> >>tape.
> >
> >Yes-and-no. Addressing /dev/nrst(n+8) makes no difference on those of
> >our machines that run SunOS 4.1.1, but on this machine (an SS10/41
> >running SunOS 4.1.3-beta) it works as described. I haven't yet had time
> >to try it on 4.1.2 and I don't know if patches for the older OS
> >versions are available. Can anyone else shed some light on this?
> 
> According to the EXB-8500 Users Manual the 8500, when positioned at
> PBOT will write at whichever density you tell it to.  Under SunOS
> 4.1.2 the tape devices /dev/{r,nr}st[0-7] are 8200 format and
> /dev/{r,nr}st[8-15] are 8500 format.  More information is available
> from 'man st'.  If you write to an EXB-8500 anywhere but the beginning
> it will ignore the density setting you tell it and will write at the
> same density the rest of the tape has been written at.
> 
> Under SunOS 4.1.1 and below there is no support for 8500 drives which
> is why it will write 8200 format if the tape was already written.  I
> believe that if you don't tell the drive what to do it assumes that
> you want to use the format that is already on the tape.
> 
> ++Brett;

SunOS 4.1.1 actually can support 8500. It just needs to be helped a little
bit :

on sun3, sun4 architectures modify /sys/sundev/streg.h :
add an entry for 8500 with the low-density flag as first device :

/* Exabyte 8mm 5GB cartridge */ \
{       "Exabyte", 16, "EXABYTE EXB-8500", ST_TYPE_EXABYTE, \
        1024, (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE | ST_PHYSREC), \
        30, 30, 30, 30, 60, 60, 60, 60, \
        0x14, 0x00, 0x00, 0x00,  0, 0, 0, 0 }, \

on sun4c (sun4m must have at least 4.1.2) modify /sys/scsi/targets/st_conf.c
add an entry for 8500 with the low-density flag as first device :

        "Exabyte EXB-8500 8mm Helical Scan", 16, "EXABYTE EXB-8500",
        ST_TYPE_EXB8500, 1024,
        (ST_VARIABLE | ST_BSF | ST_BSR | ST_LONG_ERASE),
        5000, 5000,
        { 0x14, 0x00, 0x00, 0x00 },
        {  0, 0, 0, 0 }

and rebuild kernel. This will then use the 0x14 for rst{n} turning the 8500
in low density. rst{n+8} will be the normal mode. Note that an 8200 will not
accept the 0x14 density flag so this entry will NOT work for 8200.

Frederic.

Frederic Hemmer                          email: hemmer@sun1.cern.ch
European Laboratory for Particle Physics bitnet: hemmer at cernvm
Computers and Networks division          phone: +41-22-7676104
CH-1211 Geneva 23 - Switzerland          fax:   +41-22-7677155
From: jc@raven.bu.edu (James Cameron)
Newsgroups: comp.sys.sun.admin
Subject: How to properly call rcp.yppasswdd.
Date: 28 Jul 92 16:18:13 GMT
Article-I.D.: raven.JC.92Jul28121813
Organization: What do you mean 'That *can't* be done????'


System:  Running SunOS 4.1.1 

Problem: rpc.passwdd does not correctly update NIS information.  I
         recall someone mentioning that there was a bug and you simply
         needed to do somthing trivial.  What might this be?

Thanks for the info!

--
			-- James Cameron  (jc@raven.bu.edu) (617) 353-2879
					  
    System Manager, Signal Processing and Interpretation Lab.  Boston, Mass  
------------------------------------------------------------------------------
"But to risk we must, for the greatest hazard in life is to risk nothing.  For
the man or woman who risks nothing, has nothing, does nothing, is nothing."
	(Quote from the eulogy for the late Christa McAuliffe.)
From: guy@Logibec.COM (Guy Thibault)
Newsgroups: comp.sys.sun.admin
Subject: Help! pac does'nt work
Summary: Help! pac seems to does'nt work !!!
Keywords: pac
Date: 22 Jul 92 17:59:29 GMT
Organization: Logibec Group Ltee


I try to use the command pac and the resuslt is always

  Login               pages/feet   runs    price

total                       0.00    0   $  0.00


and my printcap look like this:


lp7:\
	:lp=/dev/ttyAe:sd=/var/spool/lpd/lp7:\
	:lf=/usr/adm/lpd-errs:\
	:pc#200:af=/var/spool/lpd/lp7/acct:\
	:br#9600:mx#0:rw:sh:\
	:ms=pass8,ixon,crtscts,cread:


Can someone help me for this ?

thanks in advance...


Guy Thibault	g.thibault@logibec.com
LOGIBEC GROUPE INFORMATIQUE
8 PLACE DU COMMERCE, MONTREAL QC.  H3E 1N3
Tel: (514) 766-0134	Fax: (514) 766-9237
-- 
Guy Thibault	g.thibault@logibec.com
LOGIBEC GROUPE INFORMATIQUE
8 PLACE DU COMMERCE, MONTREAL QC.  H3E 1N3
Tel: (514) 766-0134	Fax: (514) 766-9237
Newsgroups: comp.sys.sun.admin,comp.sys.sun.hardware
From: eloranta@jyu.fi (Jussi Eloranta)
Subject: SCSI error messages...
Organization: University of Jyvaskyla, Finland
Date: Fri, 24 Jul 1992 16:30:28 GMT


Does anybody know what these error messages mean?

Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2:    transport rejected
Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2:    transport rejected
Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2:    kluster error- retryings ops singly
Jul 24 17:22:17 tukki.jyu.fi vmunix: sd2:    kluster error- retryings ops singly

I'm using sun-4/670 with on board scsi and scsi II from pti. The drives
are old wrens (connected via pti scsi card). The disks seem to work ok
and fsck complains nothing, but there must be some purpose for these
messages...

jussi
-- 
============================================================================
Jussi Eloranta               Internet(/Bitnet):    ! The ultimate trip is
University of Jyvaskyla,     Jussi.Eloranta@jyu.fi !    death.
Finland                      [130.234.0.1]         !  -- Jim Morrison
Newsgroups: comp.sys.sun.admin,comp.sys.sun.apps,comp.sys.sun.misc
From: shenai@amnese.eng.uab.edu (Aravind K. Shenai)
Subject: Image Processing S/W Info wanted
Originator: shenai@amnese.eng.uab.edu
Reply-To: shenai@amnese.eng.uab.edu
Organization: University of Alabama at Birmingham
Distribution: na
Date: Fri, 31 Jul 1992 16:28:19 GMT

I want to find information about any latest frame-grabber software for 
SUN-SPARCs which would allow to analyze parts of the image.

Sorry if this is an FAQ.

-- 
ARAVIND SHENAI                           | Internet : shenai@amnese.eng.uab.edu
University of Alabama at Birmingham      |
Newsgroups: comp.sys.sun.admin
From: edlee@gandalf.ca (Ed Lee)
Subject: Kernel Config:  UDP window & buffer size
Summary: change?
Keywords: Kernel, UDP
Organization: Gandalf Data Ltd.
Distribution: na
Date: Wed, 22 Jul 1992 20:45:56 GMT

hi there,

I'm new to this group so please excuse me if this question is
common knowledge.

We are trying to run the SUN in a special network configuration.
However, whenever the SUN decides to send a burst of 24 IP packets
(consisting of 4 x 9000 byte UDP packets which we think is 1 UDP
window) this special network will drop half of them.  We are seeing
this during a simple 'cp' command (remote disk to remote disk) and
what should take about 30 seconds to do is taking minutes to hours.

We can see these packets via a 'sniffer' connected in parallel and
we know that they are not getting through.  What we would like to
do is reconfigure the Kernel on the SUN so that the UDP window or
packet size is greatly reduced.

Please reply via e-mail as I don't really read this group.

Thanks in advance
edly

--

C. Edward Lee              CAnet: edlee@gandalf.ca
Gandalf Data Limited       Voice: (613) 723-6500 x 8787
Nepean, Ontario              Fax: (613) 226-1717
Canada  K2E 7M4

Permanently cured from wanting to pitch in baseball!  :-(
Now I just wanna ski!!
From: rcaliari@su5v.ess.harris.com (Richard Caliari)
Newsgroups: comp.sys.sun.admin
Subject: Re: Quick & Dirty Disk Swap
Date: 28 Jul 92 12:20:47 GMT
Organization: Advanced Technology Department, Harris Corporation

Thanks to all who e-mailed me responses. It seems that the tried and
proven method is to partition the new disk appropriately and then
with the original disk as sd0 and the new disk as sd1, mount the
partitions from the new drive in /mnt, or some other mount point,
and then:

/etc/dump 0f - /dev/rsd0a | (cd /mnt; /etc/restore xf -)

Thanks for the info.

-- 
----------------------------------------------------------------------
Rich Caliari
email: rcaliari@su5v.ess.harris.com
Xref: sparky comp.sys.sun.admin:5053 comp.sys.sun.misc:3377
From: ce1zzes@prism.gatech.EDU (Eric Sheppard)
Newsgroups: comp.sys.sun.admin,comp.sys.sun.misc
Subject: Halting/pausing HP7475a plotter
Date: 29 Jul 92 03:34:33 GMT
Followup-To: comp.sys.sun.admin
Organization: Georgia Institute of Technology

We have a couple of HP plotters, a Draftmaster II and a 7475A connected to
a Sun Sparcstation 2.  We have the proper queues set up for each, and they
plot correctly given an appropriate file.  The problem we are facing is 
that when the HP7475 plotter finishes a job, it will not stop.  It will 
continue immediately to the next output job.  The Draftmaster has a special
'NR' (not-ready) code that prevents this; the queue handler sends this
halt-code after each job.  Alas, a thorough examination of the programmer's
manual reveals that the NR command doesn't exist for the 7475.

Is there a simple, elegant way to manage the queue without involving an
operator on the server?  Sticking in a sleeper segment isn't practical;
jobs might arrive when paper is not loaded, jobs that aren't attended
promptly will get overwritten, and overly long delays can take their toll
on users as a dozen jobs remain backed up in the queue.

Looking for a happy medium,
Eric
-- 
Eric Sheppard      Georgia Tech    |   "Of course the US Constitution isn't
Atlanta, GA                        | perfect, but it's a lot better than what
ARPA: ce1zzes@prism.gatech.edu     |             we have now." -Unknown
uucp: ...!{allegra,amd,hplabs,seismo,ut-ngp}!gatech!prism!ce1zzes
From: medley@sun44.synercom.hounix.org (Bert Medley)
Newsgroups: comp.sys.sun.admin
Subject: How do you manage the getty?
Date: 24 Jul 92 20:31:56 GMT
Distribution: na
Organization: Synercom Technology, Inc., Houston, TX

I am a newbie sysadmin responsible for the USENET connection and have two
questions.

1.  How do you reset the getty?  Under ISC you kill the getty process and
    it is restarted by init.

2.  I set up the modem on ttyb as specified by both the Sun doc and the
    TELEBIT set procedures and the getty IS NOT raising DTR after someone
    calls in.  Does this problem ring a bell?


-- 
Bert Medley				medley@synercom.hounix.org 	[work]
					bert@medley.ssdl.com		[home]
Newsgroups: comp.sys.sun.admin
From: gord@jericho.uunet.uu.net (Gord Wait)
Subject: lpd messages ?
Organization: S-MOS Systems, Inc. (Vancouver Design Center)
Date: Thu, 30 Jul 1992 21:37:42 GMT


We have a couple of postscript printers on serial ports on our sun
servers. For the longest time, any printer status messages (like paper
tray empty, or postscript error messages) were being sent to the
console. I made no changes to the log facilities, but the messages
stopped appearing! I have tried to reconfigure the printcap entry,
re-ran lpd with the logfile option, and messed with syslog.conf all to
no avail. It won't send status to a file in var/admin, or to the
console. I also checked the printer port with tip, to make sure the
serial line was OK.

The printers are on a sun 4/300 running 4.1.1

Any clues, or further debug suggestions?
-- 
Gord Wait 	SMOS Systems Vancouver Design Centre
uunet!jericho!gord
jericho!gord@uunet.UU.NET

Newsgroups: comp.sys.sun.admin