Clement wrote:
>
> You are genius. Linuxconf failed when it open a file "included" in the
> named.conf. It looks like linuxconf simply do not know how to take care
> of that.
No, I'm not a genius, I'm a fool. It's evidenced by some of my past
posts. I did nothing more than show you the way t
You are genius. Linuxconf failed when it open a file "included" in the
named.conf. It looks like linuxconf simply do not know how to take care
of that.
Gordon Messmer wrote:
>
> Clement wrote:
> > In preparing a new Redhat 6.1 machine, the linuxconf worked well in the
> > first place. However
xconf core dumps
Clement wrote:
> In preparing a new Redhat 6.1 machine, the linuxconf worked well in the
> first place. However, after installing other applications, apache,
> samba, etc, the linuxconf is now giving me core dumps only!
I've seen that happen when linuxconf isn&
Clement wrote:
> In preparing a new Redhat 6.1 machine, the linuxconf worked well in the
> first place. However, after installing other applications, apache,
> samba, etc, the linuxconf is now giving me core dumps only!
I've seen that happen when linuxconf isn't able to correctly parse a
config
Hi,
In preparing a new Redhat 6.1 machine, the linuxconf worked well in the
first place. However, after installing other applications, apache,
samba, etc, the linuxconf is now giving me core dumps only! Removing
and re-installing linuxconf will only give me the first info screen,
then core dump
