byobu

CentOS issues

Asked by Igor Feghali

Hello,

Here follows the issues (and a few solutions) I found running byobu on CentOS 5.

1) date status is broken (base64 issue). patch that fixes the problem:

--- date.bak 2011-02-10 14:56:38.000000000 -0200
+++ date 2011-02-10 14:56:44.000000000 -0200
@@ -25,7 +25,7 @@
                date +%Y-%m-%d
        ;;
        *)
- msg="$(echo SGFwcHkgQmlydGhkYXkgU2NyZWVuIC0tIGh0dHA6Ly9iaXQubHkvc2NyZWVuLWJkYXkK | base64 -d)"
+ msg="$(echo SGFwcHkgQmlydGhkYXkgU2NyZWVuIC0tIGh0dHA6Ly9iaXQubHkvc2NyZWVuLWJkYXkK | base64 -di)"
                [ "$(date +%d)" = "20" ] && [ "$(date +%m)" = "03" ] && screen -X -S "byobu" at "*" echo "[$msg]"
                printf "\005Y-\005m-\005d "
        ;;

2) disk_io status is broken. error:

stat: cannot stat `/var/run/screen/S-uqn7/byobu.disk_read': No such file or directory
cat: /var/run/screen/S-uqn7/byobu.disk_read: No such file or directory
awk: cmd. line:1: fatal: cannot open file `/sys/block/ROOTVG-LVROOT/stat' for reading (No such file or directory)

possible solution: it should read from /sys/block/md0/stat

3) the status bar has color issues. could be fixed applying your own patch (from https://bugs.launchpad.net/ubuntu/+source/screen/+bug/315871) to GNU screen's source code. It would be great to have it documented in a better place (like the manpage)

4) my .profile is not being read. actually it does get read, but it seems that its somehow dismissed. all the alias are lost, PS1 is reseted and TERM is set to vt100 instead of xterm-256color.

Very nice work by the way,

Question information

Language:
English Edit question
Status:
Solved
For:
byobu Edit question
Assignee:
No assignee Edit question
Solved by:
Igor Feghali
Solved:
Last query:
Last reply:
Revision history for this message
Dustin Kirkland  (kirkland) said : 		#1

Hi there!

Thanks for the detailed report!

 (1) Fixed in bzr now, thanks ;-)
 (2) This one is a little tougher. Could I ask you to please open a new bug report for this issue, and please attach the output of 'sh -x /usr/lib/byobu/disk_io' and your /etc/mtab. Feel free to fuzz any private information you can't share. I think there's a problem in my processing of LVM volumes to the appropriate /sys/block/$disk path. I rarely use LVM so this bit is perhaps a little untested by me. In the mean time, see the byobu.1 manpage, and see the section on disk_io. You can set MONITORED_DISK in your ~/.byobu/statusrc and you can override Byobu's detected default disk.
 (3) Done. Added a paragraph to the manpage. Thanks, good suggestion.
 (4) Hmm, now that is strange. I can confirm that none of byobu's wrapping shell code modifies your PS1 or TERM environment values. It's possible that we're using some option of GNU Screen that's doing this under the covers (such as the caption or hardstatus always lastline directives). If you'd like to get to the bottom of this, please file a new bug on this issue and I'd be happy to try and work through this, as your .profile should be read. My is read just fine on all of my Ubuntu/byobu installs.

Thanks again!

Revision history for this message
Igor Feghali (ifeghali) said : 		#2

thank you for the fixes.

regarding (4), someone already reported it at Bug #525552