Hello,
I am trying to send a signal using sdbus but I am not able to see anything
on my dbus-monitor command:
dbus-monitor "type='signal',interface='test.signal.Type'"
code:
sd_bus_error error = SD_BUS_ERROR_NULL;
sd_bus_message *m = NULL;
sd_bus *bus = NULL;
int r;
r = sd_bus_open_user();
if (r
On Mo, 15.07.19 13:55, Salman Ahmed (salman@gmail.com) wrote:
> Hello,
> I am trying to send a signal using sdbus but I am not able to see anything
> on my dbus-monitor command:
> dbus-monitor "type='signal',interface='test.signal.Type'"
>
> code:
> sd_bus_error error = SD_BUS_ERROR_NULL;
>
I have a simple example of a service unit and bash script on rhel7 using
Type=notify that I was trying to get working. When the service unit is
configured to start the script as root things work as expected. When adding
User=testuser it fails. While the script initially starts (as seen on
I apologize if this was already answered. My company might have blocked
the response.
I have a simple example of a service unit and bash script on rhel7 using
Type=notify that I was trying to get working. When the service unit is
configured to start the script as root things work as expected.
Hi,
Is there an directory/list of available portable services?
With kind regards
Thomas
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
This is still a problem with systemd-242-5.git7a6d834.fc31.x86_64
If I boot using 'systemd.journald.forward_to_console=1
console=ttyS0,38400 console=tty1 systemd.log_level=debug rd.debug
rd.udev.debug'
There is no debug output forwarded to console, only kernel messages
and normal systemd logging
On Mon, Jul 15, 2019 at 2:32 PM Chris Murphy wrote:
>
> If I boot using 'systemd.log_level=debug rd.debug rd.udev.debug
> systemd.log_target=kmsg log_buf_len=64M printk.devkmsg=on'
Another data point. Is kmsg dumped into a file is 5MiB, after the
point in time when journald had done vacuuming on
