Date: Mon, 22 Nov 1999 16:27:59 +0200 From: Sheldon Hearn <sheldonh@uunet.co.za> To: mideyon <leoric@fastlane.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: many questions Message-ID: <77556.943280879@axl.noc.iafrica.com> In-Reply-To: Your message of "Sun, 21 Nov 1999 15:51:24 CST." <3838695C.5048CB01@fastlane.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 21 Nov 1999 15:51:24 CST, mideyon wrote: > The first time i startup the ppp program after a reboot i always get the > error Warning: Add! route failed: 0.0.0.0: errno: Disc quota exceeded. > Why does it do this? Dunno, but you could investigate with the quot(1) utility, which displays the disk space occupied by each user. This, of course, assumes that the software isn't giving you a sensible error message. While that's always possible, start by assuming that the error messages are useful. :-) See the quot(1) manual page for more details: man quot > Also whenever i try to su to root on an Eterm i get this error load: > 0.29 cmd: su 298 [ttyin] 0.00u 0.00s 0% 640k. I was to concerned at > first until i started up freebsd and when i got to the console and > tried to type i got garbled text and after i hit enter a couple of > time got a similar error to the one above. Anyone know what this > means? Okay, that's two different questions. :-) As far as the [ttyin] issue is concerned, I can't remember how this situation comes into play, but I do know that the bottom line is that your Eterm is configured for a screwy status command. Usually, the status display is produced when you press Ctrl-T. This condition is obviously different in your environment. Try one of these in your .profile: stty status ^T or stty nokerninfo The first tries to reset the status key to the more conventional Ctrl-T. The second disables the printing of status information completely. I must admit, this weirdness seems exclusive to Eterm. As to the garbling of input at a login(1) prompt, it's a known issue. It seems that this behaviour gets tickled when you press keys at unexpected times during the bootstrapping process. At this stage, the only useful advice I can offer is "don't do that". :-) > Also i noticed that when i use ssh2 it calls the ssh1 binary. Is it > suppoed to use ssh1 or does it have a binary of its own? SSH also tries > to initalize itself two times at boot. What files might i need to edit > to keep it from doing this twice? It looks to me like you have both ssh2 and ssh installed on your machine. You don't need both, since ssh2 is supposed to be backward compatible with ssh. I'd suggest that you pkg_delete both and install ssh2. This assumes that you _must_ have ssh2. If you don't need ssh2, just use ssh (or even openssh). In this particular case, the higher version number is no assurance of a better product. ;-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77556.943280879>