On 08.05.2022 20:19, Kamil Jońca wrote:
> I have question about custom options in network interface definitions
> and passing it via command line.
> In currend Debian tools
>
> (https://manpages.debian.org/buster/ifupdown/interfaces.5.en.html)
> there is a possibility to define custom option and
github.com/x-yuri/b12e8178a621372a4aa62c60693af37b#file-b-journal-gnome-keyring-gist-md
>
> Do you know any reason a process can remain alive after exit() or
> return from main()? Any threads started by PAM or anything
> dbus-related (wild guesses on my part)? Anything else I can che
On 05.05.2022 04:41, Yuri Kanivetsky wrote:
> Hi,
>
> This might be not a systemd issue. But the behavior is weird, and I'm not
> sure.
>
> I'm trying to run GNOME in a docker container. And gnome-keyring fails to
> start:
>
> https://gist.github.com/x-yuri/c3c715ea6355633de4546ae957a66410
>
On 28.04.2022 10:54, Lennart Poettering wrote:
>
>> * systemd-boot is an additional bootloader, rather than replacing
>> an existing one, thus increasing the attack surface.
>
> Hmm, what? "additional bootloader"? Are they suggesting you use grub
> to start sd-boot? I mean, you certainly could
On 08.04.2022 23:35, Nick Howitt wrote:
> Sorry, for the delay. Big internet outage.
>
> On 08/04/2022 15:15, Andrei Borzenkov wrote:
>>
>> On 08.04.2022 14:54, Nick Howitt wrote:
>>> Hi,
>>> I apologise if this is not the right place for user help. If it
On 08.04.2022 14:54, Nick Howitt wrote:
> Hi,
> I apologise if this is not the right place for user help. If it is not,
> please point me to the best place.
>
> I am trying to start a service (clearshare-scheduler) when another
> service (siad) starts. Clearshare-scheduler is an odd service.
On 17.03.2022 14:15, Ulrich Windl wrote:
>>>> Andrei Borzenkov schrieb am 17.03.2022 um 12:08 in
> Nachricht
> :
>> On Thu, Mar 17, 2022 at 12:32 PM Ulrich Windl
>> wrote:
>>>
>>> Hi!
>>>
>>> When reading the manual page s
On Thu, Mar 17, 2022 at 12:32 PM Ulrich Windl
wrote:
>
> Hi!
>
> When reading the manual page systemd.unit(5), I'm not quite sure what the
> difference between AssertPathExists and ConditionPathExists is:
>
> (Condition)
> If the specified absolute path name does not exist, the condition will
On Wed, Mar 9, 2022 at 10:18 AM Michael Biebl wrote:
>
> Am Mi., 9. März 2022 um 06:49 Uhr schrieb Andrei Borzenkov
> :
> >
> > On 09.03.2022 00:59, Michael Biebl wrote:
> > > Hi,
> > >
> > > I need help with firewalld issue, specifically
> &g
On 09.03.2022 00:59, Michael Biebl wrote:
> Hi,
>
> I need help with firewalld issue, specifically
> https://github.com/firewalld/firewalld/issues/414
>
> the TLDR: both firewalld.service and cloud-init-local.service hook
> into network-pre.target and have a Before=network-pre.target ordering.
>
On 08.03.2022 18:20, Manuel Wagesreither wrote:
> Hi all,
>
> Am Do, 3. Mär 2022, um 19:02, schrieb Lennart Poettering:
>> On Mi, 02.03.22 17:50, Lennart Poettering (lenn...@poettering.net) wrote:
>>
>>> That said, we could certainly show both the comm field and the PID of
>>> the offending
On 24.01.2022 17:37, Tomáš Hnyk wrote:
>
>
> On Monday 24. January 2022, 13:50:48 (+01:00), Andrei Borzenkov wrote:
>
I posted it in response to the list and you sent personal reply. Please use
reply to all.
>> On Mon, Jan 24, 2022 at 1:14 AM Tomáš Hnyk wrote:
>>&g
On Mon, Jan 24, 2022 at 1:14 AM Tomáš Hnyk wrote:
>
> Hello,
> I have my computer hooked up to an AVR that runs my home cinema and ideally I
> would like the computer to turn off the AVR when I turn it off or suspend it.
> The only way to do this is over network and I wrote a simple script that
On 23.01.2022 19:42, Wols Lists wrote:
> This is probably a classic "need a clue" problem ... my system has
> suddenly stopped booting properly, and I guess it's a problem with my
> custom systemd service.
>
> Basically, I've configured my raid device on top of dm-integrity, so
> that needs to
On Tue, Jan 4, 2022 at 4:53 PM Harald Dunkel wrote:
>
> Hi folks,
>
> after the upgrade from Buster to Bullseye (including the migration from
> sysv init to systemd) the network interface names were messed up on
> several hosts. Apparently udev stumbles over a naming conflict:
>
> # journalctl -b
Running with debig log level may give some more hints.
>
> Best Regards,
>
> Christopher Wong
>
> ____
> From: systemd-devel on behalf
> of Andrei Borzenkov
> Sent: Monday, December 20, 2021 1:27:42 PM
> To: systemd-devel@lists.freed
On 20.12.2021 15:06, Christopher Wong wrote:
> # /etc/systemd/system/iris-detection.service
> After=temperature-controller.service
>
> # /usr/lib/systemd/system/temperature-controller.service
> After=iris-detection.service
This is loop and systemd is free to break it by ignoring some dependency.
On 08.12.2021 08:35, Prashantkumar dhotre wrote:
> Hi,
> Is there a batching of service stops by systemd during shutdown.
> In journal logs, I see a batch of 40 odd 'Stopping' messages and then the
> next batch is seen after few seconds (4-6 seconds)
> Is this by design ?
> I am looking for a
On 02.12.2021 23:39, Ian Pilcher wrote:
> I.e., how does it determine that a particular interface is an on-board
> interface, and how does it determine the "number" of such an interface?
>
> Thanks!
>
It is looking at sysfs attributes (acpi_index, index and some others). Details
are in
On 01.12.2021 17:20, Brian Hutchinson wrote:
> Hi,
>
> I'm on embedded imx8 mm platform and trying to order services such that
> ptp4l (LinuxPTP) is started after a bond is created between two DSA network
> interfaces on my Microchip Ethernet Switch.
>
> No matter what I try with BindsTo,
On 18.11.2021 03:20, Brian Hutchinson wrote:
> Yet another update, I was able to get it working .. but feel like it is a
> hack so comments welcome ... see below:
>
> On Wed, Nov 17, 2021 at 12:26 AM Brian Hutchinson
> wrote:
>
>> Update below
>>
>> On Tue, Nov 16, 2021 at 2:27 PM Brian
On 29.10.2021 19:24, Han wrote:
> I have a follow-up question inline. Thanks.
>
> On Thu, Oct 28, 2021 at 10:47 PM Han wrote:
>
>>
>> On Thu, Oct 28, 2021 at 10:25 PM Andrei Borzenkov
>> wrote:
>>
>>> On 29.10.2021 04:54, Han wrote:
>>>
On 29.10.2021 04:54, Han wrote:
> Hi,
>
> I'm a newbie to systemd. I encountered a strange problem when using
> systemd user
> service in Debian 10 (hardware: Raspberry Pi 4), systemd version 241.
>
> I posted this question on stackoverflow but didn't get answers yet. Hence
> trying to ask here.
On 18.10.2021 23:08, Silvio Knizek wrote:
> Am Montag, dem 18.10.2021 um 12:43 -0700 schrieb Kenneth Porter:
>> I just installed the new-to-EPEL ndppd service and am seeing this in my log:
>>
>> Oct 17 21:10:08 saruman systemd: Can't open PID file
>> /var/run/ndppd/ndppd.pid (yet?) after start: No
On Wed, Sep 22, 2021 at 9:27 AM wrote:
>
> Now that the operation of flush can be done automatically when you switch
> from Storage=volatile to #Storage=volatile, why do we still need journalctl
> --flush?
>
To switch from volatile storage to persistent storage on boot as
explained in the man
On 15.09.2021 18:15, Manuel Wagesreither wrote:
> Hello all,
>
> I'm onboarding some collegues who don't have much experience with systemd.
> One thing I would like to focus on is the difference between Before=/After=
> and Wants=/Requires=/BindsTo in systemd units.
>
> I think it would get
On 01.09.2021 14:39, Manuel Wagesreither wrote:
> Am Mi, 25. Aug 2021, um 18:51, schrieb Andrei Borzenkov:
>> On Wed, Aug 25, 2021 at 3:44 PM Andrei Borzenkov wrote:
>> ...
>>>> Here's the udev rule:
>>>> ```
>>>> ACTION=="add", SUBSYS
On 02.09.2021 15:10, Leon Fauster wrote:
> On 02.09.21 08:00, Andrei Borzenkov wrote:
>> On 02.09.2021 01:19, Leon Fauster wrote:
>>> Example:
>>>
>>> a@.service
>>> b.service
>>>
>>> a@.service is started as a@host1.service and b
On 02.09.2021 01:19, Leon Fauster wrote:
> Dear list,
>
> following requirement exists here (systemd-239 installed):
>
> Applying a "Requires" statement with an instantiated service.
>
> Example:
>
> a@.service
> b.service
>
> a@.service is started as a@host1.service and b.service must be
On Wed, Aug 25, 2021 at 3:44 PM Andrei Borzenkov wrote:
...
> > Here's the udev rule:
> > ```
> > ACTION=="add", SUBSYSTEMS=="usb", SUBSYSTEM=="block", KERNEL=="*[0-9]*",
> > ENV{ID_FS_USAGE}=="filesystem", TAG+=&qu
On Wed, Aug 25, 2021 at 2:26 PM Manuel Wagesreither wrote:
>
> Hello all,
>
> this is my first post on this mailing list and, first of all, I'd like to
> thank you and appreciate your work on systemd in general. I admire the logic,
> the completeness of the manpages and in general how
On 16.08.2021 18:20, Gildas Bayard wrote:
> Hello,
>
> I've first posted on stackoverflow but couldn't get any usefull answer
> (gomenasai )
>
> I'm trying to start a task when bluetooth is ready on a raspi (running
> raspbian 10 - buster) with systemd. I've added the file
>
On 13.08.2021 15:13, George Avrunin wrote:
> On Fri, 13 Aug 2021 08:05:29 +0200, Ulrich Windl wrote:
>
>>> I suppose that's possible, though I haven't been able to find anywhere
>>> that's configured. (I'll ask again on the Fedora list to be sure.) In
>>> the places where I know I've manually
On 12.08.2021 00:11, George Avrunin wrote:
> Hello,
>
> As a result of a major power outage and consequent issues with some
> switches, my office workstation, a Dell Precision T1700 running
> fully-updated Fedora 34, was off the network for most of last weekend. As
> our department IT staff
On Tue, Aug 3, 2021 at 1:28 PM Ulrich Windl
wrote:
> Thanks for having a look! So it seems not as broken as I was afraid.
> You are right that the service was written for inetd originally, and one of
> the problems found with systemd is that the process ends with varying exit
> codes (mostly 1
On 17.07.2021 22:22, Debraj Manna wrote:
>
> Should not unmasking and starting a service also make it enabled?
>
No. Starting/stopping, enabling/disabling and masking/unmasking are
orthogonal operations.
___
systemd-devel mailing list
On 17.07.2021 03:36, Ed Greshko wrote:
> Hi,
>
> This may be an "uninformed" question since I've not done much with systemd.
>
> Is there a way for a service or unit to be aware if the environment is
> Bare Metal or a Virtual Machine.
>
> For example, a unit is triggered by a user logging in as
On Tue, Jul 13, 2021 at 4:06 PM Andrei Borzenkov wrote:
>
> On Tue, Jul 13, 2021 at 3:46 PM Manuel Wagesreither
> wrote:
> >
> > Hi all,
> >
> > when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
> > another.service with
On Tue, Jul 13, 2021 at 3:46 PM Manuel Wagesreither wrote:
>
> Hi all,
>
> when I have an udev rule with an ENV{SYSTEMD_WANTS}+="my.service", and
> another.service with After=systemd-udevd.service, can I at system boot rely
> on my.service to be already run when another.service starts?
>
No.
On 08.07.2021 18:33, Andreas Krueger wrote:
> Hi Folks,
>
> For my customer I have to verify the logger in its system, which is journald
> (241). For that I have written some tests that should verify if expired
> messages will been thrown out of the log. As you can see, the configuration
> is
On 19.06.2021 11:00, Norbert Lange wrote:
>>
>> What you could try is creating a new unit in /etc/systemd/system/
>> --- systemd-reload.service ---
>> [Unit]
>> Description=Reload systemd
>> Requires=usr-local.mount
>> After=usr-local.mount
>>
>> [Service]
>> Type=oneshot
>>
On 18.06.2021 20:48, Norbert Lange wrote:
> Am Fr., 18. Juni 2021 um 16:35 Uhr schrieb Silvio Knizek
> :
>>
>> Am Freitag, dem 18.06.2021 um 15:04 +0200 schrieb Norbert Lange:
>>> Hello,
>>>
>>> I have an extra mount for /usr/local (Tools + Services which are just
>>> useful for development),
On 21.05.2021 17:07, Benjamin Berg wrote:
> Hi,
>
> On Fri, 2021-05-21 at 15:25 +0300, Andrei Borzenkov wrote:
>> systemd offers MemoryLow for an individual units. It actually sets
>> memory.low cgroup attribute, so this is OK. The problem is according to
>> kern
On 21.05.2021 18:18, lejeczek wrote:
> Hi guys.
>
> While surfing the web for answers I thought I would try to call on
> experts - how, if possible at all, to make systemd service unit depend
> on users' unit/services?
>
No, it is not possible. Nor is it really possible in reverse direction.
systemd offers MemoryLow for an individual units. It actually sets
memory.low cgroup attribute, so this is OK. The problem is according to
kernel dcouemtation, memory.low is limited by value set in parent cgroup
and all parent cgroups have memory.low=0:
On 16.05.2021 14:07, Manuel Reimer wrote:
> Hello systemd-devel list,
>
>
> according to the changelog of udev, it should be possible to clear TAGs
> using "TAG-=" since systemd 217:
>
> https://cgit.freedesktop.org/systemd/systemd/tree/NEWS?id=v217#n70
>
> But either I'm completely failing
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
1 - 100 of 780 matches
Mail list logo
