3455d025a22f08389c2135f7757c166e64c6643c
2000-01-23 Martin Baulig <martin@home-of-linux.org> This is now a LibGTop backend which can be loaded additionally to the normal Linux sysdeps code. * open.c, close.c: Removed. * shm_limits.c, msg_limits.c, sem_limits.c, ppp.c: Removed. * siglist.c, sysinfo.c: Removed. * backend-kernel.c: New file. * glibtop-backend-private.h: New file. * libgtop-kernel.backend: New file. * backend-kernel.pl: New file. Automatically creates `backend-kernel.h'. * marshal.pl: New file. Automatically creates `marshal.c'. * glibtop_server.h: Replaced all `GLIBTOP_SUID_<feature>' constants with `GLIBTOP_IMPL_<feature>' ones; they're used in marshal.c to find out which features this backend implements. * *.c: Renamed all `glibtop_get_<feature>_s' functions to `glibtop_get_<feature>_k' and all `glibtop_init_<feature>_s' ones to `glibtop_init_<feature>_k'.
This is the *development* branch of LibGTop. It is indended for people who want to help with the development of LibGTop and not for end-users. Please use the LIBGTOP_STABLE_1_0 branch (which is LibGTop 1.0.x) unless you're really a developer. If you're using LibGTop from CVS simply do a cvs update -r LIBGTOP_STABLE_1_0 to get the latest version from the stable branch. However, I'll periodically make snapshot releases from the development branch for Solaris users of LibGTop. They can be found at ftp://ftp.home-of-linux.org/pub/libgtop/1.1/ in near future. Using released tarballs from the development branch is a lot better than compiling directly from CVS since things in CVS may not always work as expected. Note that releases from the developer branch are neither binary nor fully source compatible; you'll normally have to recompile everything that use them. October 1999 Martin Baulig
Description
Languages
C
87.9%
Shell
6.9%
M4
2.7%
Makefile
1.1%
Perl
0.9%
Other
0.5%