github/byobu
1
0
Fork 0
mirror of https://github.com/dustinkirkland/byobu synced 2025-08-14 10:46:58 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions

* usr/share/man/man1/byobu.1: LP: #713879

Browse source 
- note too many files open ulimit error in documentation
This commit is contained in:
Dustin Kirkland 2011-10-22 03:20:20 -05:00
commit ee14e90e19
2 changed files with 4 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

2
debian/changelog vendored
View file

@ -21,6 +21,8 @@ byobu (4.43) unreleased; urgency=low
- search and use a shared dir when possible
* usr/lib/byobu/battery: LP: #851100
- rework the battery logic to use /sys instead of /proc
* usr/share/man/man1/byobu.1: LP: #713879
- note too many files open ulimit error in documentation
[ Daniel Hahler ]
* usr/bin/byobu, usr/bin/byobu-launcher-install, usr/bin/byobu-

2
usr/share/man/man1/byobu.1
View file

@ -192,6 +192,8 @@ Users who customize their PS1 prompt need to put this setting in \fI~/.bashrc\fP
If you run \fBbyobu\fP(1) under \fBsudo\fP(8), you \fBmust\fP use the -H option, such that the user's $HOME directory environment variable is set properly. Otherwise, \fBbyobu\fP(1) will create a bunch of directories in the $SUDO_USER's $HOME, but will be owned by root. To prevent this from happening, \fBbyobu\fP(1) will simply refuse to run if $USER does not own $HOME.
Byobu requires a suitable \fBulimit\fP(3) values to run. If you get an error at startup saying, 'pipe: too many open files', then check your ulimit -a values, as your "open files" or "max user processes" are too low. In this case, you will probably need to run simple \fBscreen\fP(1)
.SH SEE ALSO
.PD 0
.TP