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
backup(1M)																backup(1M)

NAME
backup - backup or archive file system SYNOPSIS
[-archive] DESCRIPTION
The command uses find(1) and cpio(1) to save a archive of all files that have been modified since the modification time of on the default tape drive should be invoked periodically to ensure adequate file backup. The option suppresses warning messages regarding optional access control list entries. backup(1M) does not backup optional access control list entries in a file's access control list (see acl(5)). Normally, a warning message is printed for each file having optional access control list entries. The option causes backup to save all files, regardless of their modification date, and then update using touch(1). prompts you to mount a new tape and continue if there is no more room on the current tape. Note that this prompting does not occur if you are running from cron(1M). The option causes to start a file system consistency check (without correction) after the backup is complete. For correct results, it is important that the system be effectively single-user while is running, especially if is allowed to automatically fix whatever inconsisten- cies it finds. does not ensure that the system is single-user. You can edit to customize it for your system. Several local values are used that can be customized: specifies which directories to back up recursively (usually meaning all directories); file name where start and finish times, block counts, and error messages are logged; file name whose date is the date of the last archive; file name that is checked by to remind the next person who logs in to change the backup tape; file name where start and finish times and output is logged. You may want to make other changes, such as whether or not does automatic correction (according to its arguments), where output is directed, other information logging, etc. In all cases, the output from is a normal archive file (or volume) which can be read using with the option. File Recovery creates archive tapes with all files and directories specified relative to the root directory. When recovering files from an archive tape created by you should be in the root directory and specify the directory path names for recovered files relative to the root directory When specifying the directory path name for file recovery by do not precede the leading directory name with a slash. If you prefer, you can also use with a option to determine how files and directories are named on the archive tape before attempting recovery. WARNINGS
Refer to in cpio(1). When runs out of tape, it sends an error to standard error and demands a new special file name from To continue, rewind the tape, mount the new tape, type the name of the new special file at the system console, and press If is being run unattended from cron(1M) and the tape runs out, terminates, leaving the process still waiting. Kill this process when you return. FILES
parameterized file names SEE ALSO
cpio(1), find(1), touch(1), cron(1M), fbackup(1M), frecover(1M), fsck(1M), acl(5). backup(1M)
All times are GMT -4. The time now is 09:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy