| SD_BUS_MESSAGE_COPY(3) | sd_bus_message_copy | SD_BUS_MESSAGE_COPY(3) |
.SH "NAME" sd_bus_message_copy - Copy the contents of one message
to another
.SH "SYNOPSIS"
#include <systemd/sd-bus.h>
.HP 576u int sd_bus_message_copy(sd_bus_message *m,
sd_bus_message *source,
int all);
.SH "DESCRIPTION"
.PP sd_bus_message_copy() copies the contents from message
source to m. If all is false, a single complete type is
copied (basic or container). If all is true, the contents are copied
until the end of the currently open container or the end of
source.
.SH "RETURN VALUE"
.PP On success, this call returns true if anything was copied, and false if
there was nothing to copy. On failure, it returns a negative errno-style
error code.
.SS "Errors"
.PP Returned errors may indicate the following problems:
.PP -EINVAL
source or m are NULL.
.RE
.PP -EPERM
Message m has been sealed or source has not been
sealed.
.RE
.PP -ESTALE
Destination message is in invalid state.
.RE
.PP -ENXIO
Destination message cannot be appended to.
.RE
.PP -ENOMEM
Memory allocation failed.
.RE
.SH "NOTES"
.PP Functions described here are available as a shared library, which can be
compiled against and linked to with the
libsystemd pkg-config(1) file.
.PP All functions listed here are thread-agnostic and only a single thread
may operate on a given object at any given time. Different threads may
access the same object at different times. Multiple independent objects may
be used from different threads in parallel.
.PP The code described here uses getenv(3), which is declared to be
not multi-thread-safe. This means that the code calling the functions
described here must not call setenv(3) from a parallel thread. It is
recommended to only do calls to setenv() from an early phase of the
program when no other threads have been started.
.SH "SEE ALSO"
| systemd 262.2 |