[pve-devel] [PATCH container 1/2] LXC: drop unused imported locking functions

Fabian Ebner f.ebner at proxmox.com
Tue Apr 28 14:41:46 CEST 2020


Played around for a bit with your patches applied on top of mine and 
found no obvious issue, except for LXC creation [0] which is exposed by 
my second patch.

So for Fabian G.'s patches:
Tested-By: Fabian Ebner <f.ebner at proxmox.com>

[0]: https://pve.proxmox.com/pipermail/pve-devel/2020-April/043210.html

On 27.04.20 10:24, Fabian Grünbichler wrote:
> Signed-off-by: Fabian Grünbichler <f.gruenbichler at proxmox.com>
> ---
>   src/PVE/LXC.pm | 4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> index fbe736e..651ec08 100644
> --- a/src/PVE/LXC.pm
> +++ b/src/PVE/LXC.pm
> @@ -20,8 +20,8 @@ use PVE::SafeSyslog;
>   use PVE::INotify;
>   use PVE::JSONSchema qw(get_standard_option);
>   use PVE::Tools qw(
> -    dir_glob_foreach file_get_contents file_set_contents lock_file
> -    lock_file_full AT_FDCWD O_PATH $IPV4RE $IPV6RE
> +    dir_glob_foreach file_get_contents file_set_contents
> +    AT_FDCWD O_PATH $IPV4RE $IPV6RE
>   );
>   use PVE::CpuSet;
>   use PVE::Network;
> 




More information about the pve-devel mailing list