Quote:
Originally Posted by
jlliagre
This is indeed the point and I'm sorry to insist telling you are incorrect in thinking you can dump in the filesystem.
As I already wrote and as the documentation states you either dump in the swap area or in a dedicated partition. The latter doesn't help saving disk space, just the opposite. It helps speeding up the boot process which might make sense.
No, I am sorry to disagree on this point. The documentation for dumpadm(1M) and savecore(1M) both say that you specify the partition, but you can also specify the directory:
Quote:
-s savecore-dir
Modify the dump configuration to use the specified directory to save files written by savecore. The directory should be an absolute path and exist on the system. If upon reboot the directory does not exist, it will be created prior to the execution of savecore. See the NOTES section below for a discussion of security issues relating to access to the savecore directory. The default savecore directory is /var/crash/hostname where hostname is the output of the -n option to the uname(1) command
.
Excuse me for saying so, but /var/crash/hostname, for example, is a directory in a
filesystem because directories are created in filesystems. (In other words, you have to make a filesystem before you can create a directory!)
And, as I mentioned before, this line of discussion has little to do with the issues reborg's point on swap space that you questioned, he posted:
Quote:
You don't need to allocate any swap space to deal with savecores, and have not since Solaris 8.
and he was absolutely right.
You replied with your personal preference to dump in swap. That is your preference, not a requirement. While I respect your opinion, it is an opinion, not a requirement. You simply do not need to dump in swap.
08-10-2008
