Your message dated Thu, 16 Apr 2009 15:14:37 +0100
with message-id <[email protected]>
and subject line Re: Bug#524359: nis fails to start if there is no master (case
install a master)
has caused the Debian Bug report #524359,
regarding nis fails to start if there is no master (case install a master)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
524359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524359
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nis
Version: 3.17-17
Severity: normal
When installing nis on lenny, debconf only asks for the nis domain,
auto-starting the service after install fails if there is no master.
This is just the case when setting up the master right now.
suggestion: let debconf ask the role (master,slave or client)
best regards
Stefan Pampel
-- System Information:
Debian Release: 5.0.1
APT prefers gutsy
APT policy: (500, 'gutsy'), (500, 'testing'), (500, 'stable'), (10,
'experimental'), (10, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.28.4-vs2.3.0.36.7 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Thu, Apr 16, 2009 at 03:56:46PM +0200, Stefan Pampel wrote:
> When installing nis on lenny, debconf only asks for the nis domain,
> auto-starting the service after install fails if there is no master.
> This is just the case when setting up the master right now.
That's not the case; ypbind starts up perfectly fine and the init script
completes sucessfully. All that happens is that the init script will
wait for a while (about 10s) for for a binding but once the timeout
expires it just carries on.
> suggestion: let debconf ask the role (master,slave or client)
This is not really feasable - a system may be both a master/slave and a
client and setting up as a client involves making system-specific
changes to critical files like /etc/passwd which are far too risky to do
as part of package installation, especially given the need to support
reconfiguring the package.
--- End Message ---
