1
0
Fork 0

Document where C structures for state file header and job entry come from

This commit is contained in:
Julien Dessaux 2020-01-29 14:27:03 +01:00
parent e6ab5d33da
commit e07ce016c4
2 changed files with 4 additions and 1 deletions

View file

@ -85,3 +85,4 @@ Because of the way we record jobs in a spool file in order to track missing jobs
- start the bareos file daemon again - start the bareos file daemon again
- run any job in order to have the file daemon recreate a valid status file - run any job in order to have the file daemon recreate a valid status file
- delete the line referencing this job in the spool file (/var/lib/bareos/bareos-zabbix-check.spool by default) - delete the line referencing this job in the spool file (/var/lib/bareos/bareos-zabbix-check.spool by default)

View file

@ -11,6 +11,7 @@ import (
) )
// stateFileHeader : A structure to hold the header of the state file. It is statically aligned for amd64 architecture // stateFileHeader : A structure to hold the header of the state file. It is statically aligned for amd64 architecture
// This comes from bareos repository file core/src/lib/bsys.cc:525 and core/src/lib/bsys.cc:652
type stateFileHeader struct { type stateFileHeader struct {
ID [14]byte ID [14]byte
_ int16 _ int16
@ -26,6 +27,7 @@ func (sfh stateFileHeader) String() string {
} }
// jobEntry : A structure to hold a job result from the state file // jobEntry : A structure to hold a job result from the state file
// This comes from bareos repository file core/src/lib/recent_job_results_list.h:29 and file core/src/lib/recent_job_results_list.cc:44
type jobEntry struct { type jobEntry struct {
Pad [16]byte Pad [16]byte
Errors int32 Errors int32