summaryrefslogtreecommitdiff
path: root/src/bus-proxyd/synthesize.h
diff options
context:
space:
mode:
authorLennart Poettering <lennart@poettering.net>2015-02-13 15:38:38 +0100
committerLennart Poettering <lennart@poettering.net>2015-02-13 15:49:51 +0100
commit5f6cb091278906423f8b7e70c40131db7269916a (patch)
tree9c482e4cc78b3592b12fde4cbfff66be68ac9ff9 /src/bus-proxyd/synthesize.h
parent1433efd219a6df414a1821b3d3d70d86201ed3e4 (diff)
bus-proxy: whenever we cannot forward a message, report this back to caller, but don't exit
Errors like EPERM from the kernel should certainly not be reason to exit. Let's try to be defensive here, and try to continue on most send errors, but possibly tell the sender about it.
Diffstat (limited to 'src/bus-proxyd/synthesize.h')
-rw-r--r--src/bus-proxyd/synthesize.h4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/bus-proxyd/synthesize.h b/src/bus-proxyd/synthesize.h
index e93e0d34da..a55f171cb2 100644
--- a/src/bus-proxyd/synthesize.h
+++ b/src/bus-proxyd/synthesize.h
@@ -23,10 +23,12 @@
#include "sd-bus.h"
-int synthetic_reply_method_errorf(sd_bus_message *call, const char *name, const char *format, ...);
int synthetic_reply_method_return(sd_bus_message *call, const char *types, ...);
int synthetic_reply_method_return_strv(sd_bus_message *call, char **l);
int synthetic_reply_method_error(sd_bus_message *call, const sd_bus_error *e);
+int synthetic_reply_method_errorf(sd_bus_message *call, const char *name, const char *format, ...) _sd_printf_(3, 4);
int synthetic_reply_method_errno(sd_bus_message *call, int error, const sd_bus_error *p);
+int synthetic_reply_method_errnof(sd_bus_message *call, int error, const char *format, ...) _sd_printf_(3, 4);
+
int synthesize_name_acquired(sd_bus *a, sd_bus *b, sd_bus_message *m);