Dear Jeffrey,
On 2020-01-07 03:17, Jeffrey Walton wrote:
[…]
> There are absolutely 0 entires about my monitor service:
>
> $ journalctl -e | grep -i callboot | grep monitor
> $
The switch `-e` implies that by default only 1000 lines are shown.
-e, --pager-end
On Mon, 6 Jan 2020 21:47:37 -0500
Jeffrey Walton wrote:
> On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald
> wrote:
> >
> > Am 07.01.20 um 02:57 schrieb Jeffrey Walton:
> > > To fix my ordering problem I need Systemd to stop lying about
> > > when the network is ready.
> >
> > one last comment:
On Mo, 06.01.20 21:06, Jeffrey Walton (noloa...@gmail.com) wrote:
> I think that was a very good summary of the problem.
>
> I want my monitor service to start (it is the most important one), but
> there are absolutely no traces of it.
>
> The joke is Systemd and its inability to provide basic
On Mo, 06.01.20 08:51, Jeffrey Walton (noloa...@gmail.com) wrote:
> Hi Everyone,
>
> I'm trying to install a service. The script is failing with:
>
> + systemctl enable callboot-monitor.service
> Failed to enable unit: File callboot-monitor.service: Invalid argument
> + exit 1
>
> The
On Mo, 06.01.20 20:28, Jeffrey Walton (noloa...@gmail.com) wrote:
> I'm trying to determine my service fails to start. I copied the
> service to the systemd unit directory, and then enabled and started
> the service. Upon reboot the service is not started automatically.
>
> Here are the logs:
>
>
On Mo, 06.01.20 20:44, Claes H (claesatw...@gmail.com) wrote:
> On Mon, Jan 6, 2020 at 1:40 PM Lennart Poettering
> wrote:
> >
> > If possible use DynamicUser=1, i.e. have a short-lived user that only
> > exists while your service is running.
> >
> > For some usecases that doesn#t work though.
On Mo, 06.01.20 20:57, Jeffrey Walton (noloa...@gmail.com) wrote:
> > and to your other post "5 seconds after all systems services have
> > actually started" is something which simply don#t exist and can't exist
> > at all
> >
> > fix your orderings and your problems are gone
>
> To fix my
On Di, 07.01.20 03:03, Reindl Harald (h.rei...@thelounge.net) wrote:
> >> Especially the "Wants" is problematic and noramlly not needed for
> >> enabled services, normally your only use After/NBefore unless there is a
> >> compelling resason for Wants/Requires and with growing useless
> >>
On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
> About a year ago there was some discussion on having persistent network names
> on Hyper-V/Azure. Haiyang did some patches to add an attribute which
> could be used by udev to do this. But there are some reluctance
On Mo, 06.01.20 20:46, Jeffrey Walton (noloa...@gmail.com) wrote:
> On Mon, Jan 6, 2020 at 8:34 PM Reindl Harald wrote:
> >
> > Am 07.01.20 um 02:28 schrieb Jeffrey Walton:
> > > I'm trying to determine my service fails to start. I copied the
> > > service to the systemd unit directory, and then
On Mo, 06.01.20 21:47, Jeffrey Walton (noloa...@gmail.com) wrote:
> On Mon, Jan 6, 2020 at 9:35 PM Reindl Harald wrote:
> >
> > Am 07.01.20 um 02:57 schrieb Jeffrey Walton:
> > > To fix my ordering problem I need Systemd to stop lying about when the
> > > network is ready.
> >
> > one last
(resending after subscribed to systemd-devel)
> -Original Message-
> From: Lennart Poettering
> Sent: Tuesday, January 7, 2020 9:01 AM
> To: Stephen Hemminger
> Cc: systemd-devel@lists.freedesktop.org; Haiyang Zhang
>
> Subject: Re: [systemd-devel] Better network naming on
On Di, 07.01.20 16:01, Haiyang Zhang (haiya...@microsoft.com) wrote:
> > I have no idea what that means, what is Accelerated Networking?
>
> On Azure, "Accelerated Networking" means SRIOV / VF NICs.
There's nowadays already support for SR-IOV naming in place:
On Di, 07.01.20 09:53, Stephen Hemminger (step...@networkplumber.org) wrote:
> On Tue, 7 Jan 2020 15:01:25 +0100
> Lennart Poettering wrote:
>
> > On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
> >
> > > About a year ago there was some discussion on having
On Tue, 7 Jan 2020 15:01:25 +0100
Lennart Poettering wrote:
> On Mo, 06.01.20 15:36, Stephen Hemminger (step...@networkplumber.org) wrote:
>
> > About a year ago there was some discussion on having persistent network
> > names
> > on Hyper-V/Azure. Haiyang did some patches to add an attribute
Hello,
I see that a mount unit with `Options=bind` set creates the resource
to be mounted, specified by `What`, in addition to the mount point,
specified by `Where`, when they don't exist.
Manual page at
https://www.freedesktop.org/software/systemd/man/systemd.mount.html
mentions that the mount
16 matches
Mail list logo
