I had a weird thing this morning while running save-config, where it
aborted in a very strange way (in VMware). To make a long story short,
after a lot of traces, manual "tar" commands, and head beating, I
figured out it was because my VMware was set to 16MB of memory.
This is a fresh boot with a blank floppy. It seems like there is enough
memory in 16MB to run tar, but when the "j" option kicks in, bzip2 loads
and aborts tar.
I increased my memory in VMware to 32MB and save-config runs fine there
(except for the "diff" part which I don't care about).
We might want NOT want to advertise DL will run in 16MB of memory, if
people cannot save their configuration on that size machine. The other
option would be to use some busybox commands in save-config instead of
the standard ones ... (or not :)
--------------------------------------------
Bruce Smith br...@ar...
System Administrator / Network Administrator
Armstrong International, Inc.
Three Rivers, Michigan 49093 USA
http://www.armstrong-intl.com/
--------------------------------------------
|