07-25-2014
How do I disable a core(or more) while boot up in Solaris 10?
Hi,
I have 4 cores in my PC. I know how to disable a core using psradm -f command after boot up. But I want to disable while boot up (permanently).
1) I want only 1 core. How to disable all other cores while boot up?
2) I need to disable 2 cores. How to disable all other cores while boot up?
I need the best way.
Thank you.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm new to UNIX....
I'm running SCO UNIX and would like to disable routed daemon from being start at boot time.
How should I do this????? Please help. (2 Replies)
Discussion started by: rrivas
2 Replies
2. UNIX for Dummies Questions & Answers
I want to upgrade from Red Hat Linux 8.0 to Fedora Core 3. I have already downloaded FC3 on CD's. My current config. on my PC is that I have Win XP on primary hard drive and Red Hat 8.0 on another hard drive. Because my Compaq Presario reserves the first cylinder of my primary hard drive, I... (1 Reply)
Discussion started by: Mark McWilliams
1 Replies
3. Solaris
Hi,
I'm looking for a command to be able to disable a network card under the boot PROM.
I need it to force my Jumpstart to use the Ethernet card of my server (V880) instead of my fiber card (gem0).
Thanks,
Fabien (6 Replies)
Discussion started by: unclefab
6 Replies
4. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
5. Solaris
All -
would you please some one help me to disable telnet on Solaris?
/etc/inetd.conf
Thanks :confused: (11 Replies)
Discussion started by: March_2007
11 Replies
6. Solaris
Hi
Is there anyway to disable all logs/logging (lastlog, sulog, messages etc.) in Solaris 9&10? I know this is not recommended but i just want to know if this is possible.
TIA
Reddy (8 Replies)
Discussion started by: reddyr
8 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Solaris
I've new installed Solaris 11 on Sparc T4-1.
I'd like to disable IPv6 but with no luck.
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
net0: flags=1000803<UP,BROADCAST,MULTICAST,IPv4> mtu 1500 index 2
inet... (6 Replies)
Discussion started by: samer.odeh
6 Replies
9. Solaris
Hello,
I have a problem with my machine that won't boot properly.
The story is that I installed a software called apcupsd, which is a control application for my APC battery UPS. I have used version 3.14.10 earlier, but as part of restoring my previously crashed os harddrive I wanted to... (18 Replies)
Discussion started by: Zorken
18 Replies
GCORE(1) General Commands Manual GCORE(1)
NAME
gcore - get core image of running process
SYNOPSIS
gcore [-s][-c core] pid
DESCRIPTION
gcore creates a core image of each specified process, suitable for use with adb(1). By default the core image is written to the file
<pid>.core.
The options are:
-c Write the core file to the specified file instead of <pid>.core.
-s Stop the process while creating the core image and resume it when done. This makes sure that the core dump will be in a consistent
state. The process is resumed even if it was already stopped. Of course, you can obtain the same result by manually stopping the
process with kill(1).
The core image name was changed from core.<pid> to <pid>.core to prevent matching names like core.h and core.c when using programs such as
find(1).
FILES
<process-id>.core The core image.
BUGS
If gcore encounters an error while creating the core image and the -s option was used the process will remain stopped.
Swapped out processes and system processes (the swapper) may not be gcore'd.
4.2 Berkeley Distribution April 15, 1994 GCORE(1)