On Wed, Apr 07, 2010 at 06:16:39PM -0700, Rick Stevens wrote:
> On 04/07/2010 06:03 PM, Paul W. Frields wrote:
> > On Wed, Apr 07, 2010 at 01:34:35PM -0700, Rick Stevens wrote:
> >> On 04/07/2010 10:51 AM, Tom H wrote:
> >>> I've never found a need to reboot on changing hostnames. The most
> >
On Wed, Apr 7, 2010 at 4:34 PM, Rick Stevens wrote:
> On 04/07/2010 10:51 AM, Tom H wrote:
>> I've never found a need to reboot on changing hostnames. The most
>> drastic action I've taken was to "service network restart".
>>
> One wold assumme if yo are using 'service network start'
On Wed, Apr 7, 2010 at 4:22 PM, Paul W. Frields wrote:
> On Wed, Apr 07, 2010 at 01:51:37PM -0400, Tom H wrote:
>> There is a "NM_CONTROLLED" variable that can be set in the ifcfg-*
>> scripts to use one or the other (although I do not see where my F13
>> init.d scripts check for its value.)
> II
On 04/07/2010 06:03 PM, Paul W. Frields wrote:
> On Wed, Apr 07, 2010 at 01:34:35PM -0700, Rick Stevens wrote:
>> On 04/07/2010 10:51 AM, Tom H wrote:
>>> I've never found a need to reboot on changing hostnames. The most
>>> drastic action I've taken was to "service network restart".
>>>
>
On Wed, Apr 07, 2010 at 01:34:35PM -0700, Rick Stevens wrote:
> On 04/07/2010 10:51 AM, Tom H wrote:
> > I've never found a need to reboot on changing hostnames. The most
> > drastic action I've taken was to "service network restart".
> >
> One wold assumme if yo are using 'service ne
On 04/08/2010 08:02 AM, Rick Stevens wrote:
> On 04/07/2010 03:59 PM, Ed Greshko wrote:
>
>>
>> Bottom line One can use "service network restart" when using NM if
>> one wants to. One can also use "service NetworkManager restart". If
>> anything I choose to use the former since network is
On 04/07/2010 03:59 PM, Ed Greshko wrote:
> On 04/08/2010 05:36 AM, Aaron Konstam wrote:
>> On Wed, 2010-04-07 at 17:38 +0800, Ed Greshko wrote:
>>
>>> On 04/07/2010 05:34 PM, Ed Greshko wrote:
>>>
On 04/07/2010 05:28 PM, Aaron Konstam wrote:
> On Wed, 2010-04-07 at 11:11 +0800,
On 7 April 2010 23:59, Ed Greshko wrote:
> Bottom line One can use "service network restart" when using NM if
> one wants to. One can also use "service NetworkManager restart". If
> anything I choose to use the former since network is 7 keystrokes and
> NetworkManager 14 plus it involves th
On 04/08/2010 05:36 AM, Aaron Konstam wrote:
> On Wed, 2010-04-07 at 17:38 +0800, Ed Greshko wrote:
>
>> On 04/07/2010 05:34 PM, Ed Greshko wrote:
>>
>>> On 04/07/2010 05:28 PM, Aaron Konstam wrote:
>>>
>>>
On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
On Wed, 2010-04-07 at 17:38 +0800, Ed Greshko wrote:
> On 04/07/2010 05:34 PM, Ed Greshko wrote:
> > On 04/07/2010 05:28 PM, Aaron Konstam wrote:
> >
> >> On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
> >>
> >>
> >>> I've never found a need to reboot on changing hostnames. The
On 04/07/2010 10:51 AM, Tom H wrote:
> I've never found a need to reboot on changing hostnames. The most
> drastic action I've taken was to "service network restart".
>
One wold assumme if yo are using 'service network start' you are not
using NM so your comments about the changi
On Wed, Apr 07, 2010 at 01:51:37PM -0400, Tom H wrote:
> I've never found a need to reboot on changing hostnames. The most
> drastic action I've taken was to "service network restart".
>
> >>> One wold assumme if yo are using 'service network start' you are not
> >>> using NM so your co
I've never found a need to reboot on changing hostnames. The most
drastic action I've taken was to "service network restart".
>>> One wold assumme if yo are using 'service network start' you are not
>>> using NM so your comments about the changing hostname may not apply to
>>> the OP's
On Wed, 2010-04-07 at 17:34 +0800, Ed Greshko wrote:
> On 04/07/2010 05:28 PM, Aaron Konstam wrote:
> > On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
> >
> >>
> >> I've never found a need to reboot on changing hostnames. The most
> >> drastic action I've taken was to "service network re
On 04/07/2010 05:34 PM, Ed Greshko wrote:
> On 04/07/2010 05:28 PM, Aaron Konstam wrote:
>
>> On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
>>
>>
>>> I've never found a need to reboot on changing hostnames. The most
>>> drastic action I've taken was to "service network restart".
On 04/07/2010 05:28 PM, Aaron Konstam wrote:
> On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
>
>>
>> I've never found a need to reboot on changing hostnames. The most
>> drastic action I've taken was to "service network restart".
>>
> One wold assumme if yo are using 'service netwo
On Wed, 2010-04-07 at 11:11 +0800, Ed Greshko wrote:
> >
> > On 04/06/2010 05:52 PM, Ed Greshko wrote:
> >
> >>> On Tue, 2010-04-06 at 23:47 +0800, Ed Greshko wrote:
> >>>
> >>>
> I believe Patrick may have missed the part about your using
> "system-control-network"...if that i
>
> On 04/06/2010 05:52 PM, Ed Greshko wrote:
>
>>> On Tue, 2010-04-06 at 23:47 +0800, Ed Greshko wrote:
>>>
>>>
I believe Patrick may have missed the part about your using
"system-control-network"...if that is of any value.
>>> Not really, given that he didn't say
On 04/06/2010 05:52 PM, Ed Greshko wrote:
>>
>> On Tue, 2010-04-06 at 23:47 +0800, Ed Greshko wrote:
>>
>>> I believe Patrick may have missed the part about your using
>>> "system-control-network"...if that is of any value.
>> Not really, given that he didn't say he was using s-c-n but something
>>
>
> On Tue, 2010-04-06 at 23:47 +0800, Ed Greshko wrote:
>
>> I believe Patrick may have missed the part about your using
>> "system-control-network"...if that is of any value.
> Not really, given that he didn't say he was using s-c-n but something
> called the "network control applet" in Gnom
On Tue, 2010-04-06 at 23:47 +0800, Ed Greshko wrote:
> I believe Patrick may have missed the part about your using
> "system-control-network"...if that is of any value. :-)
Not really, given that he didn't say he was using s-c-n but something
called the "network control applet" in Gnome. Since I
> As far as I know ::1 is only valid as a local address for ipv6.
> You need the ip_address of the machine in the hosts file.
>
>
> --
> ===
> There Is No Cabal.
> ==
On Tue, 2010-04-06 at 16:20 +0100, Michael Thompson wrote:
> On 06/04/2010 16:05, Patrick O'Callaghan wrote:
> > On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrote:
> >
> >> When I change the hostname on my fedora 12 box, from the installation
> >> default of localhost.localdomain, the n
On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrote:
> When I change the hostname on my fedora 12 box, from the installation
> default of localhost.localdomain, the network dies until it is reset back.
>
> I'm changing the hostname by the Network control applet in Gnome, and
> have checked
On 04/06/2010 09:51 AM, Michael Thompson wrote:
> When I change the hostname on my fedora 12 box, from the installation
> default of localhost.localdomain, the network dies until it is reset back.
>
> I'm changing the hostname by the Network control applet in Gnome, and
> have checked that /etc/s
>
> "On 10:51:14 am Michael Thompson said"
>
>> When I change the hostname on my fedora 12 box, from the installation
>> default of localhost.localdomain, the network dies until it is reset back.
>>
>> I'm changing the hostname by the Network control applet in Gnome, and
>> have checked that /e
"On 10:51:14 am Michael Thompson said"
> When I change the hostname on my fedora 12 box, from the installation
> default of localhost.localdomain, the network dies until it is reset back.
>
> I'm changing the hostname by the Network control applet in Gnome, and
> have checked that /etc/sysconfig/n
>
> When I change the hostname on my fedora 12 box, from the installation
> default of localhost.localdomain, the network dies until it is reset back.
>
> I'm changing the hostname by the Network control applet in Gnome, and
> have checked that /etc/sysconfig/network and it lists the following
>
>
On Tue, 2010-04-06 at 16:40 +0100, Michael Thompson wrote:
> On 06/04/10 16:30, Marvin Kosmal wrote:
> > OK
> >
> > I don't think anyone thinks you are stupid...
> >
> > Just people trying to be helpful..
> >
> > Every time I post.. I get great answers and help.
> >
> > YMMV
> >
> > Marvin
>
On Tue, 2010-04-06 at 16:20 +0100, Michael Thompson wrote:
> On 06/04/2010 16:05, Patrick O'Callaghan wrote:
> > On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrote:
> >
> >> When I change the hostname on my fedora 12 box, from the installation
> >> default of localhost.localdomain, the ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/10 16:30, Marvin Kosmal wrote:
> OK
>
> I don't think anyone thinks you are stupid...
>
> Just people trying to be helpful..
>
> Every time I post.. I get great answers and help.
>
> YMMV
>
> Marvin
:)
Guess I should of put a smillie o
OK
I don't think anyone thinks you are stupid...
Just people trying to be helpful..
Every time I post.. I get great answers and help.
YMMV
Marvin
On 4/6/10, Michael Thompson wrote:
> On 06/04/2010 16:05, Patrick O'Callaghan wrote:
>> On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrot
On 06/04/2010 16:05, Patrick O'Callaghan wrote:
> On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrote:
>
>> When I change the hostname on my fedora 12 box, from the installation
>> default of localhost.localdomain, the network dies until it is reset
>> back.
>>
> "localhost" is assume
On Tue, 2010-04-06 at 15:51 +0100, Michael Thompson wrote:
> When I change the hostname on my fedora 12 box, from the installation
> default of localhost.localdomain, the network dies until it is reset
> back.
"localhost" is assumed always to exist and to be bound to 127.0.0.1 (see
http://en.wikip
When I change the hostname on my fedora 12 box, from the installation
default of localhost.localdomain, the network dies until it is reset back.
I'm changing the hostname by the Network control applet in Gnome, and
have checked that /etc/sysconfig/network and it lists the following
NETWORKING=yes
35 matches
Mail list logo
