Sponsored Content
Full Discussion: Init scripts missing . . .
Top Forums UNIX for Dummies Questions & Answers Init scripts missing . . . Post 302834485 by rbatte1 on Friday 19th of July 2013 04:58:04 AM
Old 07-19-2013
We've had a similar problem where an archiving job was failing in the batch with a permissions issue. We changed it to run as root forgetting that it meant a different home directory and therefore an input file was not found. The knock on effect meant that we managed to move /dev, /etc, /opt ...... into an archive area. Very difficult to recover because you could not start a new session (/etc/passwd was not there of course) but with luck someone had a session as root that we could manipulate enough to recover, putting back /etc & /dev first and we could get more people logged on to investigte and restore.

The upshot is that your incident won't have happened by bad luck, sunspots or whatever, there has been an action taken to remove things. It may have been a mis-typed command, or an ill designed batch job where a small change has had catastrophic consequences.

Depending how paranoid your auditing is, you may have logged something, maybe not. We were able to work out what it was based on the time batch jobs started failing to start and the jobs already running, so we got lucky. We also had a bootable image on DVD to restore from if necessary.

Whilst you may be able to recover (or go to your full restore/DR plan) you need to determine what happened to prevent a recurrence.


Robin
Liverpool/Blackburn
UK
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

init scripts on AIX

Where are they located? (2 Replies)
Discussion started by: 98_1LE
2 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. Solaris

Missing init files for zsh and bash

I change my default shell to zsh but can't find the init files, .zshrc and .zlogin from /export/home and /home. The other shells init files are there:.cshrc, .profile and .login. Am I suppose to use these as templates? Also, bash_history is there but not zsh_history although zsh do keep a... (2 Replies)
Discussion started by: maag
2 Replies

4. 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

5. Red Hat

Difference between 'init s' and 'init 1'

What is the difference between 'init s' and 'init 1'. I know that both will work to change the current run level to single user mode. Is there any difference in those two commands? (5 Replies)
Discussion started by: praveen_b744
5 Replies

6. Red Hat

Init scripts for tty's under Fedora 13

In the olden days it used to be /etc/inittab. Then it got changed to /etc/event.d/tty* under Fedora 10. Can someone please point out what it is now in Fedora 13? I want to run mgetty which I had configured in Fedora 10 as /etc/event.d/ppp0: # modem - getty # # This service maintains a... (1 Reply)
Discussion started by: druidmatrix
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 Advanced & Expert Users

Init vs rc scripts, history, different UNIXes

Why not just init? What do /etc/rc*.* scripts, rc*.*d and init*.*d directories and directory trees, etc (ex like svc, startsrc, and on and on) do that init and inittab do not or could not do? Is it just so novice SysAdmins need not mess with init? Is there an overview anyplace of how start-up... (4 Replies)
Discussion started by: Clovis_Sangrail
4 Replies

10. Shell Programming and Scripting

Prioritizing scripts under /etc/init.d/

Hello Team, I work on IBM TWS ( Tivoli Workload Scheduler ) administration. I have placed TWS service stop and start script under directory /etc/init.d/ in my Linux server and coded email alert when the script has been executed with stop or start parameter . I am receiving email notification... (3 Replies)
Discussion started by: madhuraju
3 Replies
reboot(1M)																reboot(1M)

NAME
reboot - restart the operating system SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments] The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel. Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending loss of service. See shutdown(1M) for details. The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On systems, reboot may also update the boot archive as needed to ensure a successful reboot. The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present. Normally, the system reboots itself at power-up or after crashes. The following options are supported: -d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps. -l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot. -n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to sync filesystems. -q Quick. Reboot quickly and ungracefully, without shutting down running processes first. The following operands are supported: boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot argument list. Example 1: Passing the -r and -v Arguments to boot In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M). example# reboot -dl -- -rv Example 2: Rebooting Using a Specific Disk and Kernel The following example reboots using a specific disk and kernel. example# reboot disk1 kernel.test/unix /var/adm/wtmpx login accounting file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2), reboot(3C), attributes(5) The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown of system services, use shutdown(1M) or init(1M) to reboot a Solaris system. 11 Apr 2005 reboot(1M)
All times are GMT -4. The time now is 08:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy