|
Revision tags: release/12.2.0, release/11.4.0, release/12.1.0, release/11.3.0, release/12.0.0, release/11.2.0 |
|
| #
4fc0a279 |
| 17-Feb-2018 |
Mariusz Zaborski <[email protected]> |
Introduce channel flags in libcasper.
Instead of passing flags (which describe a type of nvlist)
every send/recv we remember them in channel.
It's enough for use to extract them only during unwrap.
Introduce channel flags in libcasper.
Instead of passing flags (which describe a type of nvlist)
every send/recv we remember them in channel.
It's enough for use to extract them only during unwrap.
This simplify use of Casper.
Reviewed by: bruffer@, bcr@ (both man page)
Differential Revision: https://reviews.freebsd.org/D14196 (man page)
show more ...
|
| #
5869a5d8 |
| 29-Jan-2018 |
Mariusz Zaborski <[email protected]> |
The name of the library is exactly the same like one of name the name of the
functions.
We should not create MLINKS for that one, because it's break a build.
Submitted by: lwhsu@
|
| #
eca37937 |
| 29-Jan-2018 |
Mariusz Zaborski <[email protected]> |
Document the syslog Casper service.
Reviewed by: bcr@
Differential Revision: https://reviews.freebsd.org/D14084
|
| #
7b4fce76 |
| 12-Nov-2017 |
Mariusz Zaborski <[email protected]> |
Introduce syslog service for Casper.
syslog in libc secretly reconnects to the daemon.
Another issue is that we don't have any information from openlog(3) if we
succeeded to open log or not so we do
Introduce syslog service for Casper.
syslog in libc secretly reconnects to the daemon.
Another issue is that we don't have any information from openlog(3) if we
succeeded to open log or not so we don't know if we are ready
to enter cabability mode.
Because all of that we decided we need a syslog service for Caspser.
Reviewed by: bapt@
Differential Revision: https://reviews.freebsd.org/D12824
show more ...
|