[ale] Long lag for command line

[Alex Carver]

Ok, so it hung up again.  I've got a good strace and a bad strace for 
starting up vi.  The good strace shows the whole trace taking about 
three seconds.  The bad strace shows the whole trace taking 20 seconds.

I can post both  for download if anyone can help make sense of the 
traces.  I see a couple spots where the lag is very obvious (about a ten 
second gap in the time stamps).  But for the rest of the trace, 
everything is just slow overall.  Both traces are the same length so at 
least there's no issues with missing function calls.

On 6/28/2013 19:53, Michael Potter wrote:
> strace -fto strace.out vi
>
> then look at the log file (strace.out) to see where it is hanging.
>
>
>
>
> On Fri, Jun 28, 2013 at 10:48 PM, Alex Carver <agcarver+ale at acarver.net> wrote:
>> integrit and rkhunter both run every day (late at night) and no intrusions
>> have been detected.  I'll double check it but since the machine is pretty
>> much isolated from the outside world it would be tough to hack (access from
>> outside exists only via ssh tunnels and the ssh endpoint is a different
>> machine).
>>
>>
>> On 6/28/2013 17:49, Chuck Payne wrote:
>>>
>>> Not to be the Devil, but have you done lsof on vi to see if any other
>>> process are running? I am not saying you are hack, but a lag on a
>>> program couple be several things. The first thing rule out that your
>>> vi has been swap out. About 16 years ago, when I ran a linux box with
>>> our a firewall and shut down unused ports. I got owned. My ls got
>>> swapped out. it still did ls commands but it was doing nasty things. I
>>> only found out because I ran losf and saw that it was running other
>>> programs as ls.
>>
>>
>>
>>
>> _______________________________________________
>> Ale mailing list
>> Ale at ale.org
>> http://mail.ale.org/mailman/listinfo/ale
>> See JOBS, ANNOUNCE and SCHOOLS lists at
>> http://mail.ale.org/mailman/listinfo
>
>
>