Your message dated Tue, 31 Jul 2007 08:11:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line network-manager/if-up.d
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: network-manager
Version: 0.6.4-8+b1
Yo!
Not entirely sure if this is intended behaviour, a bug or just not
implemented yet: I feel that /etc/network/if-up.d scripts etc. should be
executed if network interfaces come up or go down.
Right now, it seems the scripts are never executed - and thus ntp (for
example) isn't restarted when the network goes up.
cheers
-- vbi
--
He who despairs over an event is a coward, but he who holds hopes for
the human condition is a fool.
-- Albert Camus
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Yo!
Investigated this further: ntp's ifup script was conditional on
ADDRFAM=inet, whereas NetworkManager sets ADDRAM=NetworkManager (why?
can't it be set to a real ADDRFAM value like inet, inet6 etc.?)
I was going to reassign this to ntp, but ntp >= testing rescans interfaces
periodically anyway, so sorry about the noise...
cheers
-- vbi
--
featured product: Debian GNU/Linux - http://debian.org
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
