Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!disgorge.news.demon.net!demon!dispatch.news.demon.net!demon!slugvine.demon.co.uk!slugvine.demon.co.uk!jas
From: jas@slugvine.demon.co.uk (John Stark)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: xload error
Date: Wed, 7 May 1997 23:18:17 GMT
Organization: Home
Message-ID: <E9u3EH.ru@slugvine.demon.co.uk>
References: <336D54EA.1F6E@socs.uts.edu.au> <k0gik5.i1l.ln@dolphin.neosoft.com>
NNTP-Posting-Host: slugvine.demon.co.uk
X-NNTP-Posting-Host: slugvine.demon.co.uk
Lines: 19
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:40671
In article <k0gik5.i1l.ln@dolphin.neosoft.com>,
Conrad Sabatier <conrads@neosoft.com> wrote:
>
>In article <336D54EA.1F6E@socs.uts.edu.au>,
> Martin Gisch <mgisch@socs.uts.edu.au> writes:
>>
>> When my X-windows server starts up it gives this error:
>> xload: can't open kvm files (plus a bunch of high ascii characters)
>> What are kvm files?
>
>You need to make xload a member of the same group as /dev/{mem,kmem} and
>make it "set group ID" as well.
When I tried allowing xload to access these devices, the result was that
the PC rebooted every time I started X. So I took xload out of .fvwm95rc.
Does anyone know the answer to this problem?
--
John Stark (at home), Cambridge, UK | mailto:jas@slugvine.demon.co.uk
Tel. Cambridge (01223) 573555 | http://www.slugvine.demon.co.uk