Hello
I am using Fedora 19 and systemd in it is 204 I guess. The issue is
present in there. The following is whatmy unit file is
cat /usr/lib/systemd/system/Myservice.service
[Unit]
Description=This is a test service
[Service]
#PIDFile=/var/run/Myservice.pid
#ExecStartPre=/tmp/one_start_pr
When I fired up F20 on one of my laptops here I noticed that inputattach
doesn't work anymore for serial Wacom devices. It used to be started through
udev, but that doesn't work anymore. So moving to a systemd service it is,
but I'd like a review of the changes please.
The goal is to start inputat
Today I am giving my presentation about systemd/journald for a not very
enthusiastic public. I would like some last answers on a ‘few’ questions.
I understood that you could let systemd start-up the services sequential
for debugging purposes. How is that done?
Is it possible to change the lim
Kernel install doesn't need the second argument on his command line when
removing.
This is correctly documented in the man page.
Signed-off-by: Sébastien Luttringer
---
src/kernel-install/kernel-install | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/kernel-install/kernel
On Wed, Dec 4, 2013 at 10:42 PM, Thomas H.P. Andersen wrote:
> Does this paragraph in the README still make sense?
>
> Note that D-Bus can link against libsystemd-login.so, which
> results in a cyclic build dependency. To accommodate for
> this, please build D-Bus without systemd first, then build
Does this paragraph in the README still make sense?
Note that D-Bus can link against libsystemd-login.so, which
results in a cyclic build dependency. To accommodate for
this, please build D-Bus without systemd first, then build
systemd, then rebuild D-Bus with systemd support.
git send-email is sadly still not working for me. I am pasting the
patch here and attaching it as well.
In busname_trigger_notify the last check uses IS_SET on the
busname's state but compares it to service states.
I assume that the intended logic was to check the service's
state instead.
---
sr
On Wed, Dec 4, 2013 at 1:17 AM, Sascha Kattelmann wrote:
> Whats the status of this bug?
I personally think it would be best to:
(1) Keep the current behavior of sd_journal_seek_tail() +
sd_journal_previous_skip()
(2) Update the docs to reflect that usage
(3) Fix sd_journal_seek_tail() to set
On Wed, Dec 4, 2013 at 4:26 PM, János Illés wrote:
> I did not find a bug tracker for gummiboot, sorry if this is not the
> right place for this.
>
> I would like to report a small cosmetic bug for gummiboot. It looks like this:
> http://i.imgur.com/cDRwIwX.jpg [62 kbyte]
>
> This is laptop with a
Hi!
I did not find a bug tracker for gummiboot, sorry if this is not the
right place for this.
I would like to report a small cosmetic bug for gummiboot. It looks like this:
http://i.imgur.com/cDRwIwX.jpg [62 kbyte]
This is laptop with an intel haswell chipset with full hd display.
--
János
__
This patch makes it possible to set extended attributes on files created
by tmpfiles. This can be especially used to set SMACK security labels on
volatile files and directories.
It is done by adding new line of type "t". Such line should contain
attributes in Argument field, using following format
ENXIO, ESRCH and EADDRNOTAVAIL are also returned by ioctl(KDBUS_CMD_MSG_SEND)
when we have unicast signal messages (signals with a DESTINATION field).
---
src/libsystemd-bus/bus-kernel.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/libsystemd-bus/bus-kernel.c b/src/l
Hi,
I'm working on Fedora 19 with systemd 204. I had trouble with the
journald-API
regarding the seek_tail function. The bug is already described here:
https://bugs.freedesktop.org/show_bug.cgi?id=64614
Here is one more related post:
https://bugzilla.redhat.com/show_bug.cgi?id=979487
On 12/04/2013 09:13 AM, Yin Kangkai wrote:
> On 2013-12-04, 08:49 +0100, Daniel Mack wrote:
>>> Actually, I have a stupid question, do we have any particular reason
>>> to use "part/PART"? giving the fact that we already have term "item"
>>> everywhere in the code...
>>>
>>> struct kdbus_item, item
On 2013-12-04, 08:49 +0100, Daniel Mack wrote:
> > Actually, I have a stupid question, do we have any particular reason
> > to use "part/PART"? giving the fact that we already have term "item"
> > everywhere in the code...
> >
> > struct kdbus_item, items, kdbus_msg.items...
> >
> > My opinion, o
15 matches
Mail list logo