Prev: More live years with SLES?
Next: Parallel threads from a gnome-terminal
From: Kevin Miller on 23 Feb 2010 12:55
JT wrote:
> On 23/02/10 07:01, Ruben Safir wrote:
>> Can someone explain this to me?
>>
>> [ 46.159094] eth1: link up, 10Mbps, half-duplex, lpa 0x0000
>> [ 46.793780] ip_tables: (C) 2000-2006 Netfilter Core Team
>> [ 46.895748] nf_conntrack version 0.5.0 (16099 buckets, 64396 max)
>> [ 46.895911] CONFIG_NF_CT_ACCT is deprecated and will be removed soon.
>> Please use
>> [ 46.895920] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack
>> module option or
>> [ 46.895927] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
>>
>>
>> Ruben
>>
> Urrr, it's a dump of Linux bringing up your network interface and
> telling you what to change to be future-proof. Heck, even the command to
> do so is in there.....
>
> Serious: what's your question?

Although the commands are given, it doesn't say where to use them. At
the cli? Parameter in /boot/grub/menu.lst? Some file in the
/etc/modprobe.d tree? Which one?

Which one would be the preferred approach? Are they all equally likely
to survive a reboot or upgrade?

....Kevin
--
Kevin Miller
Juneau, Alaska
http://www.alaska.net/~atftb
In a recent poll, seven out of ten hard drives preferred Linux.
From: JT on 23 Feb 2010 13:04
On 23/02/10 18:55, Kevin Miller wrote:
> JT wrote:
>> On 23/02/10 07:01, Ruben Safir wrote:
>>> Can someone explain this to me?
>>>
>>> [ 46.159094] eth1: link up, 10Mbps, half-duplex, lpa 0x0000
>>> [ 46.793780] ip_tables: (C) 2000-2006 Netfilter Core Team
>>> [ 46.895748] nf_conntrack version 0.5.0 (16099 buckets, 64396 max)
>>> [ 46.895911] CONFIG_NF_CT_ACCT is deprecated and will be removed
>>> soon. Please use
>>> [ 46.895920] nf_conntrack.acct=1 kernel parameter, acct=1
>>> nf_conntrack module option or
>>> [ 46.895927] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
>>>
>>>
>>> Ruben
>>>
>> Urrr, it's a dump of Linux bringing up your network interface and
>> telling you what to change to be future-proof. Heck, even the command to
>> do so is in there.....
>>
>> Serious: what's your question?
>
> Although the commands are given, it doesn't say where to use them. At
> the cli? Parameter in /boot/grub/menu.lst? Some file in the
> /etc/modprobe.d tree? Which one?
>
> Which one would be the preferred approach? Are they all equally
> likely to survive a reboot or upgrade?
>
> ...Kevin
Use the 'sysctl ' (etc!) cmd in a cli as root (via 'sudo' if needed).
Good luck!

--
Kind regards, JT

From: J G Miller on 23 Feb 2010 16:18
On Tue, 23 Feb 2010 12:56:09 +0100, JT wrote:

> I don't do cups.

Are you still on BSD lpr system?
From: JT on 24 Feb 2010 02:21
On 23/02/10 22:18, J G Miller wrote:
> On Tue, 23 Feb 2010 12:56:09 +0100, JT wrote:
>
>
>> I don't do cups.
>>
> Are you still on BSD lpr system?
>
If you read the rest of the message, instead of just this snippet, you
might see a 'joke' in there. Refer to a dictionary for a description of
the concept ;-)

--
Kind regards, JT

First  |  Prev  | 
Pages: 1 2
Prev: More live years with SLES?
Next: Parallel threads from a gnome-terminal