Search results for query: *

There is not -t on the ttys file. What would i be looking for anyway?

What am I looking for?

Can you give me a hint as to why this system is acting strange. It takes forever to get a login prompt via telnet or on the console, if at all. I have to press the off button, then turn it on and let it boot up. It is okay for a while but then starts hanging again. Please remind me how to...

I have looked at the aplawrence posts and tried them It will not reconize the /mnt/bin/chroot /mnt I have also tried the type tools at the boot prompt but with no success. It seems to me that the floppy disettes do not have every thing on them that I need.

We are in Northern California. I am trying to get a hold of someone in another office where the CD's are stored to see if there is a bootable CD. After that I quess I will need a GURU. This was all installed back east and shipped here but I will call and ask about the BTLDs.

I do have the install media so I guess we will have to do that. But I tried both /mnt/bin/chroot and /mnt/usr/bin/chroot and neither of them worked. In the meantime there are 2 terminals that are disabled so far. Glad it is the end of the week! when I cd to the /mnt directory I see the...

No I do not, this is the only one around. Is it the boot disk that is the probelm maybe? If it is I might be able to get another one from the people that installed it.

Last evening I got a little farther than before. I used: mount /dev/root mnt and that seemed to work. I could not use: mount /dev/hd0root /mnt as it could not find hf0root. When I tried the line /mnt/bin/chroot etc it came back and said it could not be found. Also it does not understand any...

No I have not because it asks for the root password. Is there another way?

Well I really have a problem don't I?! I tried several things. There is no "tools" as referred to in faq58-1366. I could not get to the hard drive. It says too many attemts at mount, or no space left on device, error 28. I could not mount /dev/hd0root /mnt. When I did an ls -l I did find...

It seems that now the account is enabled as it booted up without the message that root was disabled. In the boot from emergency disk process there was an error message when I put the root disk in. It said there was no room on mnt and whatever else. So I shut it down again and let it boot...

The root account has become disabled so I want to boot from the emergency boot disk but the question or problem is as follows: The boot disk was created in 2001 when the system was delivered. I was not instructed to make any as we go like I should have been doing all along. In the mean time...

I looked at the troubleshooting section for the error message and did what it suggested, stop and start both the NIC agent and the SMUX manager. That has not worked. Have you any more suggestions? There has to be something causing this. Thanks

I do not know the version of Management Agents, is there any way to query that in the system? I did a google search but using the whole string, did not work. I just tried 'cmanicd'. I did get an idea that it might have something to do with the 2 NIC cards. But I have no idea what or why

I just became aware of a file that is growing on the system and when I clear it out is sits at zero for 15 to 20 seconds, then comes back a little bigger than it was. When I 'more' the message and go to the end the following appears: Nov 28 08:51:27 SCO_SV cmanicd[929]: cmanicd: Couldn't get...

Thank you, that works. I just didn't know because it had the 'c' in front of it, hadn't done one like that before.

I need to chnage the mode on the tape drive. Currently it is: crw-rw---- I want it to be: crw-rw-rw- Thank you

I was doing a modification to the network manager and it said it had to relink the kernal. Does it do a shutdown when this happens? It has been so long since I had to do anything like this that I have forgotten. If it requires a shutdown then I must warn everyone. Thank you!

I found the culprit!! Someone had sent a huge job to a printer and built a big file in: /var/spool/lps/lp08. I removed that and we are going again. Thanks for your quick responses.

The reason I figured it was on /dev is because of the message above. Could this be a large file resulting from a print job? The printers stopped working first. I cannot get the find command to work that you gave me. Any more ideas, and I sure appreciate your help.