15.05.2019 23:21, Jeffrey Walton пишет:
> I have a systemd timer that starts a service, and the service executes
> a script that downloads data files once a day. Once the data files are
> retrieved I don't need the timer for the remainder of the day.
> However, I need the time again the next day.
03.06.2019 10:15, Ulrich Windl пишет:
Michael Chapman schrieb am 31.05.2019 um 13:28 in
> Nachricht :
>> On Fri, 31 May 2019, Reindl Harald wrote:
>>> Am 31.05.19 um 12:31 schrieb Michael Chapman:
For RPM on Fedora, the systemd package has %transfiletriggerin and
13.06.2019 11:11, Josef Moellers пишет:
> On 12.06.19 17:34, Andrei Borzenkov wrote:
...
>>
>> If I add pam_keyinit to systemd-user, I do get session keyring for gnome
>> terminal, but this is really wrong one:
>>
>> bor@10:~> cat /proc/keys
>> 2133e4
14.06.2019 17:13, Germano Massullo пишет:
> I have two different options at the moment, and I would like to ask
> you for a feedback.
>
>
> A file
>
> /usr/lib/udev/rules.d/01-boinc-gpu-plugged.rules
>
> containing
>
> ACTION=="add", SUBSYSTEM=="drm", RUN+=systemctl --no-block restart
>
24.06.2019 17:41, Conrad Hoffmann пишет:
> Hi,
>
> TL;DR: I was wondering what happens if a unit executed early during the
> boot process changes the current dependency graph by either enabling or
> even starting another unit that was previously disabled. Is this defined
> behaviour, and if so
12.06.2019 19:18, Simon McVittie пишет:
> On Wed, 12 Jun 2019 at 18:34:30 +0300, Andrei Borzenkov wrote:
>> Technically this is probably correct - session keyring lifetime is
>> exactly that - session, and systemd-user lifetime is independent of
>> individual (GUI) l
11.06.2019 15:32, Josef Moellers пишет:
> On 11.06.19 13:27, Mantas Mikulėnas wrote:
>> On Tue, Jun 11, 2019 at 1:58 PM Josef Moellers
>> The point is that in the gnome-terminal case, pam_keyinit.so is not
>> involved.
>>
>>
>> It is. The systemd --user instance (from which dbus-daemon
09.05.2019 13:25, Ulrich Windl пишет:
> Hi!
>
> I'm developing a service and getting the status of my target gives:
> ● iotwatch.target
>Loaded: not-found (Reason: No such file or directory)
>Active: active since Thu 2019-05-09 12:00:56 CEST; 18min ago
>
> I guess it's not a file named
09.05.2019 12:49, Olaf Hering пишет:
> With ifcfg or NetworkManager it is possible to have generic config files for
> every system to configure a bridge on the one and only physical network
> interface. See the examples below how such configuration looks like.
>
> With systemd-networkd it is
09.05.2019 13:22, Ulrich Windl пишет:
> Hi!
>
> I had to subscribe to this list, even though I'm no systemd fan. Still I'll
> have to deal with it as the distribution we use switched to systemd...
>
> I'm porting my LSB code to systemd, and I'm having some trouble. Cause of the
> trouble (and
14.05.2019 16:39, Ulrich Windl пишет:
> Hi!
>
> Developing my first systemd service I have some problems I don't understand:
> After installation, I get this status:
> # systemctl status iotwatch.target ● iotwatch.target - iotwatch I/O
> performance monitor
>Loaded: loaded
On Tue, May 14, 2019 at 9:35 AM Ulrich Windl
wrote:
>
> I knew that. It doesn't answer _why_ /var/run is obsolete.
>
/var/run needs /var which is not guaranteed to be there when you need
it which complicates things.
___
systemd-devel mailing list
On Wed, May 15, 2019 at 9:01 AM Ulrich Windl
wrote:
>
> >>> Andrei Borzenkov schrieb am 14.05.2019 um 20:21 in
> Nachricht :
> > 14.05.2019 16:39, Ulrich Windl пишет:
> >> Hi!
> >>
> >> Developing my first systemd service I have some problems I
On Thu, May 23, 2019 at 11:56 AM Ulrich Windl
wrote:
>
> Hi!
>
> After seeing that systemd generators are run as the very first step in
> systemd's life (deduced from the timestamps), I quit the idea of using them,
> and started to use another sort of generator:
>
> I have a generator target,
On Tue, May 21, 2019 at 10:50 AM Ulrich Windl
wrote:
>
> >>> Andrei Borzenkov schrieb am 20.05.2019 um 19:07 in
> Nachricht <4d103eef-d000-c9b2-9f7a-e0cda8ed6...@gmail.com>:
> > 20.05.2019 16:36, Ulrich Windl пишет:
> >> Hi!
> >>
> >&
On Mon, May 20, 2019 at 10:08 AM Mantas Mikulėnas wrote:
>
> On Sun, May 19, 2019 at 9:50 PM Alex Ivanov wrote:
>>
>> Hello.
>> What is the proper way to do that? I have a unit that creates gvt device in
>> the system
>>
>> ExecStart = "sh -c 'echo a297db4a-f4c2-11e6-90f6-d3b88d6c9525 >
>>
20.05.2019 16:36, Ulrich Windl пишет:
> Hi!
>
> I have had the effect that a "systectl status" before and after a
> "daemon-reload" is different, while the service in question wasn't restarted:
>
...>
> Is that intentional?
>
daemon-reload is known to lose state for years. Some problems get
On Wed, May 15, 2019 at 12:17 PM Lennart Poettering
wrote:
> >
> > To me it's the most horrible part of systemd: Messing with
> > symlinks...
>
> You should never need to. For all relevant operations there are
> "systemctl" verbs, i.e. "systemctl enable", "systemctl disable",
> "systemctl
On Wed, May 15, 2019 at 12:29 PM Lennart Poettering
wrote:
>
> On Mi, 15.05.19 12:25, Andrei Borzenkov (arvidj...@gmail.com) wrote:
>
> > On Wed, May 15, 2019 at 12:17 PM Lennart Poettering
> > wrote:
> > > >
> > > > To me it's the most horrible p
On Wed, May 15, 2019 at 12:04 PM Ulrich Windl
wrote:
>
> Hi!
>
> When I tried to put the instances of my service into a specific slice (by
> only specifying the name), I just got an error message.
>
> I had:
> [Service]
> Slice=something
>
> in the service unit file.
Works here
07.05.2019 4:22, Matt Zagrabelny пишет:
> Greetings,
>
> I'm using Debian Buster with systemd 241-3.
>
> I have a computer (server) that is running isc-dhcpd and I have a hardwired
> interface with static addressing on the computer:
>
> $ cat /etc/systemd/network/eth-router.network
> [Match]
>
02.08.2019 23:24, Johannes Ernst пишет:
> I have a oneshot .service (certbot) that is run by its .timer with:
>
> OnCalendar=daily
> RandomizedDelaySec=1day
>
> I also have a sometimes long-running script that may modify the same data. So
> the script and the oneshot service should never run at
28.08.2019 11:38, Ulrich Windl пишет:
>
> Some design concepts in systemd are just insane, the fstab issue being a good
> example for that.
>
The problem is that systemd is used to do things it was never intended
to do.
systemd was created to do one and only one single task - start static
25.08.2019 19:57, Hans-Dieter Doll пишет:
> On shutdown we need to stop a service before systemd begins to kill all
> processes it does not know.
> The service is a process supervisor similar to init, which controls all our
> applications.
> Our applications must be terminated by this
27.08.2019 18:55, Tony Rodriguez пишет:
> Interesting that you mentioned the following. I actually added logic to
> do something like this early yesterday. Will discuss with my team to
> see if this is good enough. I'd rather not bypass _netdev either. Feels
> like I am re-eventing the wheel. I
27.08.2019 14:34, Lennart Poettering пишет:
> be able to get away with adding a drop-in to
> /etc/systemd/system/session-.scope.d/50-order.conf or so which just
Thanks for the reminder, I completely forgot about this feature.
___
systemd-devel mailing
25.07.2019 15:14, Frank Steiner пишет:
> All mount units
> for NFS filesystems created from fstab get "Before=remote-fs.target",
> so they are shutdown before the network goes down.
>
This conslusion is absolutely wrong. Before=remote-fs.target does not
(and cannot) order unit shutdown *before*
29.07.2019 9:38, Ulrich Windl пишет:
Ulrich Windl schrieb am 29.07.2019 um 08:23 in Nachricht <5D3E90D1.4EC :
161 :
> 60728>:
> Frank Steiner schrieb am 25.07.2019 um
> 14:14 in
>> Nachricht <913a3c04-a666-b44b-c6ec-fe3d8a7fe...@bio.ifi.lmu.de>:
>>> Ulrich Windl wrote:
>>>
13.11.2019 18:20, Michael Biebl пишет:
> Hi,
>
> with v243 I get the following warning in my journal:
>
> Nov 13 15:38:12 pluto systemd-udevd[319]:
> /lib/udev/rules.d/90-libgpod.rules:19 IMPORT key takes '==' or '!='
> operator, assuming '==', but please fix it.
> Nov 13 15:38:12 pluto
12.11.2019 13:52, Belisko Marek пишет:
> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
> wrote:
>>
>> On Mo, 11.11.19 13:33, Belisko Marek (marek.beli...@gmail.com) wrote:
>> 65;5802;1c
>>> Hi,
>>>
>>> I'm using systemd 234 (build by yocto) and I've setup automount of
>>> sdcard in fstab.
16.11.2019 13:54, Mantas Mikulėnas пишет:
> On Sat, Nov 16, 2019 at 11:54 AM Michael Biebl wrote:
>
>> Am Sa., 16. Nov. 2019 um 09:20 Uhr schrieb Andrei Borzenkov
>> :
>>>
>>> Likely result of mass-rewrite in
>>>
>>> commit 25de7aa7b9
04.11.2019 17:59, mmbella пишет:
> Hello,
>
> I apologize if this is not the appropriate list serve to post in
> however, I am having problems with a systemd service file not
> terminating a python script that intermittently hangs. I have tried
> other forums with no solution. The service script
20.11.2019 17:35, Belisko Marek пишет:
> Hi Andrei,
>
> On Sat, Nov 16, 2019 at 9:31 AM Andrei Borzenkov wrote:
>>
>> 12.11.2019 13:52, Belisko Marek пишет:
>>> On Mon, Nov 11, 2019 at 4:47 PM Lennart Poettering
>>> wrote:
>>>>
>>>>
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
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
>>
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?
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
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
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
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
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
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
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
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
>
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
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.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
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
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".
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
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
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
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
>
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
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
>
>
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
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
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
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
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
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
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
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
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
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
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.
>>
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:
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
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
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 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
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
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
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
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
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
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
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
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)
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:
>
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 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
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
>
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
>
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 пишет
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
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
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".
...
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
601 - 700 of 896 matches
Mail list logo
