On Thu, 2007-12-06 at 18:18 +0100, Nigel Henry wrote:
> I know it's only a workaround, but how about putting the ntp restart
> in /etc/rc.d/rc.local.

There are problems with that approach:

Cleanly handling starting in different run levels, where services may or
may not be running the same as run level 5.

Cleanly turning off services from ever starting using chkconfig or
serviceconf.

--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Tim:
>> Seems a rather bad way to organise the starting order, not having a
>> network ready before services that need to use a network.


Mikkel L. Ellertson:
> I am working on my first cup of coffee, so I may be way off base,
> but isn't NetworkManager designed to manage connections when a user
> logs in?

It's an example of yet another case where network manager is only
suitable for some users. On the other side of the coin - in some cases
you'll need name resolution working, through a DNS server not hosts
file, before you even start X or a window manager. If you have
bookmarks or desktop links to NFS served directories Gnome will take
forever to start up if it cannot access them, if it even will start up.

Sure, it has its uses. But I'd rate it as a poor default configuration.

--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Paul Smith wrote:

Dear All,

I have NTP configured to synchronize with a server at startup, but it
always fails that as reported by F8 during the booting.
Notwithstanding:

# /sbin/service ntpd restart
Shutting down ntpd: [ OK ]
ntpd: Synchronizing with time server: [ OK ]
Starting ntpd: [ OK ]
#

Any ideas?

Thanks in advance,

Paul




I have read through the thread, but I don't see mention of using
NetworkManager to start ntpd for you.


NetworkManager, as has been discussed, was designed to start interfaces
upon user login. This is especially useful for laptops and systems that
get moved around alot and have more than one user account. Thus, users
do not need to allow access to private networks that other users do not
need.


What has not been discussed, is NetworkManagers ability to start any/all
network based services when a user logs in.


This is somewhat similar to domain lofins, if that helps explain it.
Basically, a script, or group of scripts can/will be run when a user
logs in.


These can range from:
service start ntpd
to
mount server:/home/myhome/data /home/myhome/data

These scripts can run as any user, since they are executed as root in
the first place.


To resolve the OPs issue, create two simple scripts. One for startup,
one for stopping ntpd. You can also specify these by interface. For
instance: eth0=wired and eth1=wireless. Perhaps I only want nptd running
when on the wired connection because I use the wireless mostly in an
ad-hoc network, or for wardriving.


Lets assume for these examples that we want ntpd to start every time
NetworManager brings up eth0, and turn it off whenever NetworkManager
turns off eth0.


Add this script (ore make one like it to suit your needs) to the
/etc/NetworkManager/dispatcher.d/ directory.


#!/bin/sh

# scripts in the /etc/NetworkManager/dispatcher.d/ directory
# are called alphabetically and are passed two parameters:
# $1 is the interface name, and $2 is “up� or “down�

if [ "$1" = "eth0" ]
then
if [ "$2" = "up" ]
then
/sbin/service ntpd start
fi
if [ "$2" = "down" ]
then
/sbin/service ntpd stop
fi
fi

I call it ntpd.
# chmod 755 ntpd

Now pull the wired plug, and then plug it back in. ntpd should be running.

It will be most useful using this method to:

# /sbin/chkconfig ntpd off

All services you want NetworkManager to 'manage' need to be set to off
mode based on run level.


Good Luck!



