public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Oguz Bektas <o.bektas@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH container] mention file path for ct debug log
Date: Thu, 25 Feb 2021 12:01:06 +0100	[thread overview]
Message-ID: <20210225110106.GB11907@gaia.proxmox.com> (raw)
In-Reply-To: <5429d2b2-a0a8-f9f7-6d2a-57f59408efdc@proxmox.com>

On Thu, Feb 25, 2021 at 11:58:53AM +0100, Thomas Lamprecht wrote:
> On 25.02.21 11:16, Oguz Bektas wrote:
> > Signed-off-by: Oguz Bektas <o.bektas@proxmox.com>
> > ---
> >  src/PVE/LXC.pm | 5 ++++-
> >  1 file changed, 4 insertions(+), 1 deletion(-)
> > 
> > diff --git a/src/PVE/LXC.pm b/src/PVE/LXC.pm
> > index bae236b..db9a2ee 100644
> > --- a/src/PVE/LXC.pm
> > +++ b/src/PVE/LXC.pm
> > @@ -2306,7 +2306,10 @@ sub vm_start {
> >  	monitor_start($monitor_socket, $vmid) if defined($monitor_socket);
> >  
> >  	# if debug is requested, print the log it also when the start succeeded
> > -	print_ct_stderr_log($vmid) if $is_debug;
> > +	if ($is_debug) {
> > +	    print_ct_stderr_log($vmid);
> > +	    print "debug log saved in: /run/pve/ct-$vmid.stderr\n";
> 
> why though? all of that file is printed so what use is it to see the
> path (with just the same content one just gets printed).

hmm i was thinking it'd be easier to attach on the forum threads.

> 
> Also it's not really saved, this is just in memory. I'd not print that...

then maybe we can just save it somewhere and print that?

> 
> > +	}
> >      };
> >      if (my $err = $@) {
> >  	unlink $skiplock_flag_fn;
> > 
> 




  reply	other threads:[~2021-02-25 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 10:16 Oguz Bektas
2021-02-25 10:58 ` Thomas Lamprecht
2021-02-25 11:01   ` Oguz Bektas [this message]
2021-02-25 11:17     ` Thomas Lamprecht

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=20210225110106.GB11907@gaia.proxmox.com \
    --to=o.bektas@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal