Comment 1 for bug 664059
Revision history for this message
| Matthias Winzeler (matthias-winzeler) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I have to correct my statement: It does not work by simply defining $RUN in /usr/bin/byobu because on the first start, $RUN (i.e. /var/run/screen) does not exist yet and the condition -w "$RUN" will fail (the same applies to the condition in byobu-janitor). Thus the symlink will be broken. On the second start, screen (?) has created /var/run/screen, byobu-janitor will set up the symlink and everything will be fine.
It would be great if two things could be checked:
1. The additional check for the symlink in /usr/bin/byobu seems to be redundant to me - byobu-janitor would take care of that.
Remove these lines?
2. $SSH_AUTH_SOCK is broken on first startup of byobu, because it checks the existence of /var/run/screen that does not exist. Maybe the whole process with the symlinking should be reconsidered?
Thank you!