From: Christoph Heiss <c.heiss@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH installer] first-boot: multi-user: start after pveproxy.service
Date: Tue, 19 Nov 2024 16:03:22 +0100 [thread overview]
Message-ID: <zs5ddqod2pdcqdahiyxg3ccjritw5oztcb3azzdj5yx7bpvl5t@gimxj6fvfnlj> (raw)
In-Reply-To: <33b7c853-6386-43d0-97bb-11623d9471d0@proxmox.com>
On Tue, Nov 19, 2024 at 03:50:47PM +0100, Thomas Lamprecht wrote:
> Am 19.11.24 um 15:39 schrieb Christoph Heiss:
> > [..]
> > diff --git a/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service b/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service
> > index d3c798d..4b30e7e 100644
> > --- a/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service
> > +++ b/proxmox-first-boot/etc/proxmox-first-boot-multi-user.service
> > @@ -1,6 +1,7 @@
> > [Unit]
> > Description=Proxmox First Boot Setup (Fully Booted)
> > -After=systemd-remount-fs.service
> > +After=systemd-remount-fs.service pveproxy.service
> > +Wants=pveproxy.service
>
> do we already want to add the units of the API from our other products now
> already?
Right, was a bit to quick for my own good with this.
Makes sense, I'll test that and send a v2 shortly.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-11-19 15:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 14:39 Christoph Heiss
2024-11-19 14:50 ` Thomas Lamprecht
2024-11-19 15:03 ` Christoph Heiss [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=zs5ddqod2pdcqdahiyxg3ccjritw5oztcb3azzdj5yx7bpvl5t@gimxj6fvfnlj \
--to=c.heiss@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.