Hi, Actually, vi is running fine when I logged in as a normal user. When I say normal user, it is NOT logged in on the chrooted environment (SSH). http://chrootssh.sourceforge.net/
@Ron I forgot to mention, yes I used ldd to track down the needed libraries for vi or any other programs I permitted. It's actually part on the bash script to create chrooted users. Then it will create the necessary directories and libraries on the isolated space for every user. I haven't tried strace though.. :) Anyways, thanks for all the info. Olem On Sat, Nov 8, 2008 at 3:11 PM, Earl Lapus <[EMAIL PROTECTED]> wrote: > On Fri, Nov 7, 2008 at 8:21 AM, Olem Babia <[EMAIL PROTECTED]> wrote: > > @Earl > > VI does not actually crash when I try to run it. It just simply won't > > function properly. Let say for instance you are under edit mode and you > type > > in the arrow keys (not the numerical keypad) to navigate. Instead of the > > normal navigation function, it will jumble all letters (making it > uppercase, > > etc..) > > > > if your vi was compiled with debugging symbols, you can send the > output of the dump to the vi mailing list - you'd get the best answers > as to why vi is crashing there. because even if this is just some > configuration issue, vi should not have crashed. sorry, this is as far > as i can help you with this... > > -- > There are seven words in this sentence. > _________________________________________________ > Kagay-Anon Linux Users' Group (KLUG) Mailing List > [email protected] (http://lists.linux.org.ph/mailman/listinfo/klug) > Searchable Archives: http://archives.free.net.ph > -- c0d3rz f0r L!fe
_________________________________________________ Kagay-Anon Linux Users' Group (KLUG) Mailing List [email protected] (http://lists.linux.org.ph/mailman/listinfo/klug) Searchable Archives: http://archives.free.net.ph
