On Mon, Aug 23, 2004 at 12:34:55AM +0200, Dirk Reiss wrote:
> Mattia Dongili wrote:
> >On Sun, Aug 22, 2004 at 04:21:16PM +0200, Dirk Reiss wrote:
[...]
> >well, you can try to launch cpufreqd with increasing verbosity and wait
> >for it to die. Be careful as verbosity=7 is really verbose :)
> >
> > [...]
>
> Hi Mattia,
>
> I ran it now with verbosity=7 and all worked fine, right until now. I
> browsed some logfiles to find a pattern, but unfortunately failed (the
> only thing i noticed was that about half a minute afterwards, gconfd
> started and terminated, other times this was no problem).
gconfd shouldn't be a problem, I have it at home on my desktop PC and
all is working fine.
> Last time it just ran fine for some hours, then it just stopped working :-(
could you try running cpufreqd with:
# (cpufreqd -f /etc/cpufreqd.conf -D -V7 2>&1 > cpufreqd.log) &
# disown
and send me (privately only) cpufreqd.log after it crashes?
> Could it have something to do with the kernel (2.6.8 vanilla)?
I don't think so. It sounds me much more like a leak somewhere as
cpufreqd can start and run for some time. Anyway I didn't actually
tested the latest kernel yet.
Also, I just released cpufreqd-1.2.0, it might be worth a try, I'm
preparing the debian package right now. If you don't want to wait, you
can simply run the configure script with:
./configure --prefix=/usr --sbindir=/usr/sbin --sysconfdir=/etc \
--localstatedir=/var --libdir=/usr/lib/cpufreqd \
--mandir=/usr/share/man
this way it will overwrite the debian package files without leaving
trash around
bye
--
mattia
:wq!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
