On Sun, 12 Dec 1999, Alvin Jiang wrote:
>Hmm, I just solved this problem last night. It took me all of 5 mins to
>search "psmintr" and find the solution at:
>
>http://www.freebsd.org/FAQ/x.html#AEN2255
>
>You'd probably save a lot of time if you read the FAQ, rather than post and
>wait for a repl
On Sun, 12 Dec 1999, Tom wrote:
!>
!> Setting maxusers to 256 isn't help you any at all, btw.
!>
!>Tom
!>
This is simply untrue.
MAXUSERS directly influences the number of mbufs which, in turn,
influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts
will, in
>clusters - adjust NMBCLUSTERS or increase maxusers!'. I had maxusers at 256
>at that point, and had 'options NMBCLUSTERS=2048' in the kernel as well --
>it still failed.
> I'm hoping that increasing maxusers to 512, and bumping NMBCLUSTERS to 4096
>is going to provide some help, but somehow
>On Sun, 12 Dec 1999, Tom wrote:
>
>!>
>!> Setting maxusers to 256 isn't help you any at all, btw.
>!>
>!>Tom
>!>
>
> This is simply untrue.
>
> MAXUSERS directly influences the number of mbufs which, in turn,
> influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts
In article <[EMAIL PROTECTED]>,
The Unicorn <[EMAIL PROTECTED]> wrote:
>
> Just wondering why I see a *LOT* (as in one for each source file on the
> system) of SetAttrs messages coming over my screen, when I am cvsupping
> 3.3-STABLE on one system I own. While other systems act normall
Hello everyone,
I've just finished cvsup'ing 3.3-stable, to bring my 3.3-Release system up
to date. Everything went fine and seems to be working except for my laser
jet printer. Its a NEC SuperScript 870 which emulates to a HPLJ IIP. The
printer gets recognized fine during bootup and everthin
>>If you're running windows boxen behind your FreeBSD server, then (at least
>>I think) the EASIEST way to solve your problem is to run IRC clients on
>>yoru windows boxen which contain identd servers to themselves. This
>
>This is correct, but doesn't help the actual problem because internal box
>Unfortunately, the suggested remedy only compounded the problem.
>Setting the psm0 flags to 0x100 killed X when the mouse lost sync.
>Running moused and using sysmouse caused extremely eratic behavior.
>Without moused and using /dev/psm0 for X simply froze the mouse --
>although switching to anot
You're not clear about what you're printing, where you're printing it to,
or what the actual output looks like, but these symptoms are entirely
consistent with you trying to print plain text or some other encoding to
the printer. You need to ensure that you're actually printing to the
correc
On Sun, 12 Dec 1999, David Greenman wrote:
!>>On Sun, 12 Dec 1999, Tom wrote:
!>>
!>>!>
!>>!> Setting maxusers to 256 isn't help you any at all, btw.
!>>!>
!>>!>Tom
!>>!>
!>>
!>> This is simply untrue.
!>>
!>> MAXUSERS directly influences the number of mbufs which, in turn,
!>> influenc
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
On Mon, 13 Dec 1999, Kazutaka YOKOTA wrote:
>>Unfortunately, the suggested remedy only compounded the problem.
>>Setting the psm0 flags to 0x100 killed X when the mouse lost sync.
>>Running moused and using sysmouse caused extremely eratic behavior.
>>Without moused and using /dev/psm0 for X simp
subscribe freebsd-stable
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
13 matches
Mail list logo
