- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- sdlcomp silently catches SIGSEGV and coredumps
Operating System - HP-UX
1752729
Members
5642
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2004 03:52 AM
02-19-2004 03:52 AM
sdlcomp silently catches SIGSEGV and coredumps
Hi,
I've got trouble to create a rudimentary set of DSI logfiles during my first trials.
I used the DSI spec file that you may find attached.
I think its syntax is ok.
First I had used some metric qualifiers that exceeded the 20 char limit.
But now they're all trimmed to the limit.
Instead when I try to compile this happens:
# sdlcomp lola_data4_bydsk.spec lola_data4_diskperf
sdlcomp C.03.72.00 09/29/03.
Check class specification syntax.
class lola_data4 = 200001
index by hour max indexes 168
roll by day
records per hour 30
;
metrics
bydsk_devname = 4000
label "Disk HW Path"
type text length 30
;
bydsk_avg_srv_time = 4001
label "Average Service Time"
precision 2
maximum 1000
;
bydsk_util = 4002
label "% Disk I/O Utilization"
precision 1
maximum 100
;
bydsk_phys_byte_rate = 4003
Memory fault(coredump)
# file core
core: core file from 'sdlcomp' - received SIGSEGV
I've got trouble to create a rudimentary set of DSI logfiles during my first trials.
I used the DSI spec file that you may find attached.
I think its syntax is ok.
First I had used some metric qualifiers that exceeded the 20 char limit.
But now they're all trimmed to the limit.
Instead when I try to compile this happens:
# sdlcomp lola_data4_bydsk.spec lola_data4_diskperf
sdlcomp C.03.72.00 09/29/03.
Check class specification syntax.
class lola_data4 = 200001
index by hour max indexes 168
roll by day
records per hour 30
;
metrics
bydsk_devname = 4000
label "Disk HW Path"
type text length 30
;
bydsk_avg_srv_time = 4001
label "Average Service Time"
precision 2
maximum 1000
;
bydsk_util = 4002
label "% Disk I/O Utilization"
precision 1
maximum 100
;
bydsk_phys_byte_rate = 4003
Memory fault(coredump)
# file core
core: core file from 'sdlcomp' - received SIGSEGV
Madness, thy name is system administration
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP