Searched hist:218138 (Results 1 - 9 of 9) sorted by relevance
| /freebsd-9.3-release/sbin/hastd/ | ||
| H A D | proto_common.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | proto_socketpair.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | proto_uds.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | proto.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | subr.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | proto_tcp.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | hastd.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | secondary.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
| H A D | primary.c | diff 218138 Mon Jan 31 16:40:42 MST 2011 pjd - Use pjdlog for assertions and aborts as this will log assert/abort message to syslog if we run in background. - Asserts in proto.c that method we want to call is implemented and remove dummy methods from protocols implementation that are only there to abort the program with nice message. MFC after: 1 week |
Completed in 103 milliseconds