0.91-8.fc31
>
> @fedora 94 k
> teamd
>
> x86_64 1.29-2.fc31
>
> @fedora282 k
> tigervnc-license
>
> noarch 1.9.0-7.fc31
>
> @fedora 18 k
> tigervnc-server-minimal
>
> x86_64 1.9.0-7.f
Having two networking systems running at once can cause all sorts
of problems, not sure if this is the issue here or why NM is still starting
but you can try using 'systemctl mask' on it to completely prevent it from
running.
On Fri, Nov 8, 2019, 7:37 PM Anthony Joseph Messina
wrote:
> I
s network devices as they appear; it can also
> create virtual network devices. This service can be especially useful
> to set up complex network configurations for a container managed by
> systemd-nspawn or for virtual machines. It also works fine on simple
> connections.
>
&g
I'm a bit confused, where is the error about networkd not being found
coming from? Do you want networkd on the host system or inside the
container? If the latter, what distro does the container run?
On Fri, Sep 27, 2019, 6:57 PM Douglas E. Hopley Jr.
wrote:
> Greetings - I hope this finds you
It's hard to say much given we don't actually know what symptoms you're
experiencing, but at a glance the PAM messages are more important and seem
to be saying that you're trying to log into an account that's expired.
On Mon, Sep 23, 2019, 4:13 PM Omar Tapia wrote:
> Hi everyone
> I'm a arch
Could you use systemd-tmpfiles to set up the symlinks? I know OSTree-based
distros often use it to initialize symlinks on the rootfs.
On Thu, Aug 1, 2019, 12:05 PM Quinn Mikelson
wrote:
> I work at a company who develops a number of semi-stateless systems. My
> current challenge is integrating
Random side note, I've always felt like it would be neat if there were some
system for updating portable services, maybe built on Flatpak or vanilla
ostree or OCI containers / podman...
On Tue, Jul 23, 2019, 11:00 AM Lennart Poettering
wrote:
> On Mo, 15.07.19 22:45, Thomas Meyer
t; Regards.
>
> (I think I will ask to coredump mailling list if you think It boring)
>
>
> Dorian ROSSE.
>
> Provenance : Courrier pour Windows 10
>
> De : Ryan Gonzalez
> Envoyé : Friday, May 24, 2019 5:28:12 AM
> À : systemd Mailing List; Dorian ROSSE
coredumpctl debug dbus-daemon
assuming it already crashed. M
-- Ryan
https://refi64.com/
On May 23, 2019, 12:16 PM -0500, Dorian ROSSE , wrote:
> Hello everybody,
>
>
> I went to follow this link : https://wiki.archlinux.org/index.php/Core_dump
>
> I readen also coredump is missing for systemd,
Hmm not sure exactly when the offline updates generator runs, but maybe the
symlink could be made in /sysroot? Then depending on how early the generator
runs, it might even still be on / if it's before the switchroot.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >>
Latter issue may be: https://github.com/systemd/systemd/issues/12131
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Thu, Apr 4, 2019, 9:07 AM Mike Gilbert wrote:
> I pushed this out to our unstable testers yesterday, and received
.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Fri, Mar 22, 2019, 6:49 AM Lennart Poettering
wrote:
> On Do, 21.03.19 20:19, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > Hello!
> >
> > I've come to reall
Hello!
I've come to really love using the sd-bus and sd-event APIs for lightweight
D-Bus access and event loops, and I'm sure I'm not the only one. The amount
of bindings to other languages for stuff like sd-bus. However, this
unfortunately doesn't work in a Flatpak environment, and building the
ennart Poettering
wrote:
> On Di, 29.01.19 23:31, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > It's donotreply-systemd-...@refi64.com though I had already subscribed
> it
> > to the mailing list with a temporary route to my own email and then
> turned
> > off receiving mess
Sawano >> everyone else
https://refi64.com/
On Tue, Jan 29, 2019, 2:53 AM Lennart Poettering On Mo, 28.01.19 11:11, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > From here everything looks good!
>
> From which email address will these mails come? I figure I should
> whitelist t
>From here everything looks good!
On Mon, Jan 28, 2019 at 7:39 AM Lennart Poettering
wrote:
> On Mo, 28.01.19 14:32, Lennart Poettering (lenn...@poettering.net) wrote:
>
> > On Sa, 26.01.19 16:56, Ryan Gonzalez (rym...@gmail.com) wrote:
> >
> > > I'll send you
Poettering
wrote:
> On Fr, 18.01.19 20:44, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > Okay, I created this:
> >
> > https://github.com/kirbyfan64/systemd-webhook
> >
> > and attached an image of what the messages look like. It receives new tag
> > event
All that sounds great! I'll get to work ASAP.
On Wed, Jan 16, 2019 at 12:46 PM Lennart Poettering
wrote:
> On Mi, 16.01.19 12:30, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > I'd love to do this!
>
> That'd be excellent! Thank you!
>
> > To be clear, it'd basic
I'd love to do this!
To be clear, it'd basically automatically send out a message on new
"freeze" tags and release?
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Wed, Jan 16, 2019, 12:22 PM Lennart Poettering On Mi, 16.01.19
What would a patch look like? A --user that instead saves it to the user's
active secret service?
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Wed, Nov 14, 2018, 9:44 AM Lennart Poettering On Mi, 14.11.18 11:38, Sietse van Zanen
FWIW Kubernetes also supports mounting files containing secrets, which I've
personally found to be easier to work with than environment variables.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On Tue, Nov 13, 2018, 11:20 PM Tomasz
For starters, none of these are errors, and they're only appearing because
you ran clamscan in verbose mode.
This is the systemd mailing list, for the discussion and development
of...systemd. This isn't a general-purpose support forum.
On Sun, Sep 16, 2018, 12:48 PM Dorian ROSSE wrote:
> in
You can run:
journalctl -b-1 -r
This will show the logs from the last boot (-b-1) in reverse (-r). You can
then scroll down a bit and see what services didn't stop on time.
In addition, during shutdown you can press Ctrl+Alt+Del 8 times within 2
seconds (much easier than it sounds) in order to
FWIW the systemd 239+ version of systemd-resolve --status is resolvectl
status.
On Wed, Sep 5, 2018, 9:40 AM wrote:
> systemd-resolved has a DBUS API, which is used by network configuration
> managers such as systemd-networkd and NetworkManager to set the hostname
> resolution -related
I recently filed this bug with flatpak-xdg-utils:
https://github.com/flatpak/flatpak-xdg-utils/issues/12
The TL;DR is that flatpak-spawn processes will cause systemd to wait for
the "stop job to complete" on shutdown.
Here's the systemd-relevant part: if I press Ctrl+Alt+Del 7 times, I *see*
the
Isn't it just "libudev", e.g. without the 1?
On Fri, Aug 31, 2018, 11:19 AM Sayeed hyder wrote:
> Thanks Reindl. Let me be a bit more specific. I am looking for the non-dev
> package. For example, for ubuntu and sles, I can do the followiing
>
> apt-get install libudev1 works
>
Fedora 29 should have 239, so I'm not sure how you're on 238...
That being said, pretty much any rolling release distro (e.g. Arch) should
have 239 by now.
On Tue, Aug 28, 2018, 9:15 PM Douglas E. Hopley Jr.
wrote:
> Greetings.
>
> I would like to work with portable services and have a
Maybe /tmp is getting cleared or unmounted first? What happens if you put
the script somewhere else?
On Mon, Aug 20, 2018, 6:48 PM Filipe Brandenburger
wrote:
> On Mon, Aug 20, 2018 at 4:00 PM Radoslaw Garbacz
> wrote:
> > Could you please advise me with regard to systemd configuration for
>
I believe the errors are based on errno:
http://www.virtsync.com/c-error-codes-include-errno
Return status 3 -> ESRCH -> No such process
On Thu, Aug 16, 2018, 6:27 AM Cecil Westerhof
wrote:
> The man page of systemctl says:
> On success, 0 is returned, a non-zero failure code otherwise.
>
Most likely, the permissions of *something* are messed up... It looks like,
in particular, the systemd user instance isn't starting.
What does 'systemd --user status' say?
On Fri, Aug 10, 2018, 11:01 PM Johannes Ernst
wrote:
> This is Arch. I boot the system, and ssh in as user “shepherd”.
This is basically a GRUB issue and has absolutely nothing to do with
systemd. Sometimes GRUB can be a little finnicky with the modules it loads
by default, and IME in can be really odd on UEFI systems.
In general, if you can, you should look into using a proper UEFI
bootloader, like rEFInd (which
Maybe you have some generators interfering?
https://unix.stackexchange.com/a/364787/117660
On July 20, 2018 8:23:30 PM Matt Zagrabelny wrote:
Ping?
Any ideas systemd masters?
Thanks!
-m
On Fri, Jul 6, 2018 at 3:54 PM, Matt Zagrabelny wrote:
Greetings,
I'm seeing some unexpected
The fastest any distro is going to get systemd would probably be from a
bleeding-edge distro (e.g. Fedora Rawhide). If you don't want you system to
be a disaster zone, though, Arch got systemd 237 just two weeks after release.
Fedora will push systemd releases with their new versions, which
On Thu, Jul 5, 2018 at 3:34 PM Alberto Salvia Novella
wrote:
> --- THE REAL QUESTIONS ---
>
> The questions here are:
>
> - Why is the graphical-session targets inactive by default on my system?
> - How should a unit part of the graphical session be started?
>
>
This was sort of explained
iously one of them will fail
depending on system, thus my own service will fail too.
Thank you very much,
Federico
Il giorno sab 30 giu 2018 alle ore 00:10 Ryan Gonzalez
ha scritto:
systemd can depend on services, not bus names. In your example, you'd want:
Wants=polkit
However, in most cases,
systemd can depend on services, not bus names. In your example, you'd want:
Wants=polkit
However, in most cases, you don't actually want to do this; if the service
(in this case, polkit) tells systemd what bus name it is going to ask for,
systemd will automatically wait when your service asks
I *think* it's the login manager?
On June 27, 2018 11:41:22 PM Alberto Salvia Novella
wrote:
Currently many Linux Distributions don't activate
graphical-session.target and graphical-session-pre.target during login.
I liked to know which software should ideally be in charge of that. So I
The ostree docs have a good description of what to do here:
https://ostree.readthedocs.io/en/latest/manual/adapting-existing/
In particular, see the "System layout" section.
On June 17, 2018 12:03:22 PM Jérémy Rosen wrote:
Hello everybody
I am trying to understand the recommanded way to
This literally has absolutely nothing to do with systemd.
That being said, try deleting /etc/dpkg/dpkg.cfg.d/pkg-config-hook-config
and then upgrading pkg-config.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone else
https://refi64.com/
On April 28, 2018
OSError: [Errno 28] No space left on device: '/opt/skil/lib/ext'
It means what is says: whatever partition this is on has run out of space.
Try running 'df -h' to check how much free space you have on your partitions.
Regardless, this isn't really a systemd issue...
On April 25, 2018
Just filed #8722 for this: https://github.com/systemd/systemd/issues/8722
On Thu, Apr 12, 2018 at 8:17 AM, Lennart Poettering <lenn...@poettering.net>
wrote:
> On Do, 12.04.18 07:48, Ryan Gonzalez (rym...@gmail.com) wrote:
>
> > coredumpd has definitely become one of m
coredumpd has definitely become one of my favorite systemd components since
it makes debugging segfaults far easier than otherwise. However, for
various reasons, I prefer using LLDB to GDB. Unfortunately, coredumpctl's
gdb command is hardcoded to run, well, GDB.
My idea: what if there were a
I know everyone here is super busy, but I just wanted to bump this a
sec before letting it die to make sure it didn't just get lost or
something. (If someone agrees that it should be a feature, I'd happily
try to work on it.)
On Tue, Mar 20, 2018 at 4:08 PM, Ryan Gonzalez <rym...@gmail.
Hello!!
Recently, I was trying to help out someone on IRC move some sysvinit
scripts over to systemd units, and there was one interesting issue that
came up. Many older daemons will create sockets at some unspecified point
in their startup sequence, with no indication of when this occurs. In
You literally sent this out 1 minute after posting the bug. At least give
it time to breath first...
On Tue, Mar 13, 2018 at 1:09 PM, Reindl Harald
wrote:
>
>
> Am 13.03.2018 um 19:04 schrieb Michael Biebl:
>
>> My problem is sooo important, I need to pester the whole
45 matches
Mail list logo