On Wed, Apr 21, 2021 at 12:20 PM Simon Foley wrote:
...
> Here we can use the HWADDR= variable in the ifcfg-[device name] files to
> move a *specific* device name to these targeted NIC cards and ports.
Read man systemd.link.
[Match]
MACAddress= (or PermanentMACAddress=)
[Link]
On Wed, Apr 14, 2021 at 1:35 PM Ulrich Windl
wrote:
>
> Hi!
>
> I have two services defined, one using ExecStart only, the other ExecStop
> only.
> Then I discovered some asymmetry:
> systemd is still starting the service with the ExecStop only, while the one
> with the ExecStart only never is
I understand correctly it can be overridden if the user
explicitly starts ecs.service using 'systemctl start' ?
>
Requires= cannot be overridden.
> On 4/9/21, 11:45 PM, "systemd-devel on behalf of Andrei Borzenkov"
> arvidj...@gmail.com> wrote:
>
> On 10.04.2021 03
On 10.04.2021 03:07, Cameron Sparr wrote:
> Hello, I work for Amazon ECS and I’ve been working on a change to one of our
> systemd services. From what I could tell in documentation I found online, it
> seemed that RequiresOverridable= was the perfect fit for our use-case.
>
>
> When I built a
On 27.03.2021 10:11, John Ioannidis wrote:
...
>
> *workdir.path *
>
> [Unit]
> Description=Trigger workdir.service when a job starts, creating a directory
> in /opt/circleci/workdir
> After=ccistated.service
> ConditionPathExists=/run/metadata/tags/resource_class
> [Path]
>
On 14.03.2021 09:03, John Ioannidis wrote:
> I have the following service file:
>
> [Unit]
> Description=D
> After=network.target
>
> [Service]
> ExecStart=/usr/local/sbin/mktags.py
> Type=oneshot
> User=root
>
This is default anyway
> [Install]
> WantedBy=multi-user.target
>
>
>
On Fri, Mar 12, 2021 at 10:34 AM Ulrich Windl
wrote:
>
> >>> Reindl Harald schrieb am 11.03.2021 um 16:23 in
> Nachricht <4422087b-9966-e7fb-66ad-4157d83f2...@thelounge.net>:
>
> >
> > Am 11.03.21 um 12:17 schrieb Ulrich Windl:
> >> Hi!
> >>
> >> I have a unit that uses logger, and I want to run
12.02.2021 10:04, Ulrich Windl пишет:
>>>> Andrei Borzenkov schrieb am 11.02.2021 um 15:20 in
> Nachricht
> :
>> On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl
>> wrote:
>>>
>>> Hi!
>>>
>>> Suspecting systemd added some require
On Thu, Feb 11, 2021 at 1:47 PM Ulrich Windl
wrote:
>
> Hi!
>
> Suspecting systemd added some requirement that isn't fulfilled after boot,
> preventing my units from starting I wonder:
> How can I debug systemd's requirements checking for units that are enabled,
> but not started at boot
On Tue, Feb 9, 2021 at 11:54 AM Ulrich Windl
wrote:
>
> Thanks and "back to the mess": If I use libvirtd.service instead of
> libvirtd-tls.socket, it does *not* open the TLS socket, even though the
> configuration file contains "listen_tls=1"...
libvirtd --listen
Did you read the link I gave
08.02.2021 12:10, Ulrich Windl пишет:
> It seems systemd messes with that in a bad way.
>
Streetlight effect ...
For the last time - systemd does exactly what unit definitions tell it
to do. Unit definitions belong to your application. If unit definitions
that come with application are not
06.02.2021 00:33, Phillip Susi пишет:
>
> Lennart Poettering writes:
>
>> journalctl gives you one long continues log stream, joining everything
>> available, archived or not into one big interleaved stream.
>
> If you ask for everything, yes... but if you run journalctl -b then
> shuoldn't it
04.02.2021 17:53, Simon McVittie пишет:
> On Thu, 04 Feb 2021 at 13:07:33 +0100, Reindl Harald wrote:
>> "Requires=a.service" combined with "Before=a.service" is contradictory -
>> don't you get that?
>
> It means what it says: whenever my service is enabled, a.service must
> also be enabled, but
04.02.2021 10:47, Ulrich Windl пишет:
>>>> Andrei Borzenkov schrieb am 03.02.2021 um 19:13 in
> Nachricht :
>> 02.02.2021 12:43, Ulrich Windl пишет:
>>> Hi!
>>>
>>> Having:
>>> ---
>>> # /usr/lib/systemd/system/virtlockd.service
&g
03.02.2021 22:25, Benjamin Berg пишет:
> On Wed, 2021-02-03 at 20:47 +0300, Andrei Borzenkov wrote:
>> 03.02.2021 00:25, Benjamin Berg пишет:
>>> On Tue, 2021-02-02 at 22:50 +0300, Andrei Borzenkov wrote:
>>>> 02.02.2021 17:59, Lennart Poettering пишет:
>>>
03.02.2021 21:13, Andrei Borzenkov пишет:
> 02.02.2021 12:43, Ulrich Windl пишет:
>> Hi!
>>
>> Having:
>> ---
>> # /usr/lib/systemd/system/virtlockd.service
>> [Unit]
>> Description=Virtual machine lock manager
>> Requires=virtlockd.socket
&g
02.02.2021 12:43, Ulrich Windl пишет:
> Hi!
>
> Having:
> ---
> # /usr/lib/systemd/system/virtlockd.service
> [Unit]
> Description=Virtual machine lock manager
> Requires=virtlockd.socket
> Requires=virtlockd-admin.socket
That's always wrong with After for the same units unless you can prove
03.02.2021 00:25, Benjamin Berg пишет:
> On Tue, 2021-02-02 at 22:50 +0300, Andrei Borzenkov wrote:
>> 02.02.2021 17:59, Lennart Poettering пишет:
>>>
>>> Note that Requires= in almost all cases should be combined with an
>>> order dep of After= onto th
02.02.2021 17:59, Lennart Poettering пишет:
>
> Note that Requires= in almost all cases should be combined with an
> order dep of After= onto the same unit.
Years ago I asked for example when Requires makes sense without After.
Care to show it? I assume you must have use case if you say "in
19.01.2021 04:00, lejeczek пишет:
> hi guys.
>
> I'm fiddling with it but have run out of options/ideas.
> What I would like to have is systemd starts a service when a device, in
> my case a crypt-luks device, gets mounted which mount would happen by
> manual 'cryptsetup open'
I am not aware
27.12.2020 17:00, Reindl Harald пишет:
>
>
> Am 27.12.20 um 14:43 schrieb Andrei Borzenkov:
>> 27.12.2020 16:26, Germano Massullo пишет:
>>> Good day, I recently joined apcupsd (APC UPS Power Control Daemon)
>>> package maintainers on Fedora/CentOS/RHEL.
>>
27.12.2020 16:26, Germano Massullo пишет:
> Good day, I recently joined apcupsd (APC UPS Power Control Daemon)
> package maintainers on Fedora/CentOS/RHEL.
> After a power failure, apcupsd shuts down the system with a command
> almost identical to
> shutdown -h -H now
> Usually when you normally
On Thu, Dec 24, 2020 at 5:48 AM John wrote:
>
> I need to have the following start
> /usr/lib/systemd/user/pulseaudio.service so it can make use of
> pulseaudio. Using a After= or Wants= does not work. What is the
> correct way to have a system service like this run a user service
> unit?
>
23.12.2020 18:28, Alexander Sbitnev пишет:
> Hi there!
> I am trying to use upcoming Debian 11 Bullseye with read-only root
> filesystem.
> And I discovered SystemD behaviour change compared to Debian 9. It is not
> related to read-only root by itself and can be easily reproduced with a
>
21.12.2020 20:23, freedesk...@priatel.co.uk пишет:
> Perhaps I'm missing something, but that's still not doing what I expect.
>
> Here's what I have...
>
> #- /etc/systemd/system/first.target -#
> [Unit]
> Description=Started first
> Wants=third.service
>
> #-
14.12.2020 05:08, John пишет:
> If I call systemctl to shutdown or reboot, the effect is that it does
> not honor kodi-x11.service's ExecStop= line which results in an
> unclean exit of kodi and of data loss since kodi writes out some data
> when it exits. By contrast, calling systemctl to stop
14.11.2020 22:18, Nikolaus Rath пишет:
> On Nov 14 2020, Andrei Borzenkov wrote:
>> 14.11.2020 14:32, Nikolaus Rath пишет:
>> ...
>>>>>
>>>>> # grep -vE '^#' /etc/systemd/journald.conf
>>>>>
>>>>> [Journal]
>>>&
14.11.2020 14:32, Nikolaus Rath пишет:
...
>>>
>>> # grep -vE '^#' /etc/systemd/journald.conf
>>>
>>> [Journal]
>>> SystemMaxUse=300M
>>
>> The number shown by disk usage (320 MB) is higher than 300 MB. Maybe also
>> check the files
>> in `/var/log/journal`.
>
> It's a bit bigger on disk too:
>
Quoting https://freedesktop.org/wiki/Software/systemd/Debugging/
console= can be specified multiple times, systemd will output to all of
them.
That's wrong. systemd will write to /dev/console and according to kernel
documentation (and my experience :) ) kernel will forward it only to the
last
man systemd(1):
$SYSTEMD_LOG_TARGET
===
systemd reads the log target from this environment variable. This can be
overridden with --log-target=.
--log-target=
=
Set log target. See systemd.log_target above.
systemd.log_color, systemd.log_level=, systemd.log_location,
09.11.2020 19:09, Lennart Poettering пишет:
> On Mo, 09.11.20 08:48, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
>> Is it possible to query configuration options in effect in running
>> journald instance?
>
> Besides the brief log output it does itself, no there's cur
Is it possible to query configuration options in effect in running
journald instance?
Background - when user asks question about journald, the first
information is current settings (like whether persistence is enabled or
not). It needs fetching files from multiple places which varies between
25.10.2020 20:36, Marcin Kocur пишет:
> Hello,
>
> as the topic states, I want to know which action(s) from "add",
> "remove", "change", "move", "online", "offline", "bind", and "unbind"
> were triggered on my device. Is there any way to check that?
>
> At the beginning of
16.10.2020 18:51, Lennart Poettering пишет:
>>
>> Ths btrfs udev rule file appears to be missing in the initrd. The
>> block devices with the btrfs file systems on them will thus be marked
>> ready in systemd instantly instead of being delayed until all other
>> devices of the same btrfs fs have
14.10.2020 15:23, Thomas HUMMEL пишет:
>
>
> On 14/10/2020 13:24, Andrei Borzenkov wrote:
>> On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL
>> wrote:
>>>
>>> Hello,
>>>
>>> thanks for your answer. It's getting clearer.
>>
On Wed, Oct 14, 2020 at 11:42 AM Thomas HUMMEL wrote:
>
> Hello,
>
> thanks for your answer. It's getting clearer.
>
> Still : why would the user crond runs on behalf of needs to be allowed
> in access.conf to access the systemd-user service ?
> My understanding is that the user@.service creation
11.10.2020 23:57, Chris Murphy пишет:
> Hi,
>
> A Fedora 32 (systemd-245.8-2.fc32) user has a 10-drive Btrfs raid1 set
> to mount in /etc/fstab:
>
> UUID=f89f0a16- /srv btrfs defaults,nofail,x-systemd.requires=/
> 0 0
>
> For some reason, systemd is trying to mount this file system before
On Tue, Sep 22, 2020 at 2:53 PM Mantas Mikulėnas wrote:
>
> On Tue, Sep 22, 2020 at 1:46 PM Andrei Borzenkov wrote:
>>
>> On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
>> >
>> > Hi all,
>> >
>> > When I use Fedora image as rootfs on X
On Tue, Sep 22, 2020 at 1:35 PM ZhouPeng wrote:
>
> Hi all,
>
> When I use Fedora image as rootfs on Xilinx PYNQ-Z2, I encountered the issue
> when use the /dev/ttyPS0.
> I think the issue is because systemd and udev on fedora can didn't detect
> ttyPS0 properly. Do I need to install any other
09.09.2020 00:54, Alvin Šipraga пишет:
> Hi,
>
> On 9/8/20 4:12 PM, Colin Guthrie wrote:
>
>> 2. Set your /etc/ master image to make /etc/localtime to be a symlink to
>> /run/localtime and then ensure /run/localtime is a symlink to the
>> appropriate file in /usr during early boot (e.g. in
05.09.2020 01:05, Lennart Poettering пишет:
>
> I explained this already. DNS server data today is much less config
> than state, acquired dynamically via DHCP, hence most distros don#t
> configure it in /etc so much anymore, but manage it in /run (where
> transient state is generally kept), and
28.08.2020 17:47, Tom Browder пишет:
> I want to create a service file that has to consider other services. I have
What does it mean?
> looked at the man pages and probably don't have enough life expectancy to
> properly grok them.
>
If you tell us what you try to achieve, someone may have an
27.08.2020 19:11, u...@net9.ga пишет:
> Consider
>
> [Unit]
> Description=Is it looking for ${} construct in the wrong place?
> [Service]
> Type=oneshot
> ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str;
> exit 0;'
>
> When ran, the journal has:
>
> bash[14190]: +
23.08.2020 09:34, Andrii Zymohliad пишет:
> Hello! I've lost the ability to log in to my systemd-homed user account. I
> would be very grateful for any help!
>
> If I log in as root and try to authenticate:
>
> # homectl authenticate azymohliad
>
> Then after typing my password I get the
23.08.2020 15:34, Andrii Zymohliad пишет:
>> Here is the log after authentication attempt:
>> https://gitlab.com/-/snippets/2007113
>> And just in case here is the full log since boot:
>> https://gitlab.com/-/snippets/2007112
>
> Sorry, links are broken, re-uploaded:
>
> Authentication part:
23.08.2020 09:34, Andrii Zymohliad пишет:
> Hello! I've lost the ability to log in to my systemd-homed user account. I
> would be very grateful for any help!
>
> If I log in as root and try to authenticate:
>
> # homectl authenticate azymohliad
>
> Then after typing my password I get the
20.08.2020 18:55, Shravan Singh пишет:
> Hello,
> I have raspberry-pi cm3 which is running an embedded yocto poky linux
> warrior branch with mender.
>
> I have made my rootfs as read-only because of which I am not able to use
> timedatectl to change the system time zone.
>
> I was looking
15.08.2020 23:56, Reindl Harald пишет:
> is it a bug or a concept issue that it's mounted fpr root instead auf
> the user given with uid or is there just a param i am not aware mising?
>
allow_other
how is it relevant to systemd?
> there are 20 mountpoints of that style and automount would be
13.08.2020 09:54, Harald Dunkel пишет:
> On 8/12/20 2:16 PM, Andrei Borzenkov wrote:
>> 12.08.2020 14:03, Harald Dunkel пишет:
>>> See attachment. Hope this helps
>>> Harri
>>
>>
>>> 1 openat(AT_FDCWD,
>>> "/sys/fs/cgroup/un
12.08.2020 14:03, Harald Dunkel пишет:
> See attachment. Hope this helps
> Harri
> 1 openat(AT_FDCWD,
> "/sys/fs/cgroup/unified/system.slice/rsyslog.service/cgroup.procs",
> O_RDONLY|O_CLOEXEC) = 24
> 1 read(24, "0\n1544456\n", 4096)= 10
kernel returns "0" as process number in
12.08.2020 13:04, Harald Dunkel пишет:
> On 8/12/20 10:32 AM, Ulrich Windl wrote:
>>
>> As you found out the details already, maybe you could have added some
>> strace
>> output, especially after the kill() is returning...
>>
>
> See attachment. Hope this helps
Not really. We already know that
10.08.2020 20:59, Böszörményi Zoltán пишет:
> Hi,
>
> I have to use the same OS image tarball (created by Yocto)
> on several machines with different specifications.
>
> Where they differ is the disk size and partitioning. On the smaller
> machine (a Sicom SL20 POS hardware, boots from CF card)
09.08.2020 13:40, Vini Harimoorthy пишет:
> In that case, it will run only in Oct,Nov, & Dec. But, I want to run the
> timer unit weekly after a specific calendar date & time.
> How to specify if I want to run some task on every 12 hours after Jan'2021
> (start from future date & time)
>
That's
26.07.2020 22:56, Ian Pilcher пишет:
> My NAS has 16 MD RAID devices. I've created a simple service
> (raidcheck@.service) that will trigger a check of the RAID device
> identified by the argument. E.g., 'systemctl start raidcheck@md1' will
> trigger the check of md1 (after checking that no
12.07.2020 23:37, Uoti Urpala пишет:
> On Sun, 2020-07-12 at 17:13 +0300, Andrei Borzenkov wrote:
>> 12.07.2020 16:21, Amish пишет:
>>> I have a timer file like this:
>>>
>>> [Unit]
>>> Description=Foo
>>> After=multi-user.target
>
03.07.2020 12:09, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 20:48, Andrei Borzenkov wrote:
>
>
>> Once again - dependencies in systemd are between jobs, not between units.
>
> Ok. I may have missed some docs but I've read several man sections
> (likesystemd
12.07.2020 16:21, Amish пишет:
> Hello,
>
> This is a question out of curiosity and not currently any problem.
>
> I have a timer file like this:
>
> [Unit]
> Description=Foo
> After=multi-user.target
>
> [Timer]
> OnCalendar=*:0/5
> Persistent=false
>
> [Install]
> WantedBy=timers.target
>
02.07.2020 21:28, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 19:00, Andrei Borzenkov wrote:
>
>> After=syslog.socket will exist only if rsyslog.service is aliased to
>> syslog.service and your problem was when you removed this alias.
>
> Correct (I did miss this si
02.07.2020 18:57, Thomas HUMMEL пишет:
>
>
> On 02/07/2020 16:44, Andrei Borzenkov wrote:
>
>> This is common misunderstanding. Dependencies are between jobs, not
>> between units. Requires means systemd will submit additional job for
>> dependent unit - not
02.07.2020 16:09, Thomas HUMMEL пишет:
>
> [Unit]
> Requires=syslog.socket
>
> [Install]
> ;Alias=syslog.service
>
...
>
> # systemctl start rsyslog
> A dependency job for rsyslog.service failed. See 'journalctl -xe' for
> details.
>
> BUT rsyslog service (and daemon) are actually running:
>
27.06.2020 13:42, Mark Rogers пишет:
> On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
> wrote:
>> You should use Before=network-pre.target, Wants=network-pre.target.
>
> Thanks, tried that but still not working:
>
All other units that implement networking must have
18.06.2020 10:07, Kamal Rathi пишет:
>
> Now I am more eager to know if is it possible to run anything before it
> kills users processes at shutdown / reboot / halt.
User processes run either as part of user session or as part of user
service. The former is session-xxx.scope, the latter is
l started outside of rdbms.service. The
only process shown in your output is listener, but I would expect rather
more of Oracle there
Without logs it is impossible to say anything more specific.
> On Tue, Jun 16, 2020 at 12:23 AM Andrei Borzenkov
> wrote:
>
>> 16.06.2020 07:36, Ka
was giving the same results
> I am attaching debug logs .
>
dmesg output does not contain any systemd log. Anyway, we already know
that your services are not really system services.
> On Mon, Jun 15, 2020 at 10:34 AM Andrei Borzenkov
> wrote:
>
>> 15.06.2020 11:01, Kamal Rathi пишет
15.06.2020 11:01, Kamal Rathi пишет:
> Hi Team,
>
> I have two services which are dependent on each other and are working fine
> at boot up but at shutdown / reboot , the processes get killed as shutdown
> got initated.
>
> Services are running fine in particular order but processes got killed
On Thu, Jun 4, 2020 at 9:05 AM Ulrich Windl
wrote:
>
> But if so, why would it be started if that service is disabled?
Because "disabled" in systemd just means that links in the [Install]
section have not been created. It does not mean "this unit won't be
started under any circumstances".
...
28.05.2020 16:43, Ulrich Windl пишет:
> Hi!
>
> Monitoring the messages created when booting SLES12 SP5, I noticed these:
>
> ypbind-systemd-pre[1756]: \nError: NIS domain not specified.\n
> systemd[1]: ypbind.service: Control process exited, code=exited status=1
> systemd[1]: Failed to start
23.05.2020 11:56, Ede Wolf пишет:
>>
>> tw:~ # systemctl stop NetworkManager.service
>> tw:~ # ip l set dev enp0s5 down
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/use_tempaddr
>> 1
>> tw:~ # cat /proc/sys/net/ipv6/conf/enp0s5/addr_gen_mode
>> 1
>> tw:~ # echo 3 >
22.05.2020 22:17, Ede Wolf пишет:
> Am 22.05.20 um 17:58 schrieb Andrei Borzenkov:
>>>
>>> The problem is, that sysctl.conf is being executed before the interfaces
>>> get their eventual names.
>>>
>>
>> That sounds like actual bug. What sy
22.05.2020 15:44, Ede Wolf пишет:
> Hello,
>
> Thanks for replying. As I have written, I am using no custom .rules or
> .link file. /etc/udev/rules.d is empty and /etc/systemd/network only
> contains .network files.
>
This is irrelevant. *ANY* rule can set device name which will rename
17.05.2020 03:32, Michael Chapman пишет:
> On Fri, 15 May 2020, Frank Steiner wrote:
>> Hi,
>>
>> I need to run a script on shutdown before any other service is stopped.
>> Due to an advice Lennart gave a while ago I'm using this service file
>> (with multi-user.target being our default runlevel
16.05.2020 19:28, Frank Steiner пишет:
> Hi Andrei,
>
> Andrei Borzenkov wrote:
>
>> Can you reproduce it by simply running "systemctl daemon-reexec" without
>> any package update?
>
> Yes, indeed! This is enough to destroy the ordering for the next
15.05.2020 12:57, Thomas HUMMEL пишет:
>
> In other words : is it a bad practice to order a home made service
> before remote-fs-pre.target ?
>
Why would it be? The very reason remote-fs-pre.target was added is to
allow services to be reliably started before remote mounts.
15.05.2020 11:08, Frank Steiner пишет:
> Hi,
>
> I need to run a script on shutdown before any other service is stopped.
> Due to an advice Lennart gave a while ago I'm using this service file
> (with multi-user.target being our default runlevel target):
>
> [Unit]
> After=multi-user.target
>
>
13.05.2020 21:57, Thomas HUMMEL пишет:
> Hello,
>
> I'm using the xCAT (xcat.org) software to provision stateless HPC Centos
> 8.1 nodes. Via a systemd service called xcatpostinit1.service, it
> enables, at boot time, to run so called postscripts for, for instance
>
> - configure eth nic with a
On Wed, May 6, 2020 at 4:43 PM Lennart Poettering
wrote:
>
> On Mi, 06.05.20 13:03, Boyce, Kevin P [US] (AS) (kevin.bo...@ngc.com) wrote:
>
> > Ulrich,
> >
> > I just noticed that too. This seems rather restrictive given that one
> > could have a system with many drives, and with GPT it is not
On Wed, May 6, 2020 at 3:23 PM Boyce, Kevin P [US] (AS)
wrote:
>
> Good Morning List,
>
>
>
> Does anyone know how complicated of a regular expression can be utilized in a
> udev rule?
>
I would ask udev manual page :)
>
>
> For instance I have a system with a lot of drives (sda through z
05.05.2020 18:15, Thomas HUMMEL пишет:
> On 4/28/20 5:36 PM, Thomas HUMMEL wrote:
>
>> 3) regarding local-fs dans remote-fs targets : I'm not really sure if
>> any fits in either passive or active units.
>
> Hello again,
>
> regarding local-fs.target : is it legit for a custom service unit to
>
04.05.2020 00:03, Arian Van Putten пишет:
>
> My gut feeling the answer to this question is "not all initrd's use
> systemd; so they might not parse /sysroot/etc/fstab so early we need to
> account for that". Is that the case?
>
It is more "not every system uses initrd".
27.04.2020 08:43, Debraj Manna пишет:
Can someone let me know the following about systemd service shutdown
sequence
1.
If I have specified KillSignal=SIGTERM then how does this interact this
TimeoutStopSec ? Does this mean that during shutdown of service, first
SIGTERM will be
24.04.2020 16:57, John пишет:
> I'd like to have systemd (user mode) call a bash script with different
> tokens under two conditions:
> 1) When the user starts/stops a service (token would be either "sync"
> or "unsync")
> 2) When a timer tells it to run (token would be "sync")
>
> Thus far, I
13.04.2020 18:18, Tobias Brink пишет:
> Hello systemd devs and users,
>
> my internet connection is established by a router provided by my ISP (a
> Fritz Box to be precise). It can hand out delegated IPv6 prefixes via
> DHCPv6. I use a Linux box in between this router and my internal network
> to
13.04.2020 20:04, Andrei Borzenkov пишет:
>
> Huh? You seem to misunderstand configuration. End host networkd knows
> nothing about prefix delegation, it gets its configuration from CPE router.
>
Oops, ignore this. Sorry, my fault.
___
s
13.04.2020 18:26, Kevin P. Fleming пишет:
> This is a bit tricky, since RAs and prefix delegation are not really
> related. What you have described is proper behavior on the 'upstream'
> link side; when networkd sees the RA with the new prefix, and the
> lifetime of the old prefix set to zero, it
23.03.2020 14:15, Kevin P. Fleming пишет:
> Input files for systemd-networkd are not systemd unit files, so
> there's a good chance that the rules for finding and processing them
> are much simpler. That would explain why template/instance files don't
> work.
>
> The manpage for systemd.network
19.03.2020 19:47, Paul Menzel пишет:
> Dear systemd folks,
>
>
> I am using Debian Sid/unstable with systemd 245.2 and Weston 8.0.0.
>
> I amtrying to start a graphical desktop as soon as possible. Currently,
> I use Weston, but unfortunately accessing `/dev/dri/card0` it gets a
> permission
13.03.2020 11:19, Mantas Mikulėnas пишет:
> On Fri, Mar 13, 2020 at 10:03 AM Thomas Blume wrote:
>
>> Hi,
>>
>> I have a SUSE SLES system where system root is provided via iscsi firmware
>> (ibft).
>> The installer automatically adds the _netdev parameter to the system root
>> mount.
>> The
12.03.2020 12:10, Ani A пишет:
> Hello,
>
> I am on Ubuntu 18.04.2, and I have systemd version 237. I have some common
> tasks
> which need to happen prestart and poststop which I have moved to a
> script. All unit
> files look like:
>
> StandardOutput=file:/var/log/my-.log
>
22.02.2020 22:50, jay.bur...@fujitsu.com пишет:
> All,
>
> Referring to my last email regarding the systemd shutdown behavior. I am
> working on the assumption that the idea of honoring the first shutdown request
> is the preferred way to go. If not this email can be ignored.
>
> I have
28.01.2020 21:46, Johannes Ernst пишет:
> Is there a best practice for scheduling .timers based on what happened in a
> previous run?
>
> Pseudocode:
>
> while( true ) :
> delta = runService();
> sleep( delta );
>
> I can think of …
>
> 1) run the job frequently, but skip the bulk of
24.01.2020 06:56, Alexander E. Patrakov пишет:
>>
>> I assume users want their login passphrase to use local characters.
>
> That's just an assumption, with no data presented to back it up.
>
I have seen enough cases when users memorized Russian passwords and
entered ASCII characters based on
15.01.2020 10:14, Ulrich Windl пишет:
>>>> Andrei Borzenkov schrieb am 14.01.2020 um 20:08 in
> Nachricht :
>> 14.01.2020 10:57, Ulrich Windl пишет:
>>> Hi!
>>>
>>> I see the message
>>> systemd[1]: nss-lookup.target: Dependency Befo
14.01.2020 10:57, Ulrich Windl пишет:
> Hi!
>
> I see the message
> systemd[1]: nss-lookup.target: Dependency Before=nss-lookup.target dropped
> several times, wondering:
>
> Does it say "nss-lookup.target" has a dependency "Before=nss-lookup.target"
> that was dropped, or is the first argument
04.01.2020 20:58, Georg Großmann пишет:
> Has this issue been fixed on either systemd or on BTRFS side in the
> meantime?
No. Each project says that from its side there is nothing to fix.
> I am currently testing a BTRFS raid1 with two disk in my
> virtualbox. I have installed a bootloader on
31.12.2019 08:34, Kamal Rathi пишет:
> Hi Git-Hub Mailing List,
>
> I am designing a stop service which has to be run before the kill of user's
> scope / session .
> As the reboot or shutdown are being initiated the systemd kill all the
> users which are in user's.slice
> before the script ran so
09.12.2019 10:06, Ulrich Windl пишет:
>>
>> After real root is mounted daemon-reload re-runs fstab generator which
>> parses real root /etc/fstab and may pull mount points from it.
>
> I wonder: Are there realistic cases when the fstab in initrd is newer than the
> fstab in the root file system?
09.12.2019 01:23, Colin Walters пишет:
>
>
> On Sun, Dec 8, 2019, at 5:20 PM, Colin Walters wrote:
>>
>>
>> On Fri, Dec 6, 2019, at 12:53 PM, Andrei Borzenkov wrote:
>>
>>> After real root is mounted daemon-reload re-runs fstab generator which
>>
05.12.2019 17:31, Colin Walters пишет:
> See https://github.com/coreos/ignition-dracut/pull/140
>
> Basically, we do a lot of nontrivial stuff in the initramfs (Ignition) and
> this was re-starting some of our units, which I found surprising.
>
> The behavior seems to have come from
>
25.11.2019 16:19, Mantas Mikulėnas пишет:
On Mon, Nov 25, 2019 at 3:13 PM Jörg Weinhardt wrote:
Hi,
the behavior of systemd is not quite clear to me:
I have a service which requires another service to be started and running,
so I use a Requires= dependency to the required service.
But if the
15.09.2019 6:12, Daniel Duong пишет:
> Hi,
>
> I have a 2 template units: 1 for a service and 1 for a socket. Each
> instance is a version of my web application.
>
> After a successful deploy, I stop and disable the old version and I
> enable the new one:
> systemctl start
1 - 100 of 734 matches
Mail list logo
