Bug#404131: nis: NIS client broken on AMD64

2007-01-03 Thread Nelson A. de Oliveira
Hi! On 12/23/06, Mark Brown [EMAIL PROTECTED] wrote: Could you please reinstall network-manager as it was before, make sure that ypbind is still misbehaving, and then run the command nm-tool for me? This will tell me exactly what network-manager is telling NIS: it may be possible for NIS to

Bug#404131: nis: NIS client broken on AMD64

2007-01-03 Thread Nelson A. de Oliveira
On 1/3/07, Mark Brown [EMAIL PROTECTED] wrote: On Wed, Jan 03, 2007 at 03:33:17PM -0200, Nelson A. de Oliveira wrote: It's saying about eth1 but my primary interface is eth0... (I have both eth0 and eth1, but eth1 is not configured) From where do it gets this interface? (I am feeling that I

Bug#404131: nis: NIS client broken on AMD64

2007-01-03 Thread Mark Brown
On Wed, Jan 03, 2007 at 03:33:17PM -0200, Nelson A. de Oliveira wrote: It's saying about eth1 but my primary interface is eth0... (I have both eth0 and eth1, but eth1 is not configured) From where do it gets this interface? (I am feeling that I will receive another You should read the

Bug#404131: nis: NIS client broken on AMD64

2007-01-03 Thread Mark Brown
On Wed, Jan 03, 2007 at 04:41:44PM -0200, Nelson A. de Oliveira wrote: Shouldn't NetworkManager pass the configured eth0 interface to nis, so it can works properly here? It's a completely orthogonal network configuration system offering configuration via a GUI with dynamic detection of which

Bug#404131: nis: NIS client broken on AMD64

2006-12-28 Thread Nelson A. de Oliveira
Hi! On 12/23/06, Mark Brown [EMAIL PROTECTED] wrote: On Fri, Dec 22, 2006 at 02:56:39PM -0200, Nelson A. de Oliveira wrote: heard about network-manager. It could at least be documented somewhere this new behavior of nis+network-manager. It is documented in the ypbind documentation, although

Bug#404131: nis: NIS client broken on AMD64

2006-12-23 Thread Mark Brown
On Fri, Dec 22, 2006 at 02:56:39PM -0200, Nelson A. de Oliveira wrote: heard about network-manager. It could at least be documented somewhere this new behavior of nis+network-manager. It is documented in the ypbind documentation, although obviously you'd need to know to loook at that. Could

Bug#404131: nis: NIS client broken on AMD64

2006-12-22 Thread Mark Brown
On Thu, Dec 21, 2006 at 11:35:53PM -0200, Nelson A. de Oliveira wrote: 5103: NetworkManager is running. 5103: Are offline 5103: interface: org.freedesktop.DBus, object path: /org/freedesktop/DBus, method: NameAcquired This is the problem. Newer versions of ypbind introduce support for

Bug#404131: nis: NIS client broken on AMD64

2006-12-22 Thread Nelson A. de Oliveira
Hi Mark! On 12/22/06, Mark Brown [EMAIL PROTECTED] wrote: Are you using Network Manger to configure the network interfaces on this system? Is Network Manager present or in use on your i386 etch systems? Sincerely, it's the first time that I am seeing this Network Manager :-) What I did was

Bug#404131: nis: NIS client broken on AMD64

2006-12-21 Thread Nelson A. de Oliveira
Package: nis Version: 3.17-2 Severity: important Hi! Yesterday we have received here a nice new computer (with 2 dual core Xeon), installed Debian Etch for amd64 (everything went fine), etc. But trying to configure NIS (client) on it was disappointing. We have verified every configuration,

Bug#404131: nis: NIS client broken on AMD64

2006-12-21 Thread Mark Brown
On Thu, Dec 21, 2006 at 07:31:08PM -0200, Nelson A. de Oliveira wrote: trying to configure NIS (client) on it was disappointing. It would be helpful if you could describe in more detail what problems you were seeing: what steps did you take when trying to install the package and what output was

Bug#404131: nis: NIS client broken on AMD64

2006-12-21 Thread Nelson A. de Oliveira
Hi! On 12/21/06, Mark Brown [EMAIL PROTECTED] wrote: On Thu, Dec 21, 2006 at 07:31:08PM -0200, Nelson A. de Oliveira wrote: trying to configure NIS (client) on it was disappointing. It would be helpful if you could describe in more detail what problems you were seeing: what steps did you