ng) directory and below. It relies
on an http server module that prevents any access to data outside that
directory. So, until I have to share the directory with another user, I
think I will chance it.
Thanks.
-Tom
>
'm also the root user
(and currently the only user)?
Best regards,
-Tom
On Sat, Feb 26, 2022 at 09:38 Dave Howorth wrote:
> On Sat, 26 Feb 2022 09:17:38 -0600
> Tom Browder wrote:
> > Is there any way to get a plain syntax check of a potential new
> > service file?
>
> systemd-analyze verify FILE...
Thanks, Dave.
I'm appare
in red text]*:N: Failed to parse sec value, ignoring: always
I can include my current file if you'd like.
I'm running Debian Buster (10) fully updated.
Thanks.
-Tom
as a reason to reject
it. Similar portability tables like this are already a great start:
<https://systemd.io/PORTABILITY_AND_STABILITY/>
--
Tom Ryder <https://sanctum.geek.nz/>
Maybe we can bring back the light.
___
sy
On Mon, Aug 31, 2020 at 10:43 AM Arian Van Putten wrote:
>
> I can recommend the "Systemd for Administrators" series on
> http://0pointer.net/blog/archives.html as a good cookbook introduction to
> systemd
Thank you, Arian
On Sat, Aug 29, 2020 at 12:22 PM Reindl Harald wrote:
> Am 29.08.20 um 19:17 schrieb Tom Browder:
...
> make the script (besides that scripts don't belong to /etc) a
I will change that.
> oneshot-service and learn about
> https://www.freedesktop.org/software/systemd/man/sy
On Fri, Aug 28, 2020 at 11:12 Andrei Borzenkov wrote:
> 28.08.2020 17:47, Tom Browder пишет:
> > I want to create a service file that has to consider other services.
...
> If you tell us what you try to achieve, someone may have an idea how
> to express it using systemd.
O
ecipes" seem to be
like Github's where each reads like an old Saturday morning movie serial as
in "you've just found out how to write one line in one file. See my next
article on how to write the second line of another file."
Best regards,
-Tom
_
g setup at the moment,
Thanks.
Best regards,
-Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Sun, Aug 23, 2020 at 12:19 PM Tom Browder wrote:
> There is no official Apache systemd setup for Apache from source, and
...
My original post was too harsh. My requests for help haven't been very
clear. Thanks to hints and questions here, I took the time to do a
little scarier experim
stemd tutorials
> – devise your own service unit file for apache httd; you have two
> examples already
> – in your package, install the unit into /usr/lib/systemd/system/
Thanks, Tomasz.
Best regards.
-Tom
___
systemd-devel ma
. I would
greatly appreciate some guidance as to how to install the files
correctly.
Thanks.
Best regards,
-Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
job 1 at Fri Jan 1 00:00:00 2021
--
Tom Ryder <https://sanctum.geek.nz/>
Maybe we can bring back the light.
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hi all,
I'm trying to create a simple timer that will wake up the system from
suspend and run an operation with systemd-inhibit.
Contents of test.service:
[Unit]
Description=Test
[Service]
Type=oneshot
ExecStart=/bin/systemd-inhibit /bin/su user -c "echo 'Test' >
$HOME/asdf"
Contents of test.t
On Wed, Jan 2, 2019 at 10:09 PM James Feeney wrote:
> On 1/2/19 3:21 AM, Reindl Harald wrote:
>>
>> it's pretty obvious when i REQUIRE something that it should be there
>> when i get started
>
> Not only is it not "obvious" that "something should be there", it is not true.
>
> You are confusing "R
On Wed, Dec 20, 2017 at 5:39 PM, Jonathan de Boyne Pollard
wrote:
> Tom H:
>
>> The usual reason for not having a native unit is that you can't force
>> developers to do that work.
>
> Psst! This discussion is predicated upon a falsehood. There is an
> abundance
On Wed, Dec 20, 2017 at 8:59 AM, Reindl Harald wrote:
> Am 20.12.2017 um 14:52 schrieb Tom H:
>> On Tue, Dec 19, 2017 at 2:34 PM, Reindl Harald
>> wrote:
>>> in 2017 it shpuld be a native systemd-unit but from where comes the
>>> "vendor preset: enabled&q
On Tue, Dec 19, 2017 at 2:34 PM, Reindl Harald wrote:
> Am 19.12.2017 um 20:05 schrieb Lennart Poettering:
>> On Mo, 18.12.17 19:40, Cecil Westerhof ([email protected]) wrote:
>>> There is a system with tomcat8 installed and enabled. At the moment it is
>>> not used, so I thought it better
ys-devices-pci:00-:00:14.0-usb1-1\x2d4-1\x2d4:1.0-host8-target8:0:0-8:0:0:0-block-sde-sde9.device
loaded active plugged IUM01-512MFHS 9$
Kind regards,
Tom Matthews
___
systemd-devel mailing list
[email protected]
On 10/12/2017 09:04 PM, Mantas Mikulėnas wrote:
> On Fri, Oct 13, 2017, 00:30 Tom Stellard <mailto:[email protected]>> wrote:
>
> Hi,
>
> The amdkfd kernel driver exposes the /dev/kfd device file for doing gpgpu
> computing on AMD GPUs, I would like
there something else in systemd I need to modify to
get the acls set correctly?
Thanks,
Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
s just an example. I understand that nginx doesn't require a
tty, but the application that I really want to run does.
Thanks,
-Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Nov 11, 2016 at 4:13 PM, Michael Hirmke wrote:
>
> Does anyone know, what "+::" in /etc/passwd means?
Users in the nis (by default) or nisplus db will be valid on that
system if you have "compat" on the "passwd" line of
"/etc/nsswitch.conf".
___
On Sunday, August 14, 2016, Mantas Mikulėnas wrote:
...
Thank you for all the info, Mantas--very helpful!
Best regards,
-Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd
ce in init.d?
4. Do I have to use systemd for a service? If not, how do I do that?
Thanks.
Best regards,
-Tom
___
systemd-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Sun, Jun 26, 2016 at 8:09 AM, Reindl Harald wrote:
> Am 26.06.2016 um 13:27 schrieb Ralf Recktenwald:
>>
>> Smb.conf
>
> how is that a systemd problem?
>
> how do you imagine help without mention distrubition, software-versions,
> cotent of the systemd-unit, systemctl status servicename and so
>
Hi Michał,
Could you configure it manually (using ip(8) or something) and paste the
output of `ip link` and `ip addr`, and also attach the networkd
configuration you tried to use (would be great of course if you could make
it as minimal as possible, but still showing y
lly have any good suggestion
> what to do in this case I must say...
>
> Maybe adding something like a RequireDHCPServer= setting or so, that
> allows configuration of a DHCP server address, and when set would
> result in logged warnings if DHCP leases are offered from other
> server
On Thu, Feb 11, 2016 at 6:06 PM, Lennart Poettering
wrote:
> Heya!
>
> So I am thinking about some spring cleaning, and would love to remove
> the following bits from the systemd package:
>
All this looks good to me.
> 1) systemd-initctl (i.e. the /dev/initctl SysV compat support). Last
>t
On Thu, Jan 14, 2016 at 3:58 PM, Lennart Poettering
wrote:
> On Wed, 13.01.16 10:51, Steve Dickson ([email protected]) wrote:
>>
>> Is is possible to set a variable in the [Unit]
>> section of a service?
>>
>> For example in rpc-gssd.service there is
>> ConditionPathExists=/etc/krb5.keytab
>>
want to wait until it starts, *and* don't want to socket-activate it,
>> the third option is to live in a world of race conditions.
>>
>> On Sun, Jan 10, 2016, 16:25 Tom Yan > <mailto:[email protected]>> wrote:
>>
>> So I am recently experiencing som
targets, and only hold the login until the first target. Nobody
> implemented it though.
>
> But yes, pulseaudio.socket would be a requirement of that. If you don't want
> to wait until it starts, *and* don't want to socket-activate it, the third
> option is to live in a w
So I am recently experiencing some issue with pulseaudio (which I
already filed a bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=93651) that it takes a
long time to start.
The thing is, I am thinking whether it exposed a problem of systemd as
well. For example:
Jan 10 21:31:33 localhost
On Sat, Nov 28, 2015 at 4:42 PM, J Decker wrote:
> On Sat, Nov 28, 2015 at 7:36 AM, Tom Gundersen wrote:
>> On Sat, Nov 28, 2015 at 4:33 PM, J Decker wrote:
>>> Okay maybe it's not stored anywhere
>>>
>>> I was just having a plethora of network iss
On Sat, Nov 28, 2015 at 4:33 PM, J Decker wrote:
> Okay maybe it's not stored anywhere
>
> I was just having a plethora of network issues after updating.
>
> After finding others were reporting issues with the linux kernel 4.2.5
> I rollback to the prior stable 4.1.6... that resolved some of t
This is not really exposed nicely. There is a C library sd-network, which
will give you the events you want, but it is not yet public (you can still
copy it out of git of course).
On Nov 12, 2015 05:24, "J Decker" wrote:
> Should I have not said specifically Arch linux?
> Is it something that can
2f1
> enp69s0f0
> enp69s0f1
>
> or
> enp68s0f0
> enp68s0f1
> ens2f0
> ens2f1
>
> at startup.
>
> That's the best feature of biosdevname, being able to tell which slot
> the NIC is located just from the name. Systemd still has some
> limitations and/or
identifier as he can already identify the client.
Given those two facts, might it not be sufficient to use the
machine-id as the secret key after all? Or am I missing something?
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--- a/src/udev/ata_id/ata_id.c
+++ b/src/udev/ata_id/ata_id.c
@@ -485,6 +485,10 @@ int main(int argc, char *argv[])
disk_identify_fixup_uint16(identify.byte, 90); /*
time required for enhanced SECURITY ERASE UNIT */
disk_identify_fixup_uint16(identify.byte, 9
Hi Michael,
A follow-up on this, we finally figured out a way to make virtio
netdev naming persistent [0], so this will work again as of the next
release. It's a shame we had to go back and forth on this, but I hope
it does not cause you too much headaches.
Cheers,
Tom
[0]:
&
Also attach a log of `udevadm monitor` for your reference.
On 1 September 2015 at 11:32, Tom Yan wrote:
> Is it a limitation or bug that I can only capture remove events with
> purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER?
>
> I unplugged and re-plugged
Is it a limitation or bug that I can only capture remove events with
purely SUBSYSTEM or KENREL match, but not with ATTR{*} or even DRIVER?
I unplugged and re-plugged the specific device once before each `cat test`:
[tom@localhost ~]$ cat /etc/udev/rules.d/usb.rules
KERNEL=="1-14",
e behavior.
>
> But then, back to my first question:
> Is it possible to get an event from udev (or whatever) alerting that: either
> the g_mass_storage is unmounted by the other host _or_ that an usb cable is
> unplugged.
>
>
> I'll check for the rest of your an
Are you sure that the add events in jc.log actually appears before you
plugin anything? I think "usb1" is the host controller/bus and
"usb1/1-0:1.0" is the internal hub. If it's that case of course you
won't see any remove event of them by unpluging your device because
the add events doesn't belong
Maybe there's indeed some problem with your kernel or device. I tried
the following rule on my machine:
/etc/udev/rules.d/usb.rules:SUBSYSTEM=="usb", RUN+="/usr/bin/bash -c
'echo $ACTION $DEVPATH >> /home/tom/test"
And here's the "test" log af
> My device is a small robotic device. To send a file on it, I that users just
> copy files like they do with mass-storage usb-key.
> So: On usb-plugged: I load the module k_mass_storage: the other device see a
> new mass-storage device appearing, copy files and then umount/unpl
Also it seems to be g_mass_storage is just the module for setting up
dummy or emulating an mass storage device. Why would you want it to
depend on a usb "cable"/device?
On 26 August 2015 at 11:21, Tom Yan wrote:
> I am not sure about what you mean here. Do you mean that you ca
I am not sure about what you mean here. Do you mean that you can't see
any remove event with `udevadm monitor` when you unplug the "cable"?
Also do you really mean a "usb cable" without any device connected to
it on the other end?
By the way the rule you set up is so broad that the script will
bas
Ah that explains everything. I was just confused about
RUN{builtin}+="uaccess" but now I get it. Thanks a lot!
On 20 August 2015 at 18:05, Mantas Mikulėnas wrote:
> Well, as in the paste earlier, 73-seat-late.rules is the place where udev
> actually looks at the "uaccess" tag and applies initial
Wed, Aug 19, 2015 at 3:18 PM, Robert Milasan wrote:
>> On Wed, 19 Aug 2015 17:45:28 +0800
>> "Tom Yan" wrote:
>>
>>> Hi all!
>>>
>>> So I added the following rules:
>>> [tom@localhost ~]$ grep . /etc/udev/rules.d/*
>&g
Hi all!
So I added the following rules:
[tom@localhost ~]$ grep . /etc/udev/rules.d/*
/etc/udev/rules.d/uas.rules:DRIVERS=="uas", TAG+="uaccess"
/etc/udev/rules.d/usb-storage.rules:DRIVERS=="usb-storage", TAG+="uaccess"
The rules basically works, but it do
that the change acceptance is unclear for fine-tuning of this software
> also around message log programming interfaces.
> Which design approaches do you find acceptable for further considerations?
Sorry, I really can't follow. If you post a patch we can take it from there.
Cheers,
Tom
ciate you wanting to help, but this is not helpful. Please post
patches if you have suggestions for improvements.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, Jul 29, 2015 at 2:23 PM, Michael Biebl wrote:
> 2015-07-29 5:40 GMT+02:00 Tom Gundersen :
>> On Wed, Jul 29, 2015 at 1:21 AM, Michael Biebl wrote:
>>> something I was wondering regarding kdbus and udev.
>>> If udev wants to drop the netlink transport and inste
On Wed, Jul 29, 2015 at 5:40 AM, Tom Gundersen wrote:
> On Wed, Jul 29, 2015 at 1:21 AM, Michael Biebl wrote:
>> something I was wondering regarding kdbus and udev.
>> If udev wants to drop the netlink transport and instead rely on kdbus,
>> would this mean, systemd bec
m goal. Having the
same software in the initrd as on the real system seems much more
reasonable to me.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
be aware that they need to pick
up iio-sensor-proxy with the next systemd release.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Thu, Jun 18, 2015 at 9:10 PM, Lennart Poettering
wrote:
> On Sat, 30.05.15 19:55, Kai Krakow ([email protected]) wrote:
>
>> The next issue with your argument is: AFAIR nspawn doesn't create a macvlan
>> interface based on the machine name. You have to pass the name of a physical
>> interfac
Thanks for the report.
This should hopefully be fixed by https://github.com/systemd/systemd/pull/65
Cheers,
Tom
On Wed, Jun 3, 2015 at 5:34 PM, Jan Janssen wrote:
> Hi,
>
> systemd-shutdown in 220 has errors when detaching loop devices:
>
> systemd-shutdown[1]: Failed to deta
On Tue, Jun 2, 2015 at 1:53 PM, Karel Zak wrote:
> On Mon, Jun 01, 2015 at 05:06:56PM +0200, Tom Gundersen wrote:
>> > -(void)
>> > sd_event_source_set_description(m->mount_utab_event_source,
>> > "mount-utab-dispatch");
>> >
On Mon, Jun 1, 2015 at 9:16 PM, Robert Schwebel
wrote:
> systemd-timesyncd breaks with
>
> Starting Network Time Synchronization...
> [FAILED] Failed to start Network Time Synchronization.
>
> when we have timesyncd activated and systemd-networkd not. Create
> directory before using it.
Hm, t
nt_monitor_event_cleanup() in v2.26 is broken, so the patch
> uses mnt_monitor_next_change(). It's exactly the same solution which
> uses the current libmount HEAD (mnt_monitor_event_cleanup() is API
> shorcut only).
Tiny nitpick below, otherwise look g
o invalid memory handling in
> device_update_properties_bufs(). Patch attached with detailled
> explanation.
Thanks for figuring this out Martin. The patch looks good to me,
though maybe we should use NULSTR_FOREACH for the second loop?
Go ahead and push.
Cheers,
Tom
__
On Sun, May 31, 2015 at 9:45 PM, Tom Gundersen wrote:
> On Sun, May 31, 2015 at 8:45 PM, Abdó Roig-Maranges
> wrote:
>>
>> Andrei Borzenkov writes:
>>
>>> Was not it fixed by
>>> 693d371d30fee1da58365121801445b404416ada?
>>
>> No.
>
gt; single process, and was fixed in 040e689654ef08c63.
>
> Then it broke again by the commit you point 693d371d30fee1da58, due to the
> fact
> that the sd-event event loop does not like to be passed across forks. This
> breakage still remains in git.
Indeed, I failed at rebas
y',
and notify PID1 once it is ready. In the case of udev the work it
needs to do at startup is to apply permission to static device nodes
(you want to guarantee that this has finished before starting
follow-up services), if it had not been for that udev too could have
been of type 'simple&#
force lvm to use /dev/md126p2 instead of /dev/sdb2
> after starting anaconda?
This seems unlikely to be udevadm settle's fault. All it does is wait
for udev to process events, you may think of it as "sleep 5" or
something like that. It can obviously affect the timing of things, but
as Lennart said the underlying problem is surely elsewhere...
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, May 27, 2015 at 9:47 PM, Patrick Donnelly wrote:
> Signed-off-by: Patrick Donnelly
We don't use s-o-b in systemd, so dropped this when applying. Also
adjusted the subject line a bit (for future reference).
Thanks for the patch! Pushed.
Cheers,
Tom
> ---
> man/systemd
Applied. Thanks!
Tom
On Wed, May 27, 2015 at 9:02 PM, Jonathan Boulle
wrote:
> ---
> src/core/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/core/main.c b/src/core/main.c
> index c39815b10675..212ab901b18f 100644
> --- a/src/core/ma
aks crda, as it expects to see COUNTRY in its environment.
Thanks for the report! This should now be fixed in git. Let me know if
that is not the case.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Wed, May 27, 2015 at 6:23 PM, Tom Gundersen wrote:
> On Wed, May 27, 2015 at 6:16 PM, Filipe Brandenburger
> wrote:
>> Hi Tom,
>>
>> On Wed, May 27, 2015 at 8:45 AM, Tom Gundersen wrote:
>>> It appears a few people see this, but I was not able to reproduce. I
On Wed, May 27, 2015 at 6:16 PM, Filipe Brandenburger
wrote:
> Hi Tom,
>
> On Wed, May 27, 2015 at 8:45 AM, Tom Gundersen wrote:
>> It appears a few people see this, but I was not able to reproduce. If
>> anyone could reproduce with this patch applied [0], it would be most
On Tue, May 26, 2015 at 5:11 PM, Martin Pitt wrote:
> Hello Tom, all,
>
> with 220 I get a severe boot time regression:
>
> $ systemd-analyze
> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>
> which used to be
>
> $ systemd-analyze
Applied. Thanks!
Tom
On Tue, May 26, 2015 at 7:48 AM, Michael Olbrich
wrote:
> Otherwise building faild with kernel headers < v3.16
> ---
> configure.ac | 2 +-
> src/shared/missing.h | 11 +--
> 2 files changed, 10 insertions(+), 3 deletions(-)
>
> dif
to re-read its
> configuration w/o restarting? Maybe D-Bus commands or something?
There is no correct way of doing this at the moment. It is next on my
list of features to work on.
Cheers,
Tom
___
systemd-devel mailing list
systemd-devel@lists.
On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote:
> Martin Pitt on Tue, 2015/05/26 17:11:
>> Hello Tom, all,
>>
>> with 220 I get a severe boot time regression:
>>
>> $ systemd-analyze
>> Startup finished in 30.751s (kernel) + 11.706s (user
On Tue, May 26, 2015 at 9:04 PM, Christian Hesse wrote:
> Martin Pitt on Tue, 2015/05/26 17:11:
>> Hello Tom, all,
>>
>> with 220 I get a severe boot time regression:
>>
>> $ systemd-analyze
>> Startup finished in 30.751s (kernel) + 11.706s (user
-udevd: inotify_add_watch(9, /dev/dm-[0-9]+, 10) failed: Bad file
> descriptor
This was fixed by David in 185abfc3d6b4e8f804a3f7216cd8b0459593af87.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedeskto
Applied. Thanks!
Tom
On Tue, May 26, 2015 at 7:17 PM, Torstein Husebø wrote:
> ---
> NEWS| 4 ++--
> man/journal-remote.conf.xml | 2 +-
> src/libsystemd/sd-bus/bus-control.c | 2 +-
> src/libsystemd/sd-bus/bus-creds.c | 6 +++--
On Tue, May 26, 2015 at 5:11 PM, Martin Pitt wrote:
> Hello Tom, all,
>
> with 220 I get a severe boot time regression:
>
> $ systemd-analyze
> Startup finished in 30.751s (kernel) + 11.706s (userspace) = 42.458s
>
> which used to be
>
> $ systemd-analyze
---
src/udev/udevd.c | 378 ++-
1 file changed, 177 insertions(+), 201 deletions(-)
diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index c9b0ed5..8cffd81 100644
--- a/src/udev/udevd.c
+++ b/src/udev/udevd.c
@@ -41,6 +41,8 @@
#include
#inc
This allows us to drop the special sigterm handling in spawn_wait()
as this will now be passed directly to the worker event loop.
We now log failing processe at 'warning' leve, otherwise the
behavior is unchanged.
---
src/test/test-udev.c| 7 --
src/udev/udev-event.c | 177 +++
Rather than trying to schedule new events on every main-loop iteration, do it
explicitly when
processing an event finishes, a worker is killed, a new uevent is received, or
the event queue
is explicitly restarted.
---
src/udev/udevd.c | 13 ++---
1 file changed, 10 insertions(+), 3 delet
---
units/systemd-udevd.service.in | 1 +
1 file changed, 1 insertion(+)
diff --git a/units/systemd-udevd.service.in b/units/systemd-udevd.service.in
index 32f04d9..e7216d6 100644
--- a/units/systemd-udevd.service.in
+++ b/units/systemd-udevd.service.in
@@ -23,3 +23,4 @@ RestartSec=0
ExecStart=@
Also move builtin and rules initialization from main loop to
event_queue_start().
No functional change.
---
src/udev/udevd.c | 42 +-
1 file changed, 25 insertions(+), 17 deletions(-)
diff --git a/src/udev/udevd.c b/src/udev/udevd.c
index 91fe3d9..e309def
The behavior is mostly unchanged, but rather than only ever calling these
functions at
fixed points in the event loop, they are called directly whenever they are
invoked.
---
src/udev/udevd.c | 80 +++-
1 file changed, 44 insertions(+), 36 dele
Applied. Thanks!
Tom
On Mon, May 25, 2015 at 12:11 PM, Karel Zak wrote:
> This patch simplify swapon usage in systemd. The command swapon(8)
> since util-linux v2.26 supports "-o ". The idea is exactly the
> same like for mount(8). The -o specifies options in fstab-compatible
Applied. Thanks!
Tom
On Mon, May 25, 2015 at 1:35 PM, Marc-Antoine Perennou
wrote:
> ---
> Makefile.am | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile.am b/Makefile.am
> index 4933e6f..8e38010 100644
> --- a/Makefile.am
> +++ b/Makefile
Applied, with minor fix. Please verify that it still works for you!
Tom
On Mon, May 25, 2015 at 11:18 AM, Marc-Antoine Perennou
wrote:
> ---
> Makefile.am | 15 ++-
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/Makefile.am b/Makefile.am
Applied. Thanks!
Tom
On Mon, May 25, 2015 at 11:18 AM, Marc-Antoine Perennou
wrote:
> currently it would only be included if configure was ran with --enable-gnuefi
> ---
> Makefile.am | 14 --
> 1 file changed, 12 insertions(+), 2 deletions(-)
>
> diff --g
%2$s\n"
> +"ExecStart=" SYSTEMD_FSCK_PATH " %2$s\n"
> "TimeoutSec=0\n",
> program_invocation_short_name,
> what,
> --
> 2.4.1
>
> ___
> systemd-deve
On Sat, May 23, 2015 at 6:04 PM, Cristian Rodríguez
wrote:
> It was a warning when we still supported kernel < 3.4. current
> minimum version is 3.7.
Hm, we don't actually fail out here, but we still try to continue.
Isn't 'warning' more appropriate in that case?
Ch
> systemd-devel mailing list
> [email protected]
> http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Applied. Thansk!
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
ot;.)
Thanks for the report. This should be fixed now in git, please let me
know if that is not the case.
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, May 22, 2015 at 3:42 PM, Bastien Nocera wrote:
> It's moved to the iio-sensor-proxy D-Bus service.
Nice! When was this released? Should we expect all distros to have
picked up this yet?
> ---
> .gitignore | 1 -
> Makefile.am| 1
On Mon, May 18, 2015 at 6:55 PM, Lennart Poettering
wrote:
> On Fri, 15.05.15 22:49, Tom Gundersen ([email protected]) wrote:
>
>> On Fri, May 15, 2015 at 10:02 PM, Lennart Poettering
>> wrote:
>> > On Fri, 15.05.15 12:56, Michael Marineau ([email protected])
&g
config in networkd is
backed by a config file somewhere. Does that make sense? Does it
answer your question, or is there some other type of config you would
like to write out?
Cheers,
Tom
___
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Interestingly no other mechanism for
> creating a bridge (ip or brctl) got it into the same state but I'm not sure
> why.
Not sure to be honest, I'll try to keep an eye on this, but as I said
I have not been able to reproduce.
Cheers,
Tom
_
uption of speed value when setting on x64
> systems.
>
> src/udev/net/link-config.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks for the patch! I now pushed a similar fix, please verify that
it works for you.
Cheers,
Tom
_
1 - 100 of 1266 matches
Mail list logo