--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Dec 6, 2007 9:45 PM, Phil Meyer <pmeyer@themeyerfarm.com> wrote:
> > I have NTP configured to synchronize with a server at startup, but it
> > always fails that as reported by F8 during the booting.
> > Notwithstanding:
> >
> > # /sbin/service ntpd restart
> > Shutting down ntpd: [ OK ]
> > ntpd: Synchronizing with time server: [ OK ]
> > Starting ntpd: [ OK ]
> > #
> >
> > Any ideas?
> >
> > Thanks in advance,
> >
> > Paul
> >
> >
>
> I have read through the thread, but I don't see mention of using
> NetworkManager to start ntpd for you.
>
> NetworkManager, as has been discussed, was designed to start interfaces
> upon user login. This is especially useful for laptops and systems that
> get moved around alot and have more than one user account. Thus, users
> do not need to allow access to private networks that other users do not
> need.
>
> What has not been discussed, is NetworkManagers ability to start any/all
> network based services when a user logs in.
>
> This is somewhat similar to domain lofins, if that helps explain it.
> Basically, a script, or group of scripts can/will be run when a user
> logs in.
>
> These can range from:
> service start ntpd
> to
> mount server:/home/myhome/data /home/myhome/data
>
> These scripts can run as any user, since they are executed as root in
> the first place.
>
> To resolve the OPs issue, create two simple scripts. One for startup,
> one for stopping ntpd. You can also specify these by interface. For
> instance: eth0=wired and eth1=wireless. Perhaps I only want nptd running
> when on the wired connection because I use the wireless mostly in an
> ad-hoc network, or for wardriving.
>
> Lets assume for these examples that we want ntpd to start every time
> NetworManager brings up eth0, and turn it off whenever NetworkManager
> turns off eth0.
>
> Add this script (ore make one like it to suit your needs) to the
> /etc/NetworkManager/dispatcher.d/ directory.
>
> #!/bin/sh
>
> # scripts in the /etc/NetworkManager/dispatcher.d/ directory
> # are called alphabetically and are passed two parameters:
> # $1 is the interface name, and $2 is "up" or "down"
>
> if [ "$1" = "eth0" ]
> then
> if [ "$2" = "up" ]
> then
> /sbin/service ntpd start
> fi
> if [ "$2" = "down" ]
> then
> /sbin/service ntpd stop
> fi
> fi
>
> I call it ntpd.
> # chmod 755 ntpd
>
> Now pull the wired plug, and then plug it back in. ntpd should be running.
>
> It will be most useful using this method to:
>
> # /sbin/chkconfig ntpd off
>
> All services you want NetworkManager to 'manage' need to be set to off
> mode based on run level.
>
> Good Luck!

Thanks to all for all answers and help. Can this problem be considered
a bug of F8? If yes, in which component should one file the bug at
Bugzilla?

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Thu, 2007-12-06 at 22:46 +0000, Paul Smith wrote:
> On Dec 6, 2007 9:45 PM, Phil Meyer <pmeyer@themeyerfarm.com> wrote:
> > > I have NTP configured to synchronize with a server at startup, but it
> > > always fails that as reported by F8 during the booting.
> > > Notwithstanding:
> > >
> > > # /sbin/service ntpd restart
> > > Shutting down ntpd: [ OK ]
> > > ntpd: Synchronizing with time server: [ OK ]
> > > Starting ntpd: [ OK ]
> > > #
> > >
> > > Any ideas?
> > >
> > > Thanks in advance,
> > >
> > > Paul
> > >
> > >
> >
> > I have read through the thread, but I don't see mention of using
> > NetworkManager to start ntpd for you.
> >
> > NetworkManager, as has been discussed, was designed to start interfaces
> > upon user login. This is especially useful for laptops and systems that
> > get moved around alot and have more than one user account. Thus, users
> > do not need to allow access to private networks that other users do not
> > need.
> >
> > What has not been discussed, is NetworkManagers ability to start any/all
> > network based services when a user logs in.
> >
> > This is somewhat similar to domain lofins, if that helps explain it.
> > Basically, a script, or group of scripts can/will be run when a user
> > logs in.
> >
> > These can range from:
> > service start ntpd
> > to
> > mount server:/home/myhome/data /home/myhome/data
> >
> > These scripts can run as any user, since they are executed as root in
> > the first place.
> >
> > To resolve the OPs issue, create two simple scripts. One for startup,
> > one for stopping ntpd. You can also specify these by interface. For
> > instance: eth0=wired and eth1=wireless. Perhaps I only want nptd running
> > when on the wired connection because I use the wireless mostly in an
> > ad-hoc network, or for wardriving.
> >
> > Lets assume for these examples that we want ntpd to start every time
> > NetworManager brings up eth0, and turn it off whenever NetworkManager
> > turns off eth0.
> >
> > Add this script (ore make one like it to suit your needs) to the
> > /etc/NetworkManager/dispatcher.d/ directory.
> >
> > #!/bin/sh
> >
> > # scripts in the /etc/NetworkManager/dispatcher.d/ directory
> > # are called alphabetically and are passed two parameters:
> > # $1 is the interface name, and $2 is "up" or "down"
> >
> > if [ "$1" = "eth0" ]
> > then
> > if [ "$2" = "up" ]
> > then
> > /sbin/service ntpd start
> > fi
> > if [ "$2" = "down" ]
> > then
> > /sbin/service ntpd stop
> > fi
> > fi
> >
> > I call it ntpd.
> > # chmod 755 ntpd
> >
> > Now pull the wired plug, and then plug it back in. ntpd should be running.
> >
> > It will be most useful using this method to:
> >
> > # /sbin/chkconfig ntpd off
> >
> > All services you want NetworkManager to 'manage' need to be set to off
> > mode based on run level.
> >
> > Good Luck!
>
> Thanks to all for all answers and help. Can this problem be considered
> a bug of F8? If yes, in which component should one file the bug at
> Bugzilla?

