Is device polling enabled?
- M
On Thu, Nov 9, 2017 at 12:17 PM, Lev Serebryakov wrote:
>
> I still have problems with my E-1220v3 server equipped with Intel I210
> adapter. It can not be loaded more than 100Mbit/s because it is
> connection to internet.
>
> But sometimes
You need to change /etc/ttys to turn off the virtual consoles and turn
on a serial terminal.
E.g.,
ttyv0 /usr/libexec/getty Pc xterm off secure
# Virtual terminals
ttyv1 /usr/libexec/getty Pc xterm off secure
ttyv2 /usr/libexec/getty Pc xterm off secure
ttyv3
Brian T. Schellenberger wrote:
OTOH, the fact that nobody seems to have noticed until after 4.9 was released
is a pretty strong argument that not very many people care--unless of
course :-)
Ag! It was a stupid fscking idea to make
arbitrary changes to something that hadn't really
Forgive the top-post -- I have independently verified this,
suggest you open a PR. This is definitely a bug in opiepasswd.
It is also present in RELENG_4_8.
Regards, Michael
Sergey Sysoev wrote:
Hi. I have a question related to freebsd opie implementation.
I am running 4.9-RELEASE and I've
Artur Pydo wrote:
pipe 1 config bw 125Kbit/s queue 10
pipe 2 config bw 125Kbit/s queue 10
queue 10 config queue 16kByte weight 100 pipe 1 mask all
queue 11 config queue 24kByte weight 1 pipe 1 gred 0.02/3/6/0.06
queue 20 config queue 16kByte weight 100 pipe 2 mask all
queue 21 config queue
Tom Rhodes wrote:
Due to legal issues, qmail was not added to the selection. Sorry.
What legal issues? It seems entirely possible to produce a license-compliant
var-qmail package for FreeBSD. It would be nice to offer it as the default
MTA.
___
Gerald Combs wrote:
This message was created automatically by mail delivery software (TMDA).
Even TMDA has shit for brains!
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to
Dag-Erling Smorgrav wrote:
Interference is preventing the card from transmitting, causing packets
to accumulate in the outgoing queue.
Dummynet queues with RED might help -- changing the behavior from tail
dropping to early detection may improve performance.
To Unsubscribe: send mail to
David Magda wrote:
Evren Yurtesen [EMAIL PROTECTED] writes:
I wonder how come wi driver doesnt let me to set mtu higher than 1500
even though I know the card supports it?
Because the maximum size of the data poriton in a frame for 10Mbit
and 100Mbit Ethernet is 1500.
That makes no sense
What's the deal with this? This puppy broke a couple of my
machines by overwriting /var/qmail/bin/sendmail via the
symlink in /usr/sbin. Ack. Pppt.
There should be a single switch to disable sendwhale.
I'll reiterate that the make.conf switches are no substitute
for packagizing the
Richard Caley wrote:
Basicly, you can't have somethign which is stable and which gets fixed
quickly, the two aims are in opposition.
Something which gets fixed quickly is one definition of stability --
the addition of new features is its opposite. Deciding when a
proposed change is defect
Doesn't seem to be able to find the jre (/usr/local/jdk1.3.1/jre).
Solutions?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
Christopher Vance wrote:
And in case you didn't notice, timezones have nothing to do with
security - you should be using NTP and UTC for everything that is tied
to security.
Back to school for you.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of
Andrew Reilly wrote:
I ran a script using jot to send ping packets across the link, with
sizes varying from 1300 to 2300 bytes, while also watching the link with
tcpdump.
Only one ping failed (it didn't even get out), with the following error
message:
ping: sendto: Message too long
I
R. David Murray wrote:
On Mon, 6 May 2002, Ian wrote:
What changed is that the code now enforces that you do it the right way,
which is to use 255.255.255.255 as the netmask for the alias IPs. That is,
use the normal/proper netmask for the primary IP for that NIC, then use
255.255.255.255 for
Mike Meyer wrote:
Well, I handle my own mail, and *I* certainly got it. I even chmod'ed
/usr/bin/keyinit to close the known hole this bug created.
This just occurred to me -- it isn't possible that this is being
routed through an MTA whose A and PTR records don't match, is it?
To
Mike Meyer wrote:
Well, I handle my own mail, and *I* certainly got it. I even chmod'ed
/usr/bin/keyinit to close the known hole this bug created.
I handle my own mail and didn't receive it. Isn't in the mailing
list archive, either.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
Dave Hayes wrote:
Nasrudin was driving a friend in his car at a spanking
pace. Suddenly, glimpsing a signpost, the friend called out
Mulla, we're going in the wrong direction!
Why don't you ever think of something good? came the
reply. Just look, for instance, at the speed we are going at.
Peter Schultz wrote:
At system boot I see this message twice:
Starting final network daemons:rpc.umntall: 10.0.0.103: RPCPROG_MNT:
RPC: Port mapper failure - RPC: Unable to send
That's normal -- your pccard stuff probably hasn't settled down yet, but
you've got nfs compiled into the kernel
Nate Williams wrote:
See above. It can easily be done in a more standard way. (One can
argue that the '-z' should be the default flag, but so far I've failed
to convince Warner of this fact. :) :)
Forgive me if I'm mistaken, but the pccard_ether script (when last I
looked at
Michael Sierchio wrote:
Nate Williams wrote:
See above. It can easily be done in a more standard way. (One can
argue that the '-z' should be the default flag, but so far I've failed
to convince Warner of this fact. :) :)
Forgive me if I'm mistaken, but the pccard_ether
Stoian Mishinev wrote:
I have strange problem, about mount or 2 ago I've tried 2 aironet cards
on the same machine running FreeBSD one to our wireless network and the
other to my home network with success.
How do you define success? Having two transceivers in immediate proximity is
22 matches
Mail list logo