On 10/23/2014 12:56 AM, Lennart Poettering wrote:
On Tue, 07.10.14 14:20, WaLyong Cho (walyong@samsung.com) wrote:
If systemd-run is called with timer option, then systemd-run call
NewTransientUnit with service unit. And also call StartTransientUnit
with timer unit which has same name with
On Fri, Oct 10, 2014 at 01:21:10PM +0200, Jan Janssen wrote:
> ---
> src/journal/journalctl.c | 133
> +--
> 1 file changed, 58 insertions(+), 75 deletions(-)
>
> diff --git a/src/journal/journalctl.c b/src/journal/journalctl.c
> index 328e40b..550b610
On Thu, Oct 23, 2014 at 01:09:25AM +0200, Lennart Poettering wrote:
> On Wed, 27.08.14 08:39, Kris Erik Schwerdt (schwe...@itsc.uni-luebeck.de)
> wrote:
>
> > Hallo
> >
> > During a task of migration of multiple servers to a systemd-based
> > distribution I was wondering if there would be a way
On Oct 23, 2014 1:54 AM, "Lennart Poettering"
wrote:
>
> On Wed, 22.10.14 12:44, Damien Robert (
damien.olivier.robert+gm...@gmail.com) wrote:
>
> > Colin Guthrie wrote in message :
> > > I want to rely on systemd --user to handle PulseAudio's activation
> > > (ditching the built in stuff) and bu
El 22/10/14 a las #4, Rob Owens escribió:
> It is your ML, so I will oblige. But I think it is a mistake to not consider
> a broader view of your project than just the strictly technical aspects.
It is not *his* mailing list..but it is the place where *technical*
discussions about the systemd p
On Wed, Oct 22, 2014 at 12:59:45PM +0100, Simon McVittie wrote:
> On 22/10/14 12:37, Lennart Poettering wrote:
> > When used with kdbus we actually do check for that client-side
> > capability. THis is not available on dbus1 however, since we cannot
> > determine the capability racefreely and thus
On Sat, 30.08.14 21:26, Ruben Kerkhof (ru...@rubenkerkhof.com) wrote:
> Hi all,
heya,
> I'm playing around a bit with systemd-nspawn, and the new --volatile option.
> I've got it mostly working so far, except for loggin in to the container as
> root.
>
> Looking at the code, IIUC systemd-first
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23/10/2014 1:03, Lennart Poettering wrote:
> On Thu, 23.10.14 00:52, Philip Van Hoof (phi...@codeminded.be)
> wrote:
>
>>> Don't try to work around limitations of kernel APIs by
>>> implementing inherently not scalabale algorithms in userspace.
>>
On Wed, 27.08.14 08:39, Kris Erik Schwerdt (schwe...@itsc.uni-luebeck.de) wrote:
> Hallo
>
> During a task of migration of multiple servers to a systemd-based
> distribution I was wondering if there would be a way of setting the
> retentiontime of journald per unit.
> In some cases e.g. there ar
On Thu, 23.10.14 00:52, Philip Van Hoof (phi...@codeminded.be) wrote:
> > Don't try to work around limitations of kernel APIs by
> > implementing inherently not scalabale algorithms in userspace. I
> > mean, you implemented something that scales O(n) with n the numbers
> > of dirs. That's what you
On Wed, 27.08.14 09:50, Lukasz Stelmach (stl...@poczta.fm) wrote:
> Yes that is a point. However, the current description the man page
> provides is a bit less accurate than the above. Then, the delay you
> describe does not seem as bad to me as you say. Suppose we've got two
> services: aiccu, sy
On Wed, 22.10.14 12:44, Damien Robert (damien.olivier.robert+gm...@gmail.com)
wrote:
> Colin Guthrie wrote in message :
> > I want to rely on systemd --user to handle PulseAudio's activation
> > (ditching the built in stuff) and but I'm worried that e.g. GNOME or KDE
> > might start up their own
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 21/10/2014 13:21, Lennart Poettering wrote:
> Well, looking at that bug it appears to me that this is caused
> because you try to use inotify for something it shouldn't be used
> for: to recursively watch an entire directory subtree. If you fake
>
On Wed, 22.10.14 21:08, Tobias Hunger (tobias.hun...@gmail.com) wrote:
> > My idea would be that the initrd contains that info. Each usr tree
> > comes with one initrd, and that initrd knows which usr tree to boot.
>
> That implies that each installation snapshot must come with an initrd,
> even
On Wed, 22.10.14 23:53, Lennart Poettering (lenn...@poettering.net) wrote:
> On Fri, 29.08.14 22:03, WaLyong Cho (walyong@samsung.com) wrote:
>
> > On 08/27/2014 02:55 AM, Lennart Poettering wrote:
> > > On Tue, 26.08.14 15:43, WaLyong Cho (walyong@samsung.com) wrote:
> > >
> > >> There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/10/2014 15:33, Simon McVittie wrote:
[cut]
> Resource limits ===
>
> Some resource limits are lower in kdbus than in dbus-daemon.
>
> In kdbus, the number of unread messages per recipient is limited to
> 256, with up to 16 per uid;
On Fri, 29.08.14 22:03, WaLyong Cho (walyong@samsung.com) wrote:
> On 08/27/2014 02:55 AM, Lennart Poettering wrote:
> > On Tue, 26.08.14 15:43, WaLyong Cho (walyong@samsung.com) wrote:
> >
> >> There is no Bofore= or After= dependencies between
> >> systemd-journald.service and systemd-t
On Fri, 29.08.14 15:28, Jan Janssen (medhe...@web.de) wrote:
heya,
sorry for the late review!
Hmm, not generally opposed to allowing this to be configured on the
kernel cmdline, but this is so awfully asymmetric now.
luks.uuid= so far accepts a single UUID, but may be specified multiple times
On Wed, 22.10.14 23:12, Lennart Poettering (lenn...@poettering.net) wrote:
> On Thu, 16.10.14 16:59, WaLyong Cho (walyong@samsung.com) wrote:
>
> > -if (smack_label_ip_in_fd(fd, s->smack_ip_in) < 0)
> > -log_error_unit(UNIT(s)->id, "smack_label_ip_in_fd
On Thu, 16.10.14 16:59, WaLyong Cho (walyong@samsung.com) wrote:
> If selinux is disabled and smack is only enabled, smack label is
> relable-ed by label_fix. To avoid, make only be labeled for selinux.
> ---
> src/udev/udev-node.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
On Thu, 16.10.14 16:59, WaLyong Cho (walyong@samsung.com) wrote:
> -if (smack_label_ip_in_fd(fd, s->smack_ip_in) < 0)
> -log_error_unit(UNIT(s)->id, "smack_label_ip_in_fd:
> %m");
> +if (mac_smack_ip_in_fd(fd, s->smack_ip_in) < 0)
> +
On Wed, 22.10.14 22:12, Tom Gundersen (t...@jklm.no) wrote:
> On Wed, Oct 22, 2014 at 12:19 PM, Lennart Poettering
> wrote:
> > On Sat, 13.09.14 20:40, Tom Gundersen (t...@jklm.no) wrote:
> >
> >> Yeah, this could happen. It so happens that the loopback link will
> >> always have ifindex 1, so I
> From: Lennart Poettering
> We are always interested in technical feedback.
>
> We are not very interested in FUD mails that tell us how we'd "force"
> people, how we'd behave like microsoft and so on. That's not useful,
> that's pretty much only hurtful.
I haven't read this full thread, and
On Wed, Oct 22, 2014 at 10:49 AM, Chris Bell wrote:
> Why 90 seconds? Can this duration be changed?
Could I accomplish this with the `JobTimeoutSec' systemd parameter in
the `user@.service' unit file? I can't seem to force my system to get
stuck on a stop job at the moment to test it. Would chang
- Original Message -
> From: "Lennart Poettering"
>
> On Wed, 22.10.14 12:11, Rob Owens (row...@ptd.net) wrote:
>
> > > We are always interested in technical feedback.
> >
> > I have seen this comment several times from the systemd devs, and I
> > don't doubt it. But I think much of th
Hi Lennart,
On Wed, Oct 22, 2014 at 7:03 PM, Lennart Poettering
wrote:
> Sorry for the late response, been travelling for a month, and then
> have been more travelling, and still trying to process all the mails
> that queued up since.
No problem at all:-)
>> On Fri, Sep 5, 2014 at 6:58 PM, Lenn
On Wed, Oct 22, 2014 at 12:20 PM, Lennart Poettering
wrote:
> On Thu, 11.09.14 07:07, Chris Morgan (chmor...@gmail.com) wrote:
>
>> Hmm. I figured that the environment was used when the systemd user
>> instance was started.
>>
>> I tried systemctl --user set-environment and it shows up if I use
>>
On Wed, 22.10.14 20:49, Tom Gundersen (t...@jklm.no) wrote:
> On Wed, Oct 22, 2014 at 6:23 PM, Lennart Poettering
> wrote:
> > On Wed, 22.10.14 18:16, Tom Gundersen (t...@jklm.no) wrote:
> >
> >> Hi guys,
> >>
> >> I finally got around to have a look at this. I can reproduce the
> >> problem, and
On Fri, 12.09.14 15:25, Dale R. Worley (wor...@alum.mit.edu) wrote:
> > From: Tobias Geerinckx-Rice
>
> > Step back, and define exactly what it is you actually need^Wwant to do.
>
> For a certain entry in /etc/fstab (which will in practice always have
> the option "nofail"), if the device is no
On Wed, Oct 22, 2014 at 6:23 PM, Lennart Poettering
wrote:
> On Wed, 22.10.14 18:16, Tom Gundersen (t...@jklm.no) wrote:
>
>> Hi guys,
>>
>> I finally got around to have a look at this. I can reproduce the
>> problem, and for me a workaround is to set RequestBroadcast=yes in the
>> DHCP section in
On Thu, 28.08.14 21:33, WaLyong Cho (walyong@samsung.com) wrote:
> runtime journal is migrated to system journal when only
> "/run/systemd/journal/flushed" exist. It's ok but according to this
> the system journal directory size(max use) can be over the config. If
> journal is not rotated duri
On Thu, 28.08.14 00:44, WaLyong Cho (walyong@samsung.com) wrote:
> On 08/27/2014 03:49 AM, Lennart Poettering wrote:
> > On Tue, 26.08.14 18:11, Mantas Mikulėnas (graw...@gmail.com) wrote:
> >
> >> On Tue, Aug 26, 2014 at 5:07 PM, WaLyong Cho
> >> wrote:
> >>>
> >>> This case really shouldn
On Thu, 28.08.14 13:30, Dave Reisner (dreis...@archlinux.org) wrote:
> Some package managers will chroot before running post-install and
> post-upgrade scripts. Doing this prevents systemd-firstboot from being
> used piecemeal at installation or upgrade time, as the --root=/ will be
> "cleverly" i
On Sun, 31.08.14 11:12, Jan Janssen (medhe...@web.de) wrote:
> @@ -68,7 +68,7 @@ static bool arg_follow = false;
> static bool arg_full = true;
> static bool arg_all = false;
> static bool arg_no_pager = false;
> -static int arg_lines = -1;
> +static int arg_lines = -2;
Humm. No, please don't!
On Mon, 25.08.14 21:58, Filipe Brandenburger (filbran...@google.com) wrote:
>
> On Wed, Aug 20, 2014 at 3:27 PM, Lennart Poettering
> wrote:
> > Well, we have our own dbus library implementation since a while
> > ("sd-bus") that supports both dbus1 and kdbus as transport. We only link
> > agains
On Fri, 29.08.14 16:22, Mauricio Tavares (raubvo...@gmail.com) wrote:
Heya,
it's fun picking up two month old threads! ;-)
> So I have a system 2 interfaces, each of them using dhcp in
> different networks (both served by the same nameserver but in
> different vlans). Let's begin by showin
On Tue, 30.09.14 17:02, Marius Tessmann (mus@gmail.com) wrote:
> On 09/30/2014 05:03 AM, Zbigniew Jędrzejewski-Szmek wrote:
> >On Fri, Aug 29, 2014 at 05:51:45PM +0200, Marius Tessmann wrote:
> >>Since commit b1e90ec515408aec2702522f6f68c4920b56375b systemd passes
> >>its log settings to syste
On Tue, 02.09.14 10:06, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> Hi,
>
> I would like to start a configurable set of services first and the
> services are wanted by multi-user.target. I am using a service to jump
> to multi-user.target and I was wondering if we can support this use
> c
On Tue, 02.09.14 11:15, Alexander E. Patrakov (patra...@gmail.com) wrote:
> Hello.
>
> I have a Gentoo system, with btrfs on /dev/sda2 (also known as
> /dev/disk/by-id/ata-OCZ-VECTOR_OCZ-Z5CB4KC20X0ZG7F8-part2) and with dracut
> 038 with Gentoo patches that you can view here:
>
> http://sources.
On Fri, 05.09.14 16:17, Chaiken, Alison (alison_chai...@mentor.com) wrote:
> (BTW, Lennart and Kai, is there a reason this great article couldn't
> be hosted at freedesktop.org or 0pointer.de?)
Well, not sure if we own all the rights to be able to do that. As it
appears h-online.com is back up th
On Fri, 05.09.14 13:52, Viswambharan, Vibin (V.) (vvi...@visteon.com) wrote:
> 1/ Is there a recommended way to re-organize the boot target order (
> I don't see there is a way to fit my userlevel application
> executables or deamons needed for early functionality to be
> associated with these "pr
On Thu, 11.09.14 15:54, juho son (juho80@samsung.com) wrote:
> >We don't use S-O-b on systemd...
> I will send again follow.
Oh, that was just a hint for the future, no need to redo the patch
just to drop s-o-b. We usually drop it though while committing.
Anyway, merged your repost.
Thanks
On Thu, 11.09.14 16:06, Juho Son (juho80@samsung.com) wrote:
> systemd-journald check the cgroup id to support rate limit option for
> every messages. so journald should be available to access cgroup node in
> each process send messages to journald.
> In system using SMACK, cgroup node in proc
On Fri, 05.09.14 20:34, Tobias Hunger (tobias.hun...@gmail.com) wrote:
Heya,
Sorry for the late response, been travelling for a month, and then
have been more travelling, and still trying to process all the mails
that queued up since.
> On Fri, Sep 5, 2014 at 6:58 PM, Lennart Poettering
> wrote
On Mon, 08.09.14 11:56, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
> On 05/09/14 18:22, Jakub Klinkovský wrote:
> > What is the reason behind logging unit's description? Consider the
> > following journal message (from `journalctl -b`):
> >
> > systemd[1]: Starting A secure, fast, com
On Wed, 22.10.14 18:35, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> > That's difficult to say just from these logs. Can you reliably
> > reproduce this? If so, can you attach strace to journald before this
> > happens and see what it is doing?
>
> I am wondering if we should send another
On Tue, 09.09.14 01:40, Ivan Shapovalov (intelfx...@gmail.com) wrote:
> The patch by Umut did miss at least hybrid-sleep -- it involves hibernation
> as well (hybrid sleep is a hibernation followed by S3 rather than S4
> powerdown).
>
> Also, it messed up indentation a bit (Makefile.am seems to
On Wed, Oct 22, 2014 at 4:59 PM, Lennart Poettering
wrote:
> On Wed, 22.10.14 13:10, Damien Robert (damien.olivier.robert+gm...@gmail.com)
> wrote:
>
>> On one boot I got a watchdog timeout on systemd-journald:
>>
>> Oct 21 20:08:21 feanor systemd-journal[213]: Permanent journal is using
>> 68.7
2014-10-22 18:30 GMT+02:00 Lennart Poettering :
> On Wed, 22.10.14 18:28, Ronny Chevalier (chevalier.ro...@gmail.com) wrote:
>
>> >> I'm not sure abou the name 'amendments.conf'. Wouldn't 'local.conf'
>> >> be more idiomatic, and also easier to type?
>> >
>> > I was thinking about this too, and I w
On Wed, 22.10.14 18:28, Ronny Chevalier (chevalier.ro...@gmail.com) wrote:
> >> I'm not sure abou the name 'amendments.conf'. Wouldn't 'local.conf'
> >> be more idiomatic, and also easier to type?
> >
> > I was thinking about this too, and I wanted to propose "override.conf"
> > instead?
> >
> > T
On Mon, 08.09.14 15:09, Tom Gundersen (t...@jklm.no) wrote:
> Applied. Thanks!
Hmm, the route metric for dhcp routes is now configurable. But what
about implied routes created due to static IP configuration?
I wonder if it wouldn't be a better idea to move RouteMetric= from the
[DHCP] section in
On Wed, 22.10.14 18:16, Tom Gundersen (t...@jklm.no) wrote:
> Hi guys,
>
> I finally got around to have a look at this. I can reproduce the
> problem, and for me a workaround is to set RequestBroadcast=yes in the
> DHCP section in the .network file for your host0 interface in the
> container. Doe
On Wed, Oct 8, 2014 at 10:04 AM, Moviuro wrote:
> Hi all!
>
> In order to fix in an easily predictable manner the interfaces' names, I went
> and wrote the following .link file:
>
> /etc/systemd/network/00-default.link
> [Link]
> NamePolicy=mac
> MACAddressPolicy=persistent
Looks good.
> I daemo
On Sun, Oct 12, 2014 at 12:57 AM, Tom Gundersen wrote:
> On Fri, Sep 26, 2014 at 4:52 AM, Leonid Isaev wrote:
>> Hi,
>>
>> On Thu, Sep 25, 2014 at 04:56:55PM -0700, James Lott wrote:
>>> Actually, the reason I am using dhcpcd fro mthe command line is as a
>>> debugging
>>> measure, because I ori
On Wed, 22.10.14 12:11, Rob Owens (row...@ptd.net) wrote:
> > We are always interested in technical feedback.
>
> I have seen this comment several times from the systemd devs, and I
> don't doubt it. But I think much of the criticism of systemd is not
> technical. It has a more social/political
- Original Message -
> From: "Lennart Poettering"
> We are always interested in technical feedback.
I have seen this comment several times from the systemd devs, and I don't doubt
it. But I think much of the criticism of systemd is not technical. It has a
more social/political nature,
On Wed, 10.09.14 13:51, Philippe De Swert (philippedesw...@gmail.com) wrote:
> Ok so it has been taken into use and can actually somehow be considered part
> of
> the coding style? The mail was still speculating about it and I could not
> quickly see a confirmation of this.
Yes, it is the codin
On Wed, 10.09.14 12:20, philippedesw...@gmail.com (philippedesw...@gmail.com)
wrote:
> From: Philippe De Swert
>
> m->kdbus could be freed before it is released. Changing the
> order fixes the issue.
David applied this now, but actually, just for the sakes of archives,
this is a false positive
On Tue, 07.10.14 14:20, WaLyong Cho (walyong@samsung.com) wrote:
> If systemd-run is called with timer option, then systemd-run call
> NewTransientUnit with service unit. And also call StartTransientUnit
> with timer unit which has same name with the service. So actually, two
> method call is
On Tue, 07.10.14 14:20, WaLyong Cho (walyong@samsung.com) wrote:
> It similar with StartTransientUnit but the NewTransientUnit does not
> start the unit immediately. Newly generated transient unit can be
> activated by "systemctl start".
So far units are immediately GC'ed when they aren't run
>From Lennart Poettering, Wed 22 Oct 2014 at 16:59:09 (+0200) :
> On Wed, 22.10.14 13:10, Damien Robert (damien.olivier.robert+gm...@gmail.com)
> wrote:
> That's difficult to say just from these logs.
Yeah that was what I feared.
> Can you reliably reproduce this? If so, can you attach strace to
On Wed, 17.09.14 16:20, WaLyong Cho (walyong@samsung.com) wrote:
> Before start working it, we need some of discussion about how make the
> transient unit. I think we have two options.
> One is, as you said, make systemd-at and the other is add option to
> systemd-run. (e.g. --OnCalendar=, --O
On Thu, 11.09.14 17:45, WaLyong Cho (walyong@samsung.com) wrote:
> (I will happy there is already similar method already exist.)
>
> systemd already has similar functionality "systemd-run" but that is only
> for scope or service unit. I think that is useful run a service without
> unit file o
El 22/10/14 a las #4, Ivan Shapovalov escribió:
> Hi,
>
> The systemd.timer(5) manpage states:
>
> "For each timer file, a matching unit file must exist, describing the unit to
> activate when the timer elapses."
>
I guess for now you can create a dummy unit that executes /bin/true to
workaroun
On Wed, 22.10.14 14:28, Reindl Harald (h.rei...@thelounge.net) wrote:
> >Why precisely your syslog implementation is too slow is something
> >you'd have to debug on the side of theat implementation, we cannot
> >determine this from systemd's side.
> >
> >Note that rsyslog doesn't need the syslog f
On Wed, 22.10.14 14:09, Hans de Goede (hdego...@redhat.com) wrote:
> The compaq ku 0133 keyboard has 8 special keys at the top:
> http://lackof.org/taggart/hacking/keyboard/cpqwireless.jpg
>
> 3 of these use standard HID usage codes from the consumer page, the 5
> others use part of the reserved
On Wed, 10.09.14 09:12, Tristan Brindle (tcbrin...@gmail.com) wrote:
>
> Hi all,
>
> I needed to use systemd for a new project, and I was surprised to
> find that there was no nice client library available wrapping the
> D-Bus API in GObjects (or at least, if one exists, Google couldn’t
> find i
On Wed, 22.10.14 14:05, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
> On Wed, Oct 22, 2014 at 02:50:13PM +0400, Ivan Shapovalov wrote:
> > Hi,
> >
> > The systemd.timer(5) manpage states:
> >
> > "For each timer file, a matching unit file must exist, describing the unit
> > to
> > ac
On Wed, 22.10.14 13:10, Damien Robert (damien.olivier.robert+gm...@gmail.com)
wrote:
> On one boot I got a watchdog timeout on systemd-journald:
>
> Oct 21 20:08:21 feanor systemd-journal[213]: Permanent journal is using 68.7M
> (m
> Oct 21 20:08:21 feanor systemd-journal[213]: Time spent on fl
Am 22.10.2014 um 16:49 schrieb Chris Bell:
I'm running into an annoying issue. I use systemd 216 on an Arch box,
and systemd 208 on a Fedora box; the issue exists on both. Logins are
handled through getty; there is no desktop manager involved.
Occasionally, on shutdown, I get a 90 second hold wh
Hi all,
I'm running into an annoying issue. I use systemd 216 on an Arch box,
and systemd 208 on a Fedora box; the issue exists on both. Logins are
handled through getty; there is no desktop manager involved.
Occasionally, on shutdown, I get a 90 second hold while waiting for a
'Stop Job for User
On Wed, 22.10.14 16:00, Torstein Husebø (torst...@huseboe.net) wrote:
Thanks!
Applied!
> ---
> src/systemd/sd-network.h | 9 +
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/src/systemd/sd-network.h b/src/systemd/sd-network.h
> index 203a2a6a47..bb69940930 100644
>
---
src/systemd/sd-network.h | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/src/systemd/sd-network.h b/src/systemd/sd-network.h
index 203a2a6a47..bb69940930 100644
--- a/src/systemd/sd-network.h
+++ b/src/systemd/sd-network.h
@@ -61,7 +61,7 @@ int sd_network_get_opera
On one boot I got a watchdog timeout on systemd-journald:
Oct 21 20:08:21 feanor systemd-journal[213]: Permanent journal is using 68.7M (m
Oct 21 20:08:21 feanor systemd-journal[213]: Time spent on flushing to /var is 2
Oct 21 20:08:25 feanor kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not r
Lennart Poettering wrote in message <20141020173828.GA4509@gardel-login>:
> They should probably adopt socket activation anyway, otherwise they'd
> be quite annoying on multi-user systems if lingering is used.
I am brainstorming here, but would it make sense to add hooks to logind
when a session
Colin Guthrie wrote in message :
> I want to rely on systemd --user to handle PulseAudio's activation
> (ditching the built in stuff) and but I'm worried that e.g. GNOME or KDE
> might start up their own session stuff and spawn some PA consuming
> process before systemd --user has reached it's soc
On 10/20/2014 08:42 PM, Lennart Poettering wrote:
> On Thu, 16.10.14 09:50, Michal Schmidt (mschm...@redhat.com) wrote:
>> +/* Fields that all hashmap/set types must have */
>> +struct HashmapBase {
>> +const struct hash_ops *hash_ops; /* hash and compare ops to use */
>> +
>> +uni
On 10/22/2014 11:51 AM, Alexandre Detiste wrote:
Why not migrate what needs to be migrated to native system timer formats
This would be the responsability of each individual package manager;
after some policy would have mandated it and it's too late before the release
freeze.
Debian only ships
Am 22.10.2014 um 13:22 schrieb Lennart Poettering:
On Mon, 15.09.14 13:20, Reindl Harald (h.rei...@thelounge.net) wrote:
anybody an idea why?
Sep 15 13:14:43 localhost systemd-journal[4650]: Forwarding to syslog missed 2
messages.
Sep 15 13:15:13 localhost systemd-journal[4650]: Forwarding
Hello Martin,
Firstly, I apologise if you took what I said as a personal insult. It
was not my intention to do so (and I did try to make that explicitly
clear in a footnote).
I will certainly admit that some of my wording was more directed than I
had intended. This is something I would normally e
On 10/22/2014 11:26 AM, Alexandre Detiste wrote:
it just doesn't send emails like cron; but that will remain an wontfix I guess.
Systemd itself does not send email but you can configure the timer units
( the service part ) to do so when they fail via OnFailure=custom email script> but you hav
The compaq ku 0133 keyboard has 8 special keys at the top:
http://lackof.org/taggart/hacking/keyboard/cpqwireless.jpg
3 of these use standard HID usage codes from the consumer page, the 5
others use part of the reserved 0x07 - 0x1f range.
This commit adds mapping for this keyboard for these reser
On Wed, Oct 22, 2014 at 02:50:13PM +0400, Ivan Shapovalov wrote:
> Hi,
>
> The systemd.timer(5) manpage states:
>
> "For each timer file, a matching unit file must exist, describing the unit to
> activate when the timer elapses."
>
> However, if I need the timer unit just to wake up the machine
On 22/10/14 12:37, Lennart Poettering wrote:
> When used with kdbus we actually do check for that client-side
> capability. THis is not available on dbus1 however, since we cannot
> determine the capability racefreely and thus safely
... because the kernel doesn't give us that ability on Unix sock
>Why not migrate what needs to be migrated to native system timer formats
This would be the responsability of each individual package manager;
after some policy would have mandated it and it's too late before the release
freeze.
Debian only ships exaclty one timer now: systemd-tmpfiles-clean.time
On 21/10/14 20:25, Lennart Poettering wrote:
> Ah, well, at least they should make the lib64 thing arch dependent.
Multiarch means that whichever architecture systemd happens to have been
compiled for, /lib64 might exist. If it does, it's a system library
directory.
(Consider an i386 or armhf sys
On 21/10/14 20:30, Lennart Poettering wrote:
> But in cases like the iptables tool (which
> is written in a style that kinda requires the usage of shell scripts
> to invoke it, since it is more a programming language and is seldom
> called just once at boot)
If your ruleset is static (e.g. does no
On Wed, 10.09.14 16:03, Michal Witanowski (m.witanow...@samsung.com) wrote:
> Hi,
>
> I was wondering if there is a possibility to call "systemctl poweroff" as
> non-root user in this scenario:
>
> 1.I have no PolicyKit on my system, so I get access denied.
>
> 2. Calling with "-f
On Thu, 11.09.14 10:49, Alexander Larsson (al...@redhat.com) wrote:
> Hi, I'm looking at creating a runtime/app thing for Gnome in the style
> of:
> http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html
>
> However, I noticed that some core dependencies like mesa uses libudev
On Sat, 13.09.14 23:04, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> В Fri, 12 Sep 2014 19:10:01 +0100
> "lux-integ" пишет:
>
> > On Friday 12 September 2014 18:28:30 Dave Reisner wrote:
> > > I'll stop you here. You can't simply "synthesize" a socket unit for any
> > > arbitrary program that
(sorry mail fired up too soon)
> Or to put this differently we will not create. come up with, ship ( and
> thus support those ) generators but expect consumers of systemd to use
> systemd and it's format natively in their environment.
>
> Alexandre why did you decide to write that generate to b
On 10/22/2014 11:16 AM, Alexandre Detiste wrote:
>Why not migrate what needs to be migrated to native system timer formats
>for those relevant component and leave the rest be handled by the
>traditional cron daemons since those two components complement each
>others shortcomings ?
"The rest"
On Mon, 15.09.14 13:20, Reindl Harald (h.rei...@thelounge.net) wrote:
> anybody an idea why?
>
> Sep 15 13:14:43 localhost systemd-journal[4650]: Forwarding to syslog missed
> 2 messages.
> Sep 15 13:15:13 localhost systemd-journal[4650]: Forwarding to syslog missed
> 196 messages.
> Sep 15 13:
> Or to put this differently we will not create. come up with, ship ( and
> thus support those ) generators but expect consumers of systemd to use
> systemd and it's format natively in their environment.
>
> Alexandre why did you decide to write that generate to begin with?
Hi,
I've been usi
On Mon, 15.09.14 13:03, Jan Včelák (jan.vce...@nic.cz) wrote:
> > After=syslog.target is redundant since a long time. Consider removing
> > this. And After=network.target usually doesn't do what one might thing
> > it does and with well written software that listens to rtnl or uses
> > IP_FREEBIND
On Wed, 22.10.14 13:03, Alexandre Detiste (alexandre.deti...@gmail.com) wrote:
> > > -) how can I trigger a rerun of the generator
> >
> > generators are rerun if you issue "systemctl daemon-reload"
>
> I already know,
>
> this is what our "trigger unit" does.
> https://github.com/systemd-cro
On Wed, 22.10.14 14:48, Ivan Shapovalov (intelfx...@gmail.com) wrote:
> On Wednesday 22 October 2014 at 10:26:49, Jóhann B. Guðmundsson wrote:
> >
> > On 10/22/2014 09:44 AM, Lennart Poettering wrote:
> > > So, I thought myself a couple of times about adding a cron generator
> > > upstrea
> > -) how can I trigger a rerun of the generator
>
> generators are rerun if you issue "systemctl daemon-reload"
I already know,
this is what our "trigger unit" does.
https://github.com/systemd-cron/systemd-cron/blob/master/src/units/cron-update.service.in
https://github.com/systemd-cron/syst
Hi,
The systemd.timer(5) manpage states:
"For each timer file, a matching unit file must exist, describing the unit to
activate when the timer elapses."
However, if I need the timer unit just to wake up the machine (e. g. I have a
GUI alarm which does everything except configuring the wakealarm)
On Wednesday 22 October 2014 at 10:26:49, Jóhann B. Guðmundsson wrote:
>
> On 10/22/2014 09:44 AM, Lennart Poettering wrote:
> > So, I thought myself a couple of times about adding a cron generator
> > upstream
>
> As far as I can tell generators serve only one purpose and that is to
> bridge
1 - 100 of 116 matches
Mail list logo