It's not really a bug. The problem is that there's two competing
mechanisms for network management. NetworkManager is primarily used
for mobile installations (e.g. laptops and such), whereas the the
normal stuff (/etc/rc.d/rcX.d/S10network) is used for more fixed
locations.

The startup scripts could be modified to see which was the case, but
that'd have to be extended to all services that were dependent on the
network. On my F7 machine, that's at least 31 services (NFS, RPC, ntpd,
iptables, avahi, mail, NIS, lots of stuff).

Alternately, the %post part of the NetworkManager RPM could add entries
to /etc/NetworkManager/dispatcher.d and "chkconfig off" the services. A
utility could also be written that did it (e.g. "nmconfig --enable" or
"nmconfig --disable", possibly with a GUI front end as well).

Perhaps an "enhancement request" filed against NetworkManager in
bugzilla would meet with a favorable response.

----------------------------------------------------------------------
- Rick Stevens, Principal Engineer rstevens@internap.com -
- CDN Systems, Internap, Inc. http://www.internap.com -
- -
- Sarchasm: The gulf between the author of sarcastic wit and the -
- reader...who doesn't get it. -
----------------------------------------------------------------------

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

On Dec 6, 2007 9:45 PM, Phil Meyer <pmeyer@themeyerfarm.com> wrote:
> > I have NTP configured to synchronize with a server at startup, but it
> > always fails that as reported by F8 during the booting.
> > Notwithstanding:
> >
> > # /sbin/service ntpd restart
> > Shutting down ntpd: [ OK ]
> > ntpd: Synchronizing with time server: [ OK ]
> > Starting ntpd: [ OK ]
> > #
> >
> > Any ideas?
> >
> > Thanks in advance,
> >
> > Paul
> >
> >
>
> I have read through the thread, but I don't see mention of using
> NetworkManager to start ntpd for you.
>
> NetworkManager, as has been discussed, was designed to start interfaces
> upon user login. This is especially useful for laptops and systems that
> get moved around alot and have more than one user account. Thus, users
> do not need to allow access to private networks that other users do not
> need.
>
> What has not been discussed, is NetworkManagers ability to start any/all
> network based services when a user logs in.
>
> This is somewhat similar to domain lofins, if that helps explain it.
> Basically, a script, or group of scripts can/will be run when a user
> logs in.
>
> These can range from:
> service start ntpd
> to
> mount server:/home/myhome/data /home/myhome/data
>
> These scripts can run as any user, since they are executed as root in
> the first place.
>
> To resolve the OPs issue, create two simple scripts. One for startup,
> one for stopping ntpd. You can also specify these by interface. For
> instance: eth0=wired and eth1=wireless. Perhaps I only want nptd running
> when on the wired connection because I use the wireless mostly in an
> ad-hoc network, or for wardriving.
>
> Lets assume for these examples that we want ntpd to start every time
> NetworManager brings up eth0, and turn it off whenever NetworkManager
> turns off eth0.
>
> Add this script (ore make one like it to suit your needs) to the
> /etc/NetworkManager/dispatcher.d/ directory.
>
> #!/bin/sh
>
> # scripts in the /etc/NetworkManager/dispatcher.d/ directory
> # are called alphabetically and are passed two parameters:
> # $1 is the interface name, and $2 is "up" or "down"
>
> if [ "$1" = "eth0" ]
> then
> if [ "$2" = "up" ]
> then
> /sbin/service ntpd start
> fi
> if [ "$2" = "down" ]
> then
> /sbin/service ntpd stop
> fi
> fi
>
> I call it ntpd.
> # chmod 755 ntpd
>
> Now pull the wired plug, and then plug it back in. ntpd should be running.
>
> It will be most useful using this method to:
>
> # /sbin/chkconfig ntpd off
>
> All services you want NetworkManager to 'manage' need to be set to off
> mode based on run level.

Thanks, Phil, for your help.

I have just placed your script (that I also name as 'ntpd')

-----------------------
#!/bin/sh

# scripts in the /etc/NetworkManager/dispatcher.d/ directory
# are called alphabetically and are passed two parameters:
# $1 is the interface name, and $2 is "up" or "down"

if [ "$1" = "eth0" ]
then
if [ "$2" = "up" ]
then
/sbin/service ntpd start
fi
if [ "$2" = "down" ]
then
/sbin/service ntpd stop
fi
fi
-----------------------

in /etc/NetworkManager/dispatcher.d/. Moreover, I did the following:

chmod 755 ntpd
/sbin/chkconfig ntpd off

but, after a reboot, I get nothing with

# ps -A | grep ntpd
#

So, I suspect that ntpd was not called by the script.

Any ideas?

Paul

--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list