Re: Ksysguard bsd

I tried on a new system, i built FreeBSD stable, Xfree4 and Kde from the
ports, still can't make the ksysguard work :(

On Thu, 2003-09-04 at 09:32, fBSD KDE wrote:
> Thanks for your reply, in fact it's like i said it's the CPU usage, not
> the average load.
> The average load works well, but when i add the CPU (user, system, nice
> ..etc) it shows zero.
> I tried this on 3 computers with freebsd 4.4 4.7 4.8 and still same
> problem, it didn't work on any system.
> I used to remove the "root checking part" in the source of kde3.0 to
> make it work, but now it doesn't change anything.
> I verified the permissions, the user is in kmem group, the ksysguardd
> file is setguid and it's kmem group
> is there a way to launch ksysguardd manually and send to it a command to
> see where is the problem?
> Thanks again
> 
> On Wed, 2003-09-03 at 19:15, Lauri Watts wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On Wednesday 03 September 2003 09.40, fBSD KDE wrote:
> > > Hi,
> > >   The KSysguard was working well on Freebsd till 3.0.
> > > Now with all the versions till 3.1.3 i can't make it work, the
> > > connection works, i can see the memory usages, the average load but the
> > > CPU is always at 0%.
> > > Any ideas please?
> > 
> > It first occurred to me that your ksysguardd binary was not installed sgid 
> > kmem, but if you can see the memory usage, then it apparently is.  In any 
> > case, could you please check this?
> > 
> > I've tried on several machines, and had several other people try, and we can't 
> > reproduce this - both memory and cpu load monitors work as expected on 
> > various versions both from ports and hand compiled from CVS.
> > 
> > Is it possible you are meaning the process tree itself? There we did discover 
> > a problem, where it is empty, while the same process tree accessed via the 
> > Ctrl-Esc keybinding works fine.  In case I am misunderstanding your problem 
> > and this is what you meant, then yes, it does appear to be broken but I'm a 
> > little surprised to only just notice it.   I will try to find someone to look 
> > into it, and we will report it as a bug if need be.
> > 
> > In any case, please check the file permissions on the ksysguardd binary, and 
> > if it's not already, see if setting it sgid kmem helps (there is information 
> > in the user manual on this matter.)
> > 
> > Regards,
> > - -- 
> > Lauri Watts
> > KDE Documentation: http://i18n.kde.org/doc/
> > KDE on FreeBSD: http://freebsd.kde.org/
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.2.2 (FreeBSD)
> > 
> > iD4DBQE/ViG6/gUyA7PWnacRAgINAJje9Vc/D+lyj+FrmUvQ5QFwFbKbAJ0UYlzI
> > lazLulvYmdeDpsMT+xAoGQ==
> > =bDKP
> > -----END PGP SIGNATURE-----
> 
> _______________________________________________
> kde-nonlinux mailing list
> [email protected]
> http://mail.kde.org/mailman/listinfo/kde-nonlinux