HI .. Thanks for your quick response. TBH .. I didn’t know where to start. It looks like nohup and screen are doing the same thing. And its only recent. I created a brand new user - enabled byobu and ran something simple .. disconnect .. and the session closes completely.
Screen sadly does the same thing from what I can see. Just to repeat - byoby/screen and nohup are all doing it - I love Byobu - so this is my first port of call ! :) ( please be gentle ) .. executing nohup /usr/bin/python /foo/pythonthing.py & works fine while I am connected and then instantly terminates on disconnect of the SSH. It is only very recent. And I don't think its anything I did.. the baffling thing is that ROOT is unaffected by this disconnection .. I wonder if their isn’t some new permission being pushd that makes persistence a "option ?" seems silly to do that. Please help! Tx Ivan. -----Original Message----- From: Alex Chernyakhovsky [mailto:[email protected]] Sent: Thursday, May 26, 2016 1:46 AM To: Ivan Frimmel <[email protected]>; [email protected] Cc: Debian Bug Tracking System <[email protected]>; [email protected] Subject: Re: Bug#825324: byobu: Byobu session closes on SSH disconnect tags 825324 moreinfo unreproducible thanks Hi Ivan, Did your apt-get dist-upgrade include an update to tmux and/or screen? byobu has not been pushed to sid or stretch recently, so I do not see how it can be at fault. It is likely that some change in the underlying tmux and/or screen backend you are using has changed. Try `tmux list-sessions` or `screen -ls` depending on which byobu backend you are using (tmux is currently the default) to see if the sessions are present. Additionally, please try reproducing with tmux/screen directly, without byobu. Sincerely, -Alex On Thu, May 26, 2016 at 1:19 AM, Ivan Frimmel <[email protected]> wrote: > Package: byobu > Version: 5.87-1 > Severity: important > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where > appropriate *** > > * What led up to the situation? > Did a apt-get dist-upgrade > * What exactly did you do (or not do) that was effective (or > ineffective)? > root sessions will persist for some reason, but regular account > sessions that used to allow disconnect of ssh now terminate immediately on > disconnect and do not persist at all. I am not sure if byobu is crashing, I > looked for dump files but here arent any that I can see. > * What was the outcome of this action? > I can't fix the problem. I searched all the byobu an bash > documentation and /etc/profile and /etc/skel etc and I can't find anything > that would be causing this all of a suddent. I don't think it's anything I > did specifically. > * What outcome did you expect instead? > The sessions would persist after ssh disconnect. > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: stretch/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.5.0-2-amd64 (SMP w/8 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages byobu depends on: > ii debconf [debconf-2.0] 1.5.59 > ii gawk 1:4.1.3+dfsg-0.1 > ii gettext-base 0.19.7-2 > ii python 2.7.11-1 > ii python-newt 0.52.18-3 > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu recommends: > pn run-one <none> > ii screen 4.3.1-3 > ii tmux 2.2-2 > > Versions of packages byobu suggests: > pn apport <none> > pn ccze <none> > ii lsb-release 9.20160110 > ii po-debconf 1.0.19 > pn ttf-ubuntu-font-family <none> > pn update-notifier-common <none> > pn vim <none> > ii w3m 0.5.3-28 > pn wireless-tools <none> > > -- debconf information: > byobu/launch-by-default: false
smime.p7s
Description: S/MIME cryptographic signature
