Hello,
I've recently installed a CentOS 7 minimal ISO[1], where I found the new
Predictable Network Interface Naming strategy enabled.
But in my current environment this naming strategy is not viable, and I'd
like to get back to old _unpredictable_ strategy for all the interfaces. So
according
On Tue, Mar 7, 2017 at 9:25 AM, Lucas Ventura Carro
wrote:
> Hello,
>
> I've recently installed a CentOS 7 minimal ISO[1], where I found the new
> Predictable Network Interface Naming strategy enabled.
>
> But in my current environment this naming strategy is not viable,
Hello Lucas,
Lucas Ventura Carro [2017-03-07 9:25 +0100]:
> (1) Creating a symlink
> (2) Changing a kernel boot parameter
>
> But, using option (1) doesn't work, and I'm still having predictable names.
Did you rebuild the initrd after that? Without that, it won't work indeed.
Martin
Hello everyone,
I would like to constraint the network in the containers I spawn using
nspawn.
What I'd like to achieve is the following:
- prevent the containers to use the network interfaces of the host
- make one exception and allow the containers to connect (tcp) to a
specific port bound on
*Mar 07 11:06:09 3CX systemd[1]: Starting 3CX PhoneSystem 01 Management
Console...
-- Subject: Unit 3CXPhoneSystemMC01.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit 3CXPhoneSystemMC01.service has begun
Hello,
I am revisiting the issue (since it has been completely ignored by systemd
people).
The actual attempt at fixing this issue did not succeed.
The official ubuntu fix does not resolve the hang.
The problem is that the unattended-upgrades script relies on /var/run being
mounted, if the /var/
In that case, you could also just do something like this:
# for i in {u,s,b}; do echo $i > /proc/sysrq-trigger; done
For "Remount read-only, Sync, (re)Boot". There are also hotkey sequences
to do that (the modern equivalent of the three fingered salute) which might
be more appropriate in the case
On Wed, 2017-03-08 at 13:05 +1300, Sergei Franco wrote:
>
> The official ubuntu fix does not resolve the hang.
> The problem is that the unattended-upgrades script relies on /var/run
> being mounted, if the /var/ is a separate filesystem it gets
> unmounted and thus hanging the script (where it
08.03.2017 03:05, Sergei Franco пишет:
> Hello,
>
> I am revisiting the issue (since it has been completely ignored by systemd
> people).
Which issue? "hanging reboot" is too generic title, it can be anything.
> The actual attempt at fixing this issue did not succeed.
>
> The official ubuntu
Hello Jan,
2017-03-07 9:59 GMT+01:00 Jan Synacek :
> check out the official Red Hat documentation [1] on how to disable the naming
scheme.
Doing first or third option *only* it is not working.
Hello Martin,
2017-03-07 10:01 GMT+01:00 Martin Pitt :
> Did
This failure is not from systemd; systemd is only the messenger:
> Mar 07 11:08:09 3CX systemd[1]: 3CXPhoneSystemMC01.service start
operation timed out. Terminating.
Someone needs to troubleshoot why 3CXPhoneSystemMC01.service is hanging
when it tries to start, and this list can't answer that.
> But I don't want to wait for those services to shutdown.
Then there's no reason to interact with systemd if you want to force an
immediate, unclean reboot. You just want something like the reboot syscall
with LINUX_REBOOT_CMD_RESTART.
___
12 matches
Mail list logo