What's the best way to track down a really big memory leak? "Big" = enough to crash a 64 meg ARC in 24 hours. law-ts1> show mem util SYSTEM MEMORY RESOURCES Total System Memory Resources: 49509 KB Code Size: 5833 KB Initialized Data Size: 1490 KB Uninitialized Data Size: 4356 KB Stack Size: 512 KB Free Memory Current Value: 13451 KB Free Memory 1 Hour Before: 14590 KB Free Memory 12 Hours Before: 20724 KB Free Memory 24 Hours Before: 19901 KB Total Buffer Cache: 40000 Free Buffer Cache: 26690 Almost a meg an hour. Ouch. This just started happening about 28 hours ago, probably when I changed something in the config... hell if I remember what it was though. OSPF maybe. It's kinda like what happens to a NETserver when syslog is broken, but I don't think syslog is the culprit here... Is there some way I can get a list of running processes (like "list processes" does) on the card and how big each one is? I've got a list of all commands in 5.0, including the "_" commands, but so far I haven't found a winner. Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet services for Frankfort, Lawrenceburg, Owenton, Shelbyville www.fark.com: If it's not news, it's Fark. (Or something like that.) - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.