Sponsored Content
Top Forums UNIX for Dummies Questions & Answers WARNING - exit init (PID1) died. Post 41255 by Perderabo on Wednesday 1st of October 2003 10:44:25 AM
Old 10-01-2003
I would reload the os, rebuild my file systems, and read in my last backup tape. That will be much easier than trying to undo a disaster like that.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Many dtexec process that do not died

Hi, I have a problem on CDE 1.4 Solaris 8. It looks like each time I lock the screen, the dtexec that invoke the dtscreen (that is o.k.) do not died after it done his job and it stay in the system and cause many zombie. Any suggestions? Thanks, Itay. (3 Replies)
Discussion started by: itayst
3 Replies

2. UNIX for Advanced & Expert Users

Init 6 & Init 0 problem

Hi Expert, I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0.. I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies

3. UNIX and Linux Applications

My VNC died

Greetings all, I'm on a solaris 9 system with vnc-4.1.2 installed. I had a connection to a vnc server that suddenly started sapping up cpu cycles - getting up around 13%. I killed the server instance, and now when I try to start a new server, i get the following message: "vncserver: socket... (0 Replies)
Discussion started by: mike_q
0 Replies

4. HP-UX

boot failure-init died

Hello. system fails on reboot this AM. received message about not possible for kernel to find process that caused crash. system does memory dump succesfully, then tries to boot again. looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies

5. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies

6. SCO

PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200.

hi all when ever i power on my sco server it give me the message:PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200. its not booting. any help?? (1 Reply)
Discussion started by: Danish
1 Replies

7. UNIX for Advanced & Expert Users

Problem on init 0, execution is the same with init 6

Hi, I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS. When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies

8. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies

9. UNIX for Dummies Questions & Answers

WARNING: init(1M) exited on fatal signal 9: restarting automatically

Have you ever got these : WARNING: init(1M) exited on fatal signal 9: restarting automatically and how did you solve it? (3 Replies)
Discussion started by: anaABB
3 Replies

10. SCO

PANIC: exit - cannot exec /etc/init (PID 1), status 0*00000200

Hi to all, I hope that you can help me with this... SCO Unix 5.0.5, old mashine Pentium III x86, SCSI HDD 36.4 Gb PANIC: exit – Cannot exec /etc/init (PID 1), status 0x00000200 Cannot dump 49055 pages to dumpdev hd (1/41) : space for only 48640 pages Dump not completed Safe to Power Off... (1 Reply)
Discussion started by: lakicevic
1 Replies
st_san_safe(5)							     OBSOLETED							    st_san_safe(5)

NAME
st_san_safe - determine whether access to tape device special files without the no-rewind-on-close option is allowed (OBSOLETED) VALUES
Failsafe Default Allowed values Recommended values or DESCRIPTION
Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3. This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When this tunable is on the tape driver will fail any open on a tape device special file without the no-rewind-on-close option (that is, or with a status of The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from HP-UX systems via standard tape commands like which would corrupt a backup in process. Who Is Expected to Change This Tunable? Anyone. Restrictions on Changing Changes to this tunable take effect immediately. When Should the Tunable Be Turned On? This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration. What Are the Side Effects of Turning the Tunable On? The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This behavior prevents the usage of any tape device special file without the no-rewind-on-close option. When Should the Tunable Be Turned Off? This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not function unless it has access to device special files without the no-rewind-on-close option. What Are the Side Effects of Turning the Tunable Off? A rewind may be issued from this system accidentally on close possibly corrupting a backup being issued from another system on the SAN. What Other Tunables Should Be Changed at the Same Time? None. WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of HP-UX. Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation, some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun- able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was factory installed on your system, see at AUTHOR
was developed by Hewlett-Packard. SEE ALSO
norewind_close_disabled(5), scsi_tape(7), scsimgr_estape(7). Tunable Kernel Parameters st_san_safe(5)
All times are GMT -4. The time now is 05:02 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy