The Attended sysUpgrade CLI is a full-featured client for the
attended-sysupgrade service which works directly on the target device.
It requires libustream-ssl as well as at least the CA certificate
needed to contact the sysupgrade server.
It has only been tested briefly and is by no means ready for
production!
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
due to various clients and the existence of rpcd-mod-rpcsys the package
rpcd-mod-attendedsysupgrade is superflous.
From now on the attendedsysupgrade-common package should be dependencie
of all kinds of clients.
Currently active or planned:
- luci-app-attendedsysupgrade
- attendedsysupgrade cli in shell
- attendedsysupgrade cli in c
Signed-off-by: Paul Spooren <paul@spooren.de>
Two important configuration files, /etc/php7-fpm.conf and
/etc/php7-fpm.d/www.conf are silently overwritten on each php7-fpm
upgrade or lost on a sysupgrade.
This commit adds the conffiles section for php7-fpm and revises
the conffiles section for php7.
Signed-off-by: Val Kulkov <val.kulkov@gmail.com>
During keepalived config generation for the vrrp_instance and vrrp_sync_group
the notify_* sections are automatic added to the runtime keepalived.conf.
This could be used for service which want to react on keepalived notifications.
Signed-off-by: Florian Eckert <fe@dev.tdt.de>
Interfaces of some PtP protocols do not have a real gateway. In that
case ubus may fill them with '0.0.0.0' or even leave it blank. This
will cause error when adding new routing rule.
Signed-off-by: David Yang <mmyangfl@gmail.com>
Just about everything needs extutils to be built. But very little
requires it to run.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
Don't need to have a bare /etc/modules.d/ file since we can cleanly
synthesize one now.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
It seems that Inline::C evaluates to undef which is problematic, so
we need to handle this better.
Signed-off-by: Philip Prindeville <philipp@redfish-solutions.com>
This method allows getting basic info about a queried container. It's
based on the lxc-info command-line tool.
Example output:
> ubus call lxc info '{ "name": "foo" }'
{
"name": "foo",
"state": "RUNNING",
"pid": 2946,
"ips": [
"192.168.0.124"
]
}
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Approved-by: Luka Perkov <luka@openwrt.org>