On Mo, 29.06.20 12:19, Ian Pilcher (arequip...@gmail.com) wrote:
> I originally posted a variation of the question on the SELinux mailing
> list, but the more I look at this the more I realize that it really
> isn't a SELinux questions. I'm not really sure that it's a systemd
> question either, b
On Mo, 29.06.20 12:03, Marcos Alonso (marcos3...@gmail.com) wrote:
> Hi, I installed Arch and it all works good except that I have to wait for a
> timeout on startup.
> That´s what I find in the journal:
>
> -- Logs begin at Wed 2020-06-10 22:59:26 CEST, end at Mon 2020-06-29
> 11:58:14 CEST. --
>
On Sa, 27.06.20 20:55, Reindl Harald (h.rei...@thelounge.net) wrote:
> is this a dracut or systemd bug in Fedora 32?
>
> the other failing services at bottom are a direct reuslt of this while
> everything seems to work fine, but i can't stand "failed" stuff when
> consider a dist-upgrade
This loo
On Mo, 29.06.20 08:20, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
> > There's a whole section in the man page about this, it's called
> > "Command Lines". It's referred to in the first line of the explanation
> > of ExecStart=.
>
> It would be better to refer to the target section dir
On Sa, 27.06.20 15:54, Mark Rogers (m...@more-solutions.co.uk) wrote:
> > It could very well be because of the dhcpcd.service you're using.
> >
> > I don't know what it's like on Raspbian, but on Debian this unit appears
> > to have no ordering with respect to network.target or network-pre.target
On Mo, 29.06.20 11:02, Hans de Goede (hdego...@redhat.com) wrote:
> Hi All,
>
> For Fedora 33 I would like to get rid of some ugly hacks we have
> wrt the grub-hidden-menu feature Fedora has been shipping for a
> while now.
>
> One part of this will be setting SYSTEMD_REBOOT_TO_BOOT_LOADER_ENTRY
>
Hi,
On 6/30/20 11:36 AM, Lennart Poettering wrote:
On Mo, 29.06.20 11:02, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
For Fedora 33 I would like to get rid of some ugly hacks we have
wrt the grub-hidden-menu feature Fedora has been shipping for a
while now.
One part of this will be se
On Tue, 30 Jun 2020 at 10:27, Lennart Poettering
wrote:
> Yes, this is a bug in the the distro packaging. Please file a bug
> against your distro, so that they add After=network-pre.target.
>
Will do.
> My educated guess is that, it's not trvial to get this right: we
> document what network-pr
On Tue, 30 Jun 2020 at 11:27:30 +0200, Lennart Poettering wrote:
> On Sa, 27.06.20 15:54, Mark Rogers (m...@more-solutions.co.uk) wrote:
> > Adding After=network-pre.target to dhcpcd.service seems to have
> > resolved it, and taught me a lesson in the process.
> >
> > Is there an obvious reason I'm
On Tue, 30 Jun 2020 at 12:13, Simon McVittie wrote:
>
> I would have expected this to be done in some "larger" network management
> component that is responsible for bringing up network interfaces according
> to your configuration, rather than necessarily dhcpcd.service itself.
In which case one
On Tue, 30 Jun 2020 at 12:59:54 +0100, Mark Rogers wrote:
> On Tue, 30 Jun 2020 at 12:13, Simon McVittie wrote:
> >
> > I would have expected this to be done in some "larger" network management
> > component that is responsible for bringing up network interfaces according
> > to your configuration
Am 30.06.20 um 14:55 schrieb Simon McVittie:
> Adding After=network-pre.target to dhcpcd.service is probably also not
> a bad idea. It isn't clear to me whether dhcpcd brings up interfaces of
> its own accord just because you start it as a systemd unit
it just fails when like in the example bel
On 6/30/20 4:18 AM, Lennart Poettering wrote:
Maybe it double forks or forks a child off (callout script?) that
double forks somewhere?
I don't know your software, it's probably best to ping the authors of
it about this, they should know what their software does.
LOL! I am the author.
So I
13 matches
Mail list logo