[comp.unix.sysv386] "Can't find database" error on SCO UNIX

gt2186a@prism.gatech.EDU (COBIA,FRANK NAYLOR) (04/03/91)

    I use a computer running SCO UNIX when I am at home (not away at school).
The computer, on a seemingly random basis, will not let anyone log on because
it "Can not find database for this terminal" (not the exact message). When 
the support agreement was still valid, I reported it to SCO. They admitted
that it was a bug in the security software that shows up on systems with a
large number of logins (we have 7 modems with people login in and out a lot).
They said that the /etc/auth/system/ttys file was being corrupted. We found
a way to fix it when someone calls complaining that they can not get into the
system. This is unacceptable for two reasons: 1) We don't want paying customers
to have to call and complain. 2) Unless the console already has someone
logged on, we can't get in either. 

    We got a small magazine from SCO (do not remember the name) that suggeted 
to us that a bug fix had been made available on their BBS. When we follow the
procedure in the magazine for logging on the BBS, we get to a prompt that says
"Shere=sosco", but then it seems to lockup.

    When I called Tech Help, they said they had never used the BBS and 
therefore they could help me. They also refused to talk to me about the 
problem with being payed $100, even though we had reported the problem
during the 30-day free period. I do not think that we should have to pay
$100 to get a bug fix for a product that we payed more than $1000 for.

    Can someone please help me?

Thanks
Frank

-- 
COBIA,FRANK NAYLOR
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp:     ...!{allegra,amd,hplabs,ut-ngp}!gatech!prism!gt2186a
Internet: gt2186a@prism.gatech.edu

lerman@stpstn.UUCP (Ken Lerman) (04/04/91)

In article <25437@hydra.gatech.EDU> gt2186a@prism.gatech.EDU (COBIA,FRANK NAYLOR) writes:
>
[...some details deleted...]
>
>    When I called Tech Help, they said they had never used the BBS and 
>therefore they could help me. They also refused to talk to me about the 
>problem with being payed $100, even though we had reported the problem
>during the 30-day free period. I do not think that we should have to pay
>$100 to get a bug fix for a product that we payed more than $1000 for.
>
[...]



In general, in situations of this type, try talking to the sales
department.  I was recently upgraded to the 3.2.2 development system
for free.  I had reported a bug which was fixed in that system and
complained that I shouldn't have to pay for an upgrade just to have a
bug in the original fixed.  I was sent the disks for 3.2.2, but not
the manuals.  (That way, their cost was relatively small.)

Ken