 ../
|
network_stats.c
|
1.68
(20 years ago)
by ats:
Add comparison functions for names where that's likely to be useful.
Make the network_iface_stats example show how to use bsearch to find an
interface by name.
|
|
process_stats.c
|
1.72
(20 years ago)
by ats:
Skip over argv pointers on OpenBSD.
|
|
statgrab.h
|
1.49
(20 years ago)
by ats:
Add comparison functions for names where that's likely to be useful.
Make the network_iface_stats example show how to use bsearch to find an
interface by name.
|
|
error.c
|
1.11
(20 years ago)
by ats:
... and include tools.h to get the definition of sg_strlcpy.
|
|
swap_stats.c
|
1.20
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
|
statgrab_deprecated.c
|
1.2
(20 years ago)
by tdb:
Fix a couple of includes.
|
|
cpu_stats.c
|
1.23
(20 years ago)
by tdb:
Whitespace tidyup - change spaces to tabs.
|
|
Makefile.am
|
1.25
(20 years ago)
by tdb:
Update NEWS file for 0.10 release.
|
|
statgrab_deprecated.h
|
1.1
(20 years ago)
by tdb:
Add compatibility code. This provides a working pre-0.10 API for old
applications. To use simply change the #include line to:
#define SG_ENABLE_DEPRECATED
#include <statgrab.h>
This can be disabled at build time completely using --disable-deprecated.
|
|
memory_stats.c
|
1.27
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
|
tools.h
|
1.24
(20 years ago)
by tdb:
Shift a bunch of parsing functions to be linux/cygwin only. Prompted by
a regex related compile error on FreeBSD (we don't use regex's on FreeBSD).
|
|
vector.h
|
1.7
(20 years ago)
by tdb:
Add header block.
|
|
load_stats.c
|
1.15
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
|
tools.c
|
1.52
(20 years ago)
by tdb:
Shift a bunch of parsing functions to be linux/cygwin only. Prompted by
a regex related compile error on FreeBSD (we don't use regex's on FreeBSD).
|
|
vector.c
|
1.9
(20 years ago)
by tdb:
Whitespace tidyup - change spaces to tabs.
|
|
disk_stats.c
|
1.68
(20 years ago)
by tdb:
Fix bugs in error code.
|
|
os_info.c
|
1.18
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
|
page_stats.c
|
1.21
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
|
user_stats.c
|
1.25
(20 years ago)
by tdb:
The rest of the error handling stuff (except the vector code).
I've been extremely unimaginative with the string names in error.c, but
they're all in one place so much easier to tidy up. I'm also beginning to
wonder if we actually needed an SG_ERROR_SYSTEM_CALL to indicate some call
into the system failed - because the majority of our errors are those :-)
Still to do, then:
- vector code
- better string names in error.c
- deal with arg string in some way
- make use of the error status in statgrab/saidar/examples
|
