Am Mittwoch, den 02.02.2005, 11:35 -0500 schrieb Jason Vas Dias:
I couldn't manage to let the program write a configuration file at all. It always crashes with a python traceback when I instruct it to save the configuration (I've to figure out weather I entered something wrong into one of the entry fields or the program crashes by itself - so no bugzilla entry yet).
Yes, this is a known problem with system-config-bind < 4 .
Use the latest system-config-bind:
ftp://download.fedora.redhat.com/pub/fedora/linux/core/development/i386/Fedora/RPMS/system-config-bind-4.0.0-3.noarch.rpm
and you should have no problems.
I did that from the X64_86 tree (fully update Core 3 x86_64 system):
------------------------------------------------------------------- [root@shuttle fedora-updates]# rpm -U system-config- bind-4.0.0-3.noarch.rpm Warnung: /etc/pam.d/bindconf saved as /etc/pam.d/bindconf.rpmsave Warnung: /etc/security/console.apps/bindconf saved as /etc/security/console.apps /bindconf.rpmsave /var/tmp/rpm-tmp.13899: line 11: fg: no job control Fehler: %post(system-config-bind-4.0.0-3.noarch) scriptlet failed, exit status 1 -------------------------------------------------------------------
rpm -q reports both versions being installed (2.0.3-1 and 4.0.0-3) and system-config-bind doesn't even start anymore :-)
------------------------------------------------------------------- [pb@shuttle ~]$ system-config-bind Traceback (most recent call last): File "/usr/sbin/system-config-bind", line 37, in ? from BIND import * File "/usr/share/system-config-bind/BIND.py", line 12, in ? import Lookup File "/usr/share/system-config-bind/Lookup.py", line 16, in ? from Hosts import Hosts File "/usr/share/system-config-bind/Hosts.py", line 12, in ? from Conf import * ImportError: No module named Conf -------------------------------------------------------------------
Is version 4 meant to work with stock Core 3?
Peter