7 More Discussions You Might Find Interesting
1. Linux
I have created a bridge with nmcli between eth0 and wlan0
I use this procedure
sudo nmcli con add ifname br0 type bridge con-name br0
sudo nmcli con add type bridge-slave ifname eth0 master br0
sudo nmcli con add type bridge-slave ifname wlan0 master br0
sudo nmcli con modify br0... (1 Reply)
Discussion started by: Linusolaradm1
1 Replies
2. Solaris
Hi
I am planning to install solaris as a virtual machine on vista as host os.
My requirements are
I want to access virtual machine from vista using putty. So how to assign static ip to virtual machine ?
In future i might have to virtual machines so i want communication between them as... (3 Replies)
Discussion started by: ankurk
3 Replies
3. Windows & DOS: Issues & Discussions
hello
obviously something got messed up and I can't login to my Vista account anymore. the password was automatically disabled hence it was directly booting into vista. then I installed openSSH and created a password for the user. But vista login doesn't recognize this password and now I can't... (6 Replies)
Discussion started by: milhan
6 Replies
4. Solaris
I WANTED TO INSTALL SOLARIS 10 on my HP laptop but I wanted to do it in Dual mode, I mean I don't wanna loose Vista but also wanted to use Solaris 10.
I have original Solaris 10 Installation Media kit and If you know how to do it, Please let me know.
DUAL OS SETUP HELP NEEDED. (4 Replies)
Discussion started by: santy23
4 Replies
5. UNIX for Dummies Questions & Answers
Folks,
I need some help!
Please understand that I have searched and read tons of how-to's and other documents in researching this and getting Putty, Cygwin, and emacs running on the Vista machine.
I have a Ubuntu headless server i am trying to configure as my gateway system for the house... (3 Replies)
Discussion started by: poundjd
3 Replies
6. BSD
Hello,
I am using FreeBSD on my laptop (R60) and currently it is working great, however, I am having trouble connecting to open or WEP secured networks.
I have read the FreeBSD handbook regarding this many times. That is how I found out how to connect to WPA networks. If anyone could post a... (4 Replies)
Discussion started by: kpedersen
4 Replies
7. Solaris
Hi there,
I have a copy of Exceed 7.0, which I use on my Win XP pro machine to get access to the Solaris CDE, but this version will not run on my Vista laptop.
Do I need to get the very latest version of Exceed to run on Vista ? or is there an interim version which I might find on Ebay ?
... (2 Replies)
Discussion started by: Freddo_21
2 Replies
savecore(1M) System Administration Commands savecore(1M)
NAME
savecore - save a crash dump of the operating system
SYNOPSIS
/usr/bin/savecore [-Lvd] [-f dumpfile] [directory]
DESCRIPTION
The savecore utility saves a crash dump of the kernel (assuming that one was made) and writes a reboot message in the shutdown log. It is
invoked by the dumpadm service each time the system boots.
savecore saves the crash dump data in the file directory/vmcore.n and the kernel's namelist in directory/unix.n. The trailing .n in the
pathnames is replaced by a number which grows every time savecore is run in that directory.
Before writing out a crash dump, savecore reads a number from the file directory/minfree. This is the minimum number of kilobytes that must
remain free on the file system containing directory. If after saving the crash dump the file system containing directory would have less
free space the number of kilobytes specified in minfree, the crash dump is not saved. if the minfree file does not exist, savecore assumes
a minfree value of 1 megabyte.
The savecore utility also logs a reboot message using facility LOG_AUTH (see syslog(3C)). If the system crashed as a result of a panic,
savecore logs the panic string too.
OPTIONS
The following options are supported:
-d Disregard dump header valid flag. Force savecore to attempt to save a crash dump even if the header information stored on
the dump device indicates the dump has already been saved.
-f dumpfile Attempt to save a crash dump from the specified file instead of from the system's current dump device. This option may be
useful if the information stored on the dump device has been copied to an on-disk file by means of the dd(1M) command.
-L Save a crash dump of the live running Solaris system, without actually rebooting or altering the system in any way. This
option forces savecore to save a live snapshot of the system to the dump device, and then immediately to retrieve the data
and to write it out to a new set of crash dump files in the specified directory. Live system crash dumps can only be per-
formed if you have configured your system to have a dedicated dump device using dumpadm(1M).
savecore -L does not suspend the system, so the contents of memory continue to change while the dump is saved. This means
that live crash dumps are not fully self-consistent.
-v Verbose. Enables verbose error messages from savecore.
OPERANDS
The following operands are supported:
directory Save the crash dump files to the specified directory. If directory is not specified, savecore saves the crash dump
files to the default savecore directory, configured by dumpadm(1M).
FILES
directory/vmcore.n
directory/unix.n
directory/bounds
directory/minfree
/var/crash/'uname -n' default crash dump directory
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
adb(1), mdb(1), svcs(1), dd(1M), dumpadm(1M), svcadm(1M), syslog(3C), attributes(5), smf(5)
NOTES
The system crash dump service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/dumpadm:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If the dump device is also being used as a swap device, you must run savecore very soon after booting, before the swap space containing the
crash dump is overwritten by programs currently running.
SunOS 5.10 25 Sep 2004 savecore(1M)