Dear Andrei,
I very much wish I could find out how to get tigervncserver to start without
abandoning the failed configuration and moving to a higher display number.
Since the fourth quarter of 2014, I have installed (including reinstalls) 12
servers working as hypervisors. The problem happened
Hi, all
If some message went into bus-wqueue, and failed to run
ioctl(KDBUS_CMD_SEND) and returned r 0,
I found that this message will remain in the bus-wqueue. If the peer is
killed for some reason, this message will fail to be sent and remain in the
wqueu for ever.
Because in
2015-08-07 17:18 GMT+08:00 eshark eshar...@163.com:
Hi, all
If some message went into bus-wqueue, and failed to run
ioctl(KDBUS_CMD_SEND) and returned r 0,
I found that this message will remain in the bus-wqueue. If the peer is
killed for some reason, this message will fail to be
Hi all.
The journal format offers powerful filter capabilities. Unfortunately this power
is lost, if you have to use grep to find certain information.
Example given (unscientific benchmark), count the number of entries for a
(known) executable:
$ journalctl --disk-usage
Archived and
I think you should look into forwarding your logs to a more sophisticated
aggregator, like the ELK stack.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
