all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Lorenz Stechauner <l.stechauner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 storage 1/3] status: move unlink from http-server to enpoint
Date: Thu, 26 Aug 2021 18:30:30 +0200	[thread overview]
Message-ID: <03cd9b76-a623-4c4f-01a0-4282b028abb8@proxmox.com> (raw)
In-Reply-To: <20210803121640.2530993-3-l.stechauner@proxmox.com>

On 03/08/2021 14:16, Lorenz Stechauner wrote:
> this is the first step in which not the http server removes the
> temporary file, but the worker itself.
> 
> Signed-off-by: Lorenz Stechauner <l.stechauner@proxmox.com>
> ---
>  PVE/API2/Storage/Status.pm | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/PVE/API2/Storage/Status.pm b/PVE/API2/Storage/Status.pm
> index b838461..a5ac372 100644
> --- a/PVE/API2/Storage/Status.pm
> +++ b/PVE/API2/Storage/Status.pm
> @@ -486,6 +486,7 @@ __PACKAGE__->register_method ({
>  	    print "command: " . join(' ', @$cmd) . "\n";
>  
>  	    eval { run_command($cmd, errmsg => 'import failed'); };
> +	    unlink $tmpfilename or warn "unable to clean up temporary file '$tmpfilename' - $!";

and doesn't this have the same issues as you recently fixed in regards to the node
not being the local one and thus ssh/scp being used?

>  	    if (my $err = $@) {
>  		eval { $err_cleanup->() };
>  		warn "$@" if $@;
> 





  parent reply	other threads:[~2021-08-26 16:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-03 12:16 [pve-devel] [PATCH-SERIES v3 http-server/storage/manager] fix #3505: add checksum and algorithm to iso upload Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 http-server 1/1] anyevent: move unlink from http-server to endpoint Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 storage 1/3] status: move unlink from http-server to enpoint Lorenz Stechauner
2021-08-23 16:14   ` Thomas Lamprecht
2021-08-26 16:30   ` Thomas Lamprecht [this message]
2021-08-30 11:54     ` Lorenz Stechauner
2021-08-31  7:51       ` Thomas Lamprecht
2021-08-03 12:16 ` [pve-devel] [PATCH v3 storage 2/3] status: remove sleep(1) in file upload Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 storage 3/3] fix #3505: status: add checksum and algorithm to " Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 manager 1/5] ui: move upload window into UploadToStorage.js Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 manager 2/5] ui: refactor UploadToStorage.js Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 manager 3/5] fix #3505: ui/UploadToStorage: add checksum and algorithm Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 manager 4/5] ui/UploadToStorage: add TaskViewer Lorenz Stechauner
2021-08-03 12:16 ` [pve-devel] [PATCH v3 manager 5/5] ui/UplaodToStorage: check file extension Lorenz Stechauner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=03cd9b76-a623-4c4f-01a0-4282b028abb8@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=l.stechauner@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal