It work for 1.2 version (used systemd-shutdownd.service).
For 1.3 some bug with:

PR https://github.com/vyos/vyos-1x/pull/173

That is definately much better then before. But it doe not fix the second problem.

If we replace string 108 in file /usr/libexec/vyos/op_mode/powerctrl.py

Backported

In rolling this was fixed T1204, we need add this to crux.

https://phabricator.vyos.net/T1228 sent the bug and I backported from upstream . The PR is in T1228 but needs to be merged into our package which I don't have permissions for.

as far as i know the content of the platform field is the first characters from sysdescr (20 characters?). on one of my devices this is

System Description:
Cisco IOS Software, C2960 Software (C2960-LANBASEK9-M), Version 15.0(2)SE8, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2015 by Cisco Systems, Inc.
Compiled Thu 14-May-15 02:39 by prod_rel_team

As noone complained that this option is not working (and it is an extension to regular ppp) I propose to remove it.

Thanks, should be backported to crux then as I found it there

https://github.com/vyos/vyos-1x/commit/dad110ce666edae42ac18c59a800bda503589f27

Gotcha, I start implement it for the rolling release for now. Since it affects multiple other nodes as well, I'll do it for all of them equally. aka facility has no constraint and completion help too. There are a few more I've found, so I crawl through all of them and enhance it a bit.

Nope, I was talking about completionHelper, which is not implemented - same as constraint nodes for udp/tcp regex.

@c-po I used the 1.2.3 iso from the download portal and can't reproduce the issue. The help message was also already there since it was (re)implemented, could it be an issue with your installation?

If we cancel reboot, it also write about shutdown.

how can this be invalid and closed? The error is still there on a Crux build of this week...

This is already resolved in upcoming v1.2.4 release. It is due to T1738 and T818

From CPO on Slack:

@kroy AFAIK, intel drivers, KVM (VM performance and I/O), Kernel memory I/O etc.
Performace data can be recorded and replyed asewll. Looks like candidate for debug images as @c-po pointed out.

I guess I'd ask the question of whether we have any complaints of performance type issues that perf could pinpoint? I don't know if I've ever seen any of those kind of complaints in the circles I hang out in.

perf is a tool to gather performance and debug data on a running system with a deep insight into program functions etc. Since it will need a bunch of new libs within the system, I'd like to find out if there is the need for it or not.

I was reading old documentation. It does work once I set it with the configuration instead of editing the file directly.

Added additional check before cycle.

I agree. Users should be able to change the port independently from the address.

Fix for the problem:
https://github.com/vyos/vyos-1x/pull/160
https://github.com/vyos/vyos-replace/pull/4

Due to some internal logic in net-snmp this can not be done so easy.

PR for CLI https://github.com/vyos/vyos-1x/pull/159

pending review: https://github.com/vyos/vyos-build-kernel/pull/1

If someone can confirm I'm linking to the correct github repo (there are two cloud init ones under vyos), I could submit a pull request for this. @syncer, @Unicron?

PR #158 https://github.com/vyos/vyos-1x/pull/158