Init scripts missing . . .


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Init scripts missing . . .
Prev   Next
# 1  
Old 07-18-2013
Init scripts missing . . .

One of our VM machines mysteriously went read-only overnight and as it wasn't being used, thought it would be a good idea to reboot the machine and run fsck on boot, well. . . .. things didn't quite work out that way lol Smilie

Anyway, the machine booted up, but mysteriously had no hostname set, thought I would check why and the '/etc/host' file is missing, checked further and it turns out that the 'init.d' folder and ALL the init scripts are missing too, as is 'xinet.d', and probably a host of other files from '/etc'.

Although we have backups, I need to try and get the machine back onto the network so I can copy the files back over . . . . . . question is, is there any way that I can start the network back up without the init scripts ?

Tried the usuals, ifup etc all to no avail - any of you brilliant minds out there any ideas !?

Cheers, Jim
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

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

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

10. UNIX for Dummies Questions & Answers

init scripts on AIX

Where are they located? (2 Replies)
Discussion started by: 98_1LE
2 Replies
Login or Register to Ask a Question
SHUTDOWN(8)						Linux System Administrator's Manual					       SHUTDOWN(8)

NAME
shutdown - bring the system down SYNOPSIS
/sbin/shutdown [-t sec] [-arkhncfF] time [warning-message] DESCRIPTION
shutdown brings the system down in a secure way. All logged-in users are notified that the system is going down, and login(1) is blocked. It is possible to shut the system down immediately or after a specified delay. All processes are first notified that the system is going down by the signal SIGTERM. This gives programs like vi(1) the time to save the file being edited, mail and news processing programs a chance to exit cleanly, etc. shutdown does its job by signalling the init process, asking it to change the runlevel. Runlevel 0 is used to halt the system, runlevel 6 is used to reboot the system, and runlevel 1 is used to put to system into a state where administrative tasks can be performed; this is the default if neither the -h or -r flag is given to shutdown. To see which actions are taken on halt or reboot see the appropriate entries for these runlevels in the file /etc/inittab. OPTIONS
-a Use /etc/shutdown.allow. -t sec Tell init(8) to wait sec seconds between sending processes the warning and the kill signal, before changing to another runlevel. -k Don't really shutdown; only send the warning messages to everybody. -r Reboot after shutdown. -h Halt after shutdown. -n [DEPRECATED] Don't call init(8) to do the shutdown but do it ourself. The use of this option is discouraged, and its results are not always what you'd expect. -f Skip fsck on reboot. -F Force fsck on reboot. -c Cancel an already running shutdown. With this option it is of course not possible to give the time argument, but you can enter a explanatory message on the command line that will be sent to all users. time When to shutdown. warning-message Message to send to all users. The time argument can have different formats. First, it can be an absolute time in the format hh:mm, in which hh is the hour (1 or 2 dig- its) and mm is the minute of the hour (in two digits). Second, it can be in the format +m, in which m is the number of minutes to wait. The word now is an alias for +0. If shutdown is called with a delay, it creates the advisory file /etc/nologin which causes programs such as login(1) to not allow new user logins. Shutdown removes this file if it is stopped before it can signal init (i.e. it is cancelled or something goes wrong). It also removes it before calling init to change the runlevel. The -f flag means `reboot fast'. This only creates an advisory file /fastboot which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide not to run fsck(1) since the system has been shut down in the proper way. After that, the boot process should remove /fastboot. The -F flag means `force fsck'. This only creates an advisory file /forcefsck which can be tested by the system when it comes up again. The boot rc file can test if this file is present, and decide to run fsck(1) with a special `force' flag so that even properly unmounted filesystems get checked. After that, the boot process should remove /forcefsck. The -n flag causes shutdown not to call init, but to kill all running processes itself. shutdown will then turn off quota, accounting, and swapping and unmount all filesystems. ACCESS CONTROL
shutdown can be called from init(8) when the magic keys CTRL-ALT-DEL are pressed, by creating an appropriate entry in /etc/inittab. This means that everyone who has physical access to the console keyboard can shut the system down. To prevent this, shutdown can check to see if an authorized user is logged in on one of the virtual consoles. If shutdown is called with the -a argument (add this to the invocation of shutdown in /etc/inittab), it checks to see if the file /etc/shutdown.allow is present. It then compares the login names in that file with the list of people that are logged in on a virtual console (from /var/run/utmp). Only if one of those authorized users or root is logged in, it will proceed. Otherwise it will write the message shutdown: no authorized users logged in to the (physical) system console. The format of /etc/shutdown.allow is one user name per line. Empty lines and comment lines (prefixed by a #) are allowed. Currently there is a limit of 32 users in this file. Note that if /etc/shutdown.allow is not present, the -a argument is ignored. FILES
/fastboot /etc/inittab /etc/init.d/halt /etc/init.d/reboot /etc/shutdown.allow NOTES
A lot of users forget to give the time argument and are then puzzled by the error message shutdown produces. The time argument is manda- tory; in 90 percent of all cases this argument will be the word now. Init can only capture CTRL-ALT-DEL and start shutdown in console mode. If the system is running the X window System, the X server pro- cesses all key strokes. Some X11 environments make it possible to capture CTRL-ALT-DEL, but what exactly is done with that event depends on that environment. Shutdown wasn't designed to be run setuid. /etc/shutdown.allow is not used to find out who is executing shutdown, it ONLY checks who is currently logged in on (one of the) console(s). AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
fsck(8), init(8), halt(8), poweroff(8), reboot(8) Juli 31, 2001 SHUTDOWN(8)