PTY allocation request failed on channel 0 You may have messed up your environment and specifically under /dev you may have remounted a wrong source point or otherwise killed /dev/pts The solution is to recreate /dev/pts or fix whatever caused it to be wiped out or broken. In verbose mode the client may show this: #verbose client Authenticated to 172.16.17.2 ([172.16.17.2]:22). debug........

We all know Linux is known for good memory management but is it really? It seems all on its own with hardly anything running that you can come back in days or weeks and find that almost all of your RAMis used! And many will say "no don't worry it's buffers for optimization" but it doesn't seem to help because what is in buffers is not available to use for new programs running or ones that allocate more RAM as far as Ican tell. The reason Iknow........

# first we need a physical volume which we use the pvcreate tool to create # I create mine on /dev/sdb3 pvcreate /dev/sdb3 dev_is_mpath: failed to get device for 8:19 Physical volume "/dev/sdb3" successfully created # pvdisplay shows the newly created volume pvdisplay "/dev/sdb3" is a new physical volume of "1.35 TiB" --- NEW Physical volume --- PV N........

fdisk -lu VPS.img last_lba(): I don't know how to handle files with mode 81ed You must set cylinders. You can do this from the extra functions menu. Disk VPS.img: 0 MB, 0 bytes 255 heads, 63 sectors/track, 0 cylinders, total 0 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End ........

cat /proc/user_beancounters produces the following: kmemsize 1861537 5139870 12752512 12752512 26965041 Notice the failcnt "26965041", that is for kmemsize and at first it confused me. The system had enough guaranteed and enough burst RAM available. kmemsize is a variable indepedent of that, but who cars about the explanation right, let's just make thing........