A client called today after they experienced an episode
of users unable to login to the 5.0.7 system (with MP3).

They were unable to get through to me and so repeatedly
shut the system down and rebooted. During one shutdown,
the system did not respond to the "shutdown -y -g0" command
and they powered it off (big red switch).

They also powered off all the 10/100 switches as well
(some users were unable to get to the Internet, some
users were unable to get a login prompt from UNIX).

When I logged in later in the day and ran authck I see
the following report.


# /tcb/bin/authck -av
Checking defaults
Finding all entries in the Protected Password database hierarchy
Checking Protected Password hierarchy
Checking all entries in the Subsystem database
Checking all entries in the Terminal Control database
Entry 1 in Terminal Control database does not have a name.
in Terminal Control database refers to a non-existent terminal.
#

Any suggestions on the quick way to recreate a corrupted Terminal
control database?

TIA.
--

Steve Fabac
S.M. Fabac & Associates
816/765-1670

Steve M. Fabac, Jr. wrote:
> A client called today after they experienced an episode
> of users unable to login to the 5.0.7 system (with MP3).
>
> They were unable to get through to me and so repeatedly
> shut the system down and rebooted. During one shutdown,
> the system did not respond to the "shutdown -y -g0" command
> and they powered it off (big red switch).
>
> They also powered off all the 10/100 switches as well
> (some users were unable to get to the Internet, some
> users were unable to get a login prompt from UNIX).
>
> When I logged in later in the day and ran authck I see
> the following report.
>
>
> # /tcb/bin/authck -av
> Checking defaults
> Finding all entries in the Protected Password database hierarchy
> Checking Protected Password hierarchy
> Checking all entries in the Subsystem database
> Checking all entries in the Terminal Control database
> Entry 1 in Terminal Control database does not have a name.
> in Terminal Control database refers to a non-existent terminal.
> #
>
> Any suggestions on the quick way to recreate a corrupted Terminal
> control database?
>
> TIA.
> --
>
> Steve Fabac
> S.M. Fabac & Associates
> 816/765-1670

Hi Steve,

THis is a guess, don't really have time to look into this much, but you

might want to try moving /etc/auth/system/ttys out of the way, then run

/tcb/bin/ttyupd

Please proceed with caution. Not sure this fits your sitch.

Regards,
Dan Martin

Steve M. Fabac, Jr. typed (on Thu, Jun 08, 2006 at 09:56:53PM +0000):
| A client called today after they experienced an episode
| of users unable to login to the 5.0.7 system (with MP3).
|
| They were unable to get through to me and so repeatedly
| shut the system down and rebooted. During one shutdown,
| the system did not respond to the "shutdown -y -g0" command
| and they powered it off (big red switch).
|
| They also powered off all the 10/100 switches as well
| (some users were unable to get to the Internet, some
| users were unable to get a login prompt from UNIX).
|
| When I logged in later in the day and ran authck I see
| the following report.
|
|
| # /tcb/bin/authck -av
| Checking defaults
| Finding all entries in the Protected Password database hierarchy
| Checking Protected Password hierarchy
| Checking all entries in the Subsystem database
| Checking all entries in the Terminal Control database
| Entry 1 in Terminal Control database does not have a name.
| in Terminal Control database refers to a non-existent terminal.
| #
|
| Any suggestions on the quick way to recreate a corrupted Terminal
| control database?

See TA 104588.

--
JP
==> http://www.frappr.com/cusm <==

Dan Martin wrote:
>
> Steve M. Fabac, Jr. wrote:
> > A client called today after they experienced an episode
> > of users unable to login to the 5.0.7 system (with MP3).
> >
> > They were unable to get through to me and so repeatedly
> > shut the system down and rebooted. During one shutdown,
> > the system did not respond to the "shutdown -y -g0" command
> > and they powered it off (big red switch).
> >
> > They also powered off all the 10/100 switches as well
> > (some users were unable to get to the Internet, some
> > users were unable to get a login prompt from UNIX).
> >
> > When I logged in later in the day and ran authck I see
> > the following report.
> >
> >
> > # /tcb/bin/authck -av
> > Checking defaults
> > Finding all entries in the Protected Password database hierarchy
> > Checking Protected Password hierarchy
> > Checking all entries in the Subsystem database
> > Checking all entries in the Terminal Control database
> > Entry 1 in Terminal Control database does not have a name.
> > in Terminal Control database refers to a non-existent terminal.
> > #
> >
> > Any suggestions on the quick way to recreate a corrupted Terminal
> > control database?
> >
> > TIA.
> > --
> >
> > Steve Fabac
> > S.M. Fabac & Associates
> > 816/765-1670
>
> Hi Steve,
>
> THis is a guess, don't really have time to look into this much, but you
>
> might want to try moving /etc/auth/system/ttys out of the way, then run
>
> /tcb/bin/ttyupd
>
> Please proceed with caution. Not sure this fits your sitch.
>
> Regards,
> Dan Martin

Thanks Don and JP, TA 104588 did the trick. I logged in after hours
with the system idle and ran the steps listed in the TA:

cd /etc/auth/system

mv ttys /tmp/ttys.bad
(if you just copy it, you need to manually remove ttys)

touch /etc/auth/system/ttys

chown auth:auth /etc/auth/system/ttys

/tcb/bin/ttyupd

/tcb/bin/ale /etc/auth/system/ttys pttyupd

--

Steve Fabac
S.M. Fabac & Associates
816/765-1670