I had this problem once with 6.1 and fixed it by editing a config file,
access.conf for Apache I think. Now it's reappeared by I wasn't
modifying Apache. There is a log file generated as I remember that
captures an error message from linuxconf, I just don't remember which
one, nor where it's located.
Mike W
"Mikkel L. Ellertson" wrote:
>
> On Mon, 26 Jun 2000, Danny wrote:
>
> > Segment Fault is do to faulty hardwware.
> >
> > Have you tried swapping your RAM to test if your problem has gone away?
> >
> >
> > On Sun, 25 Jun 2000, Mike W wrote:
> > > I know someone explained this before but I lost the email. I'm getting a
> > > segmentation fault when I try to run linuxconf. Where do I find which
> > > configuration file is the problem?
> > >
> > > Thanks,
> > > Mike W
> > >
> > >
> Actualy, Segment Faults are usualy caused by faulty programs. In the
> case of Linux Config, it is usualy cause by a missing config file that
> it tries to open. I think it is missing a check for the value returned
> my an open statment someware, and it assumes the file pointer returned
> is valid. When it tries to access the file, it tries to read memory
> that doesn't belong to it, and Segment Faults. Linux Config Segfaulting
> when a config file is missing it a known problem.
>
> Mikkel
> --
>
> Do not meddle in the affairs of dragons,
> for you are crunchy and taste good with ketchup.
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
