NIO CommKit Host Interface Installation and System Administration Manual

DKDAEMON(1M) DKDAEMON(1M)
E-24 CommKit Host Interface, Release 4.0
dkhsopen: ERROR DKGETMODCHAN, Device errno=Code
Error Code was detected when dkdaemon tried to determine the identity of a newly clone-opened
Device during the service of an I_LINK request from one of its client subsystems.
Prog: Started, Log Level = verbosity
Written to the log file during dkdaemon startup as a record of the session logging verbosity.
Prog: UNKNOWN SIGNAL – Value
A signal with integer value Value was received unexpectedly. See signal(2).
Prog: SIGHUP
The dkdaemon process received a SIGHUP signal that will cause a full re-initialization of all client
subsystems.
Prog: WARNING Termination Requested
dkdaemon received a SIGTERM request to stop and will honor the request by exiting.
Prog: Exiting
This message is logged immediately before dkdaemon exits normally.
genstart: ERROR open(Device), errno=Code
Error Code was returned when dkdaemon tried to open Device as an administrative daemon device.
get_msg: getmsg vdatlen Length, ERROR errno = Code
A getmsg(2) system call returned error Code unexpectedly. A subsystem client request message with
up to Length bytes of variable length data had been expected.
get_msg: ERROR bad len Got, SB Length
A message of length Got was received when dkdaemon expected to receive a protocol message of
size Length. A service ERROR should follow that identifies the client driver that sent the improperly
formatted message.
send_msg: ERROR putmsg type = Type vdatlen Length, errno = Code
Error Code was returned when dkdaemon attempted to send response type Type with variable
length data of size Length.
parse: ERROR Name Unit interface bad cmd, type Type vdatlen Length
An unrecognized command with a type Type was received from interface interface of subsystem
client Name. The request included Length bytes of variable length data. This is likely caused by a
software error in the driver described by Name.
parse: ERROR Name Unit interface vdata missing, type Type vdatlen Length
A request of type Type from subsystem client Name unit interface did not include the required
variable length data buffer. This is likely caused by a software error in the driver described by Name.
parse: ERROR Name, Unit interface bad fixed vdata size, type Type vdatlen Got, SB Length
A request of type Type from subsystem client Name unit interface included a variable length data
buffer of Got bytes but Length bytes were expected. This is likely caused by a software error or a
temporary resource exhaustion in the driver described by Name.
parse: ERROR Name Unit interface unexpected vdata type Type vdatlen Length
A request of type Type from subsystem client Name unit interface included a variable length data
buffer when none was expected. This is likely caused by a software error in the driver described by
Name.
parse: Name Unit interface Handler type Type returned RetVal
The Handler for type Type client messages returned a failure (with value RetVal) while servicing a
request for Name unit interface. This message should be preceded by one or more ERROR messages
from the failed Handler.