As far as I know, systemd still officially retains compatibility with
initscripts. Unfortunately, session management now at least partially
broke it.
Any initscript that is using su - would create logind session; this
session will persist until processes started by initscript are runing.
On
On Thu, Dec 18, 2014 at 7:00 AM, Spencer Baugh sba...@catern.com wrote:
When printing the status of a unit, open a connection to the session bus
and query PackageKit for the package that the unit file belongs
to. Print it if PackageKit knows.
Searching packages database may be quite time
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a connection to the session bus
and query PackageKit for the package that the unit file belongs
to. Print it if PackageKit knows.
There are gazillion package manager in the wild and this will
significantly
there's more — synapse actually can create that .desktop file for you, just
tick start automatically checkbox in program preferences
On Thu, Dec 18, 2014 at 7:14 AM, jenia.ivlev jenia.iv...@gmail.com wrote:
That's really nice information. Thanks a lot Mantas.
Hi,
You could maybe think of adding some Package= ou SourcePackage=
attribute in units to let users
known where this unit came from.
This would work like SourcePath= does for generated units.
Alexandre Detiste
2014-12-18 10:08 GMT+01:00 Jóhann B. Guðmundsson johan...@gmail.com:
On 12/18/2014
On 12/18/2014 09:24 AM, Alexandre Detiste wrote:
Hi,
You could maybe think of adding some Package= ou SourcePackage=
attribute in units to let users
known where this unit came from.
This would work like SourcePath= does for generated units.
No this is not very smart to do in general from my
Hi Johann,
Also, note that VlanId is optional. It makes more sense for switch ports.
Regarding my “em1” (Ethernet management) interface, probably I should have send
an example without VLANId.
And “BridgeFDB”s are in the .network following the logic of routes.
To be clear look at the outputs
On Wed, Dec 17, 2014 at 08:04:38PM +0100, Lennart Poettering wrote:
This is important details, because if you use epoll file descriptor
in another epoll then you're correctly notified on the top-level epoll,
but you lost information about which underneath file descriptor is active
--
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts do that?
In Debian, our init scripts would typically use start-stop-daemon
--chuid whateveruser --start
Simon McVittie simon.mcvit...@collabora.co.uk writes:
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts do that?
More to the point, why would an
On 18/12/14 14:10, Dale R. Worley wrote:
Simon McVittie simon.mcvit...@collabora.co.uk writes:
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts do
Am 18.12.2014 um 15:10 schrieb Dale R. Worley:
Simon McVittie simon.mcvit...@collabora.co.uk writes:
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts
Hi all,
When the system is configured to read the RTC time in the local time zone,
some timestamps recorded by systemd are wrong.
This bug can be demonstrated as the following:
(RTC is in UTC+08:00)
$ last
hch tty1 Wed Nov 19 15:39 still logged in
reboot system
2014-12-18 13:19 GMT+01:00 Simon McVittie simon.mcvit...@collabora.co.uk:
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts do that?
In Debian, our
Hi Alin,
Looks good. I changed the title a bit (addedd networkd:) and dropped
the signed off by, as we don't use that, and pushed it.
Thanks for your work!
Cheers,
Tom
On Wed, Dec 17, 2014 at 4:35 PM, Alin Rauta alin.ra...@intel.com wrote:
Signed-off-by: Alin Rauta alin.ra...@intel.com
---
Thanks Tom.
Much appreciated,
Alin
-Original Message-
From: Tom Gundersen [mailto:t...@jklm.no]
Sent: Thursday, December 18, 2014 2:46 PM
To: Rauta, Alin
Cc: systemd Mailing List; Lennart Poettering; Kinsella, Ray
Subject: Re: [PATCH v3] Add FDB support
Hi Alin,
Looks good. I changed
Hi guys,
As a follow-up from splitting sd-hwdb out from libudev, I have just
pushed a patch splitting out the management of the hwdb from udevadm
into its own tool (systemd-hwdb).
The functionality is unchanged, and the fact that the hwdb is very
much Linux- and udev-centric, rather than a
Hey,
I'm sending a patch for udev to export ID_INPUT_[WIDTH|HEIGHT]_MM
properties for tablets and touchscreens. Even if it's scarcely useful info,
IMO it fills a small gap with an eye on Wayland/X11-less sessions.
As some background, I've been hacking on making GNOME input device
configuration
This rule is only run on tablet/touchscreen devices, and extracts their size
in millimeters, as it can be found out through their struct input_absinfo.
Conceivably, that information can be changed through EVIOCSABS anywhere
else, but we're only interested in values prior to any calibration, this
Hi Carlos,
I think David was working on some similar problems recently, so maybe
he has some comments on the overall approach?
Comment on the implementation: If you are going to add this tool to
the systemd codebase, it would be better to do it as a bulit-in
(calling out to binaries should only
Le jeudi 18 décembre 2014 à 12:19 +, Simon McVittie a écrit :
On 18/12/14 08:05, Andrei Borzenkov wrote:
Any initscript that is using su - would [cause badness]
Don't do that then? Init scripts are fairly clearly not login sessions.
Which init scripts do that?
Unfortunately, we don't
Hi
On Thu, Dec 18, 2014 at 3:58 PM, Carlos Garnacho carl...@gnome.org wrote:
This rule is only run on tablet/touchscreen devices, and extracts their size
in millimeters, as it can be found out through their struct input_absinfo.
Conceivably, that information can be changed through EVIOCSABS
Hi
On Thu, Dec 18, 2014 at 4:15 PM, David Herrmann dh.herrm...@gmail.com wrote:
Hi
On Thu, Dec 18, 2014 at 3:58 PM, Carlos Garnacho carl...@gnome.org wrote:
This rule is only run on tablet/touchscreen devices, and extracts their size
in millimeters, as it can be found out through their
Quoting Jóhann B. Guðmundsson (2014-12-18 04:08:32)
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a connection to the session bus
and query PackageKit for the package that the unit file belongs
to. Print it if PackageKit knows.
There are
Am 18.12.2014 um 17:19 schrieb Spencer Baugh:
Quoting Jóhann B. Guðmundsson (2014-12-18 04:08:32)
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a connection to the session bus
and query PackageKit for the package that the unit file belongs
to. Print it
On Thu, Dec 18, 2014 at 8:35 AM, Reindl Harald h.rei...@thelounge.net wrote:
Am 18.12.2014 um 17:19 schrieb Spencer Baugh:
Quoting Jóhann B. Guðmundsson (2014-12-18 04:08:32)
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a connection to the session
On Thu, Dec 18, 2014 at 11:19:22AM -0500, Spencer Baugh wrote:
Quoting Jóhann B. Guðmundsson (2014-12-18 04:08:32)
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a connection to the session bus
and query PackageKit for the package that the unit
On 12/18/2014 05:48 PM, Zbigniew Jędrzejewski-Szmek wrote:
I think you should make it opt-in, with a command-line switch (--show-package
?).
In some cases it can be very useful, but most of the time it would
be just a slow down. If the switch is used, and packagekit does not
work, then this
On Thu, Dec 18, 2014 at 06:33:50PM +, Jóhann B. Guðmundsson wrote:
On 12/18/2014 05:48 PM, Zbigniew Jędrzejewski-Szmek wrote:
I think you should make it opt-in, with a command-line switch
(--show-package ?).
In some cases it can be very useful, but most of the time it would
be just a
On 12/18/2014 06:36 PM, Zbigniew Jędrzejewski-Szmek wrote:
You missed the part where I said you should make it opt-in.
Should we not first determine the practicality of implementing this and
if the system service manager should actually be looking up this info to
begin with?
We could not
On 12/18/2014 06:44 PM, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:36 PM, Zbigniew Jędrzejewski-Szmek wrote:
You missed the part where I said you should make it opt-in.
Should we not first determine the practicality of implementing this
and if the system service manager should actually
On Thu, Dec 18, 2014 at 06:44:25PM +, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:36 PM, Zbigniew Jędrzejewski-Szmek wrote:
You missed the part where I said you should make it opt-in.
Should we not first determine the practicality of implementing this
and if the system service
On Thu, Dec 18, 2014 at 07:09:34PM +, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:44 PM, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:36 PM, Zbigniew Jędrzejewski-Szmek wrote:
You missed the part where I said you should make it opt-in.
Should we not first determine the
Fantastic Tom! You were nice enough to group all the hwdb files in a section.
Can I send a patch to wrap them with a ./configure option? The option
should even include to make udevadm-hwdb.c, libudev-hwdb.c and
udev-builtin-hwdb.c configurable.
Umut
On Thu, Dec 18, 2014 at 3:57 PM, Tom
On Wed, Dec 17, 2014 at 1:04 PM, Hannes Reinecke h...@suse.de wrote:
On 12/16/2014 11:18 PM, Benjamin Marzinski wrote:
On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote:
On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke wrote:
[ .. ]
So during bootup it's anyone's
Quoting Kay Sievers (2014-12-18 15:04:22)
On Thu, Dec 18, 2014 at 8:19 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Thu, Dec 18, 2014 at 07:09:34PM +, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:44 PM, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:36 PM, Zbigniew
On Thu, 18.12.14 18:48, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Thu, Dec 18, 2014 at 11:19:22AM -0500, Spencer Baugh wrote:
Quoting Jóhann B. Guðmundsson (2014-12-18 04:08:32)
On 12/18/2014 04:00 AM, Spencer Baugh wrote:
When printing the status of a unit, open a
Am 18.12.2014 um 21:26 schrieb Spencer Baugh:
Quoting Kay Sievers (2014-12-18 15:04:22)
On Thu, Dec 18, 2014 at 8:19 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Thu, Dec 18, 2014 at 07:09:34PM +, Jóhann B. Guðmundsson wrote:
On 12/18/2014 06:44 PM, Jóhann B. Guðmundsson
On Thu, Dec 18, 2014 at 9:11 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
Can I send a patch to wrap them with a ./configure option? The option
should even include to make udevadm-hwdb.c, libudev-hwdb.c and
udev-builtin-hwdb.c configurable.
Making systemd-hwdb optional (and hence also
Hi,
Commit 6573ef05a3cbe1 (journal: keep per-JournalFile location info
during iteration) breaks tests test-journal-stream and
test-journal-interleaving.
It seems that the logic of overriding f-current_offset in
journal_file_save_location has other unintended side effects, checking
out that
On Wed, Dec 17, 2014 at 01:04:54PM +0100, Hannes Reinecke wrote:
On 12/16/2014 11:18 PM, Benjamin Marzinski wrote:
On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote:
On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke wrote:
[ .. ]
So during bootup it's anyone's
I took a closer look at test-journal-stream. It's setting up 3
journal files and writing entries to the three of them with some
interleaving, then expecting to read them in order.
After commit 6573ef05a3cbe1, what happens is that a single call to
sd_journal_next() ends up calling
On Thu, Dec 18, 2014 at 4:39 PM, Filipe Brandenburger
filbran...@google.com wrote:
Not sure what's the correct solution, maybe journal_file_save_location
needs to happen only in real_journal_next() outside the
ORDERED_HASHMAP_FOREACH loop? I'll try that and report if I find
something that
On Thu, Dec 18, 2014 at 4:58 PM, Filipe Brandenburger
filbran...@google.com wrote:
But this does not work on trunk head, even after adapting it, the
tests start to fail in a different location, probably because of the
changes that come after it, so I think we'll need this and further
changes
Hi,
Now I encountered a prlblem. When I add an entry in /etc/fstab to mount
a disk on a dir like below, mount can be done successfully though /aa/bb
doesn't exist.
_ _ _ _ _
/dev/disk/by-uuid/xxx-xxx /aa/bb xfs defaults 0 2
However when I make a initramfs for kdump kernel, I add an entry
В Mon, 15 Dec 2014 14:20:45 -0600
Dan Williams d...@redhat.com пишет:
On Mon, 2014-12-15 at 20:40 +0300, Andrei Borzenkov wrote:
В Mon, 15 Dec 2014 11:34:17 -0600
Dan Williams d...@redhat.com пишет:
On Mon, 2014-12-15 at 16:11 +0100, Lennart Poettering wrote:
On Sat, 13.12.14
On 12/18/2014 11:04 PM, Benjamin Marzinski wrote:
On Wed, Dec 17, 2014 at 01:04:54PM +0100, Hannes Reinecke wrote:
On 12/16/2014 11:18 PM, Benjamin Marzinski wrote:
On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote:
On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke
On Thu, Dec 18, 2014 at 9:57 PM, Tom Gundersen t...@jklm.no wrote:
On Thu, Dec 18, 2014 at 9:11 PM, Umut Tezduyar Lindskog
u...@tezduyar.com wrote:
Can I send a patch to wrap them with a ./configure option? The option
should even include to make udevadm-hwdb.c, libudev-hwdb.c and
48 matches
Mail list logo