11-19-2008
Did all those things and it's still stopping at "Multi-user initialization completed". I think this must be something simple.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
On my PC I have two hard disks, the first with Windows 98 SE and the second with Linux Mandrake 8.0 (Traktopel). When I have installed Linux, it has modified the boot record of the 1st HD and it has added a graphic menu (LILO) for selecting the OS to use. By default, if I don't press a key, Linux... (2 Replies)
Discussion started by: robotronic
2 Replies
2. UNIX for Dummies Questions & Answers
I have a diskless work station.
i want to boot from a remote linux machine.
what changes i will have to do in configuration.
Plz tell me
thanks (1 Reply)
Discussion started by: hemant29
1 Replies
3. SCO
I get a message saying
Not enough space to dump xxxxx pages
Press any key to reboot
Safe to power off
After rebooting it never gets to the "Press CTRL D to continue or enter password for single user" message before it goes back to "Not enough space..." message above. Vicious cycle.
... (0 Replies)
Discussion started by: deloev
0 Replies
4. SuSE
Hi,
Our systems:
system1: amd 64 running suse linux 9 enterprize
system2: amd 64 running esx vmware 3 with suse linux 9 enterprize.
The problem is:
when we ssh into system2 and execute the command:
ls -al
the session hangs. Infact session hangs when we execute any... (3 Replies)
Discussion started by: rajranibl
3 Replies
5. UNIX for Dummies Questions & Answers
being nosey on sons laptop and set a password and now need to undo this but its in the boot system :eek::eek::eek: (4 Replies)
Discussion started by: hempel
4 Replies
6. Solaris
Hi,
where can I check the system boot up log file like those message when the system booting up....
Thanks. (14 Replies)
Discussion started by: efang
14 Replies
7. AIX
Guy's
I have AIX 6.1 has some slowness when I login to the system ..
When I login by user screen hangs for some time 20 seconds then it's give me the command prompt .. !
system is fine is working fine only this issue I faced can you please help me in this .. what's the expected reason... (2 Replies)
Discussion started by: ITHelper
2 Replies
8. Solaris
We have a system that won't boot. It is Sun V245 that was patched yesterday with the latest Recommended 10 patch cluster. I will post what we get during the boot at the end of the email message. We have tried rebuilding the bootblk, booting from the cdrom, and running an fsck, booting into failsafe... (2 Replies)
Discussion started by: brownwrap
2 Replies
9. Red Hat
Hi
im using centos 6.4
starting yesterday i have a strange issue that im unable to resolve. the system is booting to GRUB menu and the os is not starting. i tried to run a repair install and the message attached is what i get, what can cause this?
thanks, (1 Reply)
Discussion started by: guy3145
1 Replies
10. UNIX for Advanced & Expert Users
Hi,
I got stuck in a very messy situation yesterday after attempting to resolve a filesystem full issue. The user reported that their filesystem (/var/DWS) was 100% full even after moving few files of sizes 14G, 30G and 50G out of the directory. I checked the filesystem once more after this... (5 Replies)
Discussion started by: anaigini45
5 Replies
LEARN ABOUT DEBIAN
stopping
stopping(7) Miscellaneous Information Manual stopping(7)
NAME
stopping - event signalling that a job is stopping
SYNOPSIS
stopping JOB=JOB INSTANCE=INSTANCE RESULT=RESULT [PROCESS=PROCESS] [EXIT_STATUS=STATUS] [EXIT_SIGNAL=SIGNAL] [ENV]...
DESCRIPTION
The stopping event is generated by the Upstart init(8) daemon when an instance of a job begins stopping. The JOB environment variable con-
tains the job name, and the INSTANCE environment variable contains the instance name which will be empty for single-instance jobs.
If the job is stopping normally, the RESULT environment variable will be ok, otherwise if the job is stopping because it has failed it will
be failed.
When the job has failed, the process that failed will be given in the PROCESS environment variable. This may be pre-start, post-start,
main, pre-stop or post-stop; it may also be the special value respawn to indicate that the job is stopping because it hit the respawn
limit.
Finally in the case of a failed job, one of either EXIT_STATUS or EXIT_SIGNAL may be given to indicate the cause of the stop. Either
EXIT_STATUS will contain the exit status code of the process, or EXIT_SIGNAL will contain the name of the signal that the process received.
The normal exit job configuration stanza can be used to prevent particular exit status values or signals resulting in a failed job, see
init(5) for more information.
If neither EXIT_STATUS or EXIT_SIGNAL is given for a failed process, it is because the process failed to spawn (for example, file not
found). See the system logs for the error.
init(8) will wait for all services started by this event to be running, all tasks started by this event to have finished and all jobs
stopped by this event to be stopped before allowing the job to continue stopping.
This allows jobs to depend on other jobs, safely stopping themselves before their dependency goes away. This event is typically combined
with the started(7) event by services.
Job configuration files may use the export stanza to export environment variables from their own environment into the stopping event. See
init(5) for more details.
EXAMPLE
A service that wishes to depend on another service might use:
start on started apache
stop on stopping apache
A task that must be run before another task or service is stopped might use:
start on stopping postgresql RESULT=ok
SEE ALSO
starting(7) started(7) stopped(7) init(5)
Upstart 2009-07-09 stopping(7)