package bareos.core

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

service Core

bareos.proto:9

enum BareosFlagVariable

bareos.proto:287

Used in: GetFlagRequest, SetFlagRequest

enum BareosIntVariable

bareos.proto:260

Used in: GetIntRequest, SetIntRequest

enum BareosStringVariable

bareos.proto:229

Used in: GetStringRequest, SetStringRequest

enum EventType

bareos.proto:37

Used in: RegisterRequest, UnregisterRequest

enum JMsgType

bareos.proto:185

* Most of these message levels are more or less obvious. They have evolved somewhat during the development of BAREOS, and here are some of the details of where I am trying to head (in the process of changing the code) as of 15 June 2002. JMSG_ABORT BAREOS immediately aborts and tries to produce a traceback This is for really serious errors like segmentation fault. JMSG_ERROR_TERM BAREOS immediately terminates but no dump. This is for "obvious" serious errors like daemon already running or cannot open critical file, ... where a dump is not wanted. JMSG_TERM BAREOS daemon shutting down because of request (SIGTERM). JMSG_DEBUG Debug Messages The remaining apply to Jobs rather than the daemon. JMSG_FATAL BAREOS detected a fatal Job error. The Job will be killed, but BAREOS continues running. JMSG_ERROR BAREOS detected a Job error. The Job will continue running but the termination status will be error. JMSG_WARNING Job warning message. JMSG_INFO Job information message. JMSG_SAVED Info on saved file JMSG_NOTSAVED Info on not saved file JMSG_RESTORED An ls -l of each restored file. JMSG_SKIPPED File skipped during backup by option setting JMSG_SECURITY For security viloations. This is equivalent to FATAL. JMSG_ALERT For Tape Alert messages. JMSG_VOLMGMT Volume Management message JMSG_AUDIT Auditing message JMSG_MOUNT Mount requests

Used in: JobMessageRequest