Sponsored Content
Full Discussion: Strange Problem
Top Forums UNIX for Dummies Questions & Answers Strange Problem Post 7616 by Perderabo on Friday 28th of September 2001 09:25:19 AM
Old 09-28-2001
In /etc/inittab, look at the line with "x" as the first field. It will have "respawn" in the third field. For now, change "respawn" to "off" and do a "init q" to force a reread of inittab. Then you need to figure out if the line should be there and, if it should, how to fix it.

The most common cause is a getty that cannot read the device file.

Once you figure it out, go back to "respawn".
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Strange problem.Please Help !

I¡¯m a network operator, mine is an IBM PC server 320, operating system SCO unix 3.2v4.2, triton 3.1 of Baan. Recently, my server went dead every a few hours, no sign & signal shows malfunction suddenly. It looks like a sudden power failure, but the indicator of main power supply is on. Normal... (1 Reply)
Discussion started by: lyhsm
1 Replies

2. UNIX for Dummies Questions & Answers

strange...problem

Hi.. Some of my application were not running properly due to lack of virtual memory.....so wht i did add one free harddisk as swap file system...and increased the swap memory.. But since than my root file system is showing 100% full thr is no space left...is thr any link between these two..... (1 Reply)
Discussion started by: Prafulla
1 Replies

3. Linux

very strange problem

I have installed Fedora Core on a Toshiba Satellite Pro4600 laptop recently I have experienced a rather mysterious problem if I touch anything specially the keyboard or mouse I see this stuff “67yujhnmyyy” straight away some time it won't stop for while like this... (5 Replies)
Discussion started by: kemobyte
5 Replies

4. Shell Programming and Scripting

Strange problem

I am using SunOS 5.9 and I don't know why all my commands are getting executed as if an extra 'enter' has been pressed. What could be the reason and how to correct it? Please help. Asty (2 Replies)
Discussion started by: Asty
2 Replies

5. Shell Programming and Scripting

Strange problem.

Well, my script started off to do what i wanted. Now, i think its not recognizing the pattern so its not moving anything. What i have to do is execute my script command for the move to take effect. So i did that and yayy it worked. Strange thing is that my DESTDIR was empty to begin with.... (2 Replies)
Discussion started by: oxoxo
2 Replies

6. UNIX for Dummies Questions & Answers

strange rlogin problem

Hi, in my environment we have several server with rlogin passwordless login enabled, now there is a problem to setup this with a hpux server. i have check the .rhosts file and kerberos key are all setup properly and permission is correct, even other user id on the server can login without... (3 Replies)
Discussion started by: robertngo
3 Replies

7. Shell Programming and Scripting

Strange Problem

Hi All, I am encountering an unexpected problem while running my process, using daemon placed in /etc/init.d/. I have a process that is opening shared library using dlopen. When I run my process on the command line, it is able to open the library. But when I used daemon to run my process, I... (0 Replies)
Discussion started by: qwerty-1
0 Replies

8. UNIX for Dummies Questions & Answers

strange problem with samba

windowsxp:192.168.0.11 fedora14:192.168.0.12, running smb server I have disabled selinux. user list of fedora14: jone (wihch is created when install fedora14, with password 'jone') jone2 (which is added by hand, with password 'jone2') I added jone and jone2 as samba users using 'smbpasswd... (1 Reply)
Discussion started by: vistastar
1 Replies

9. Shell Programming and Scripting

strange problem

hello all, i am having problem in accessing a directory.I dont think its a permission issue.can anyone help me out. I am using korn sell code: $ ls -ltr sc* lrwxrwxrwx 1 essbase essbase 21 Oct 8 2010 sc_ssp -> /work/nfs/nas2/sc_ssp $ cd sc_ssp ksh: sc_ssp: not found $ (6 Replies)
Discussion started by: manid
6 Replies
SHUTDOWN(8)						    BSD System Manager's Manual 					       SHUTDOWN(8)

NAME
shutdown -- close down the system at a given time SYNOPSIS
shutdown [-Ddfhknprvxz] [-b bootstr] time [message ... | -] DESCRIPTION
shutdown provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties. Available friendlinesses: -b bootstr The given bootstr is passed to reboot(8) for the benefit of those systems that can pass boot arguments to the firmware. Currently, this only affects sun3 and sparc machines. -d shutdown will pass the -d flag to reboot(8) or halt(8) to request a kernel core dump. If neither the -h or -r flags are specified, then -d also implies -r. -f shutdown arranges, in the manner of fastboot(8), for the file systems not to be checked on reboot. -h The system is halted at the specified time, using halt(8). -k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all but super-user). -n Prevent the normal sync(2) before stopping. -p The system is powered down at the specified time, using poweroff(8). If the powerdown fails, or the system does not support soft- ware powerdown, the system will simply halt instead. -r The system is rebooted at the specified time, using reboot(8). -v To enable verbose messages on the console, pass -v to reboot(8) or halt(8). -x To enable debugging messages on the console, pass -x to reboot(8) or halt(8). -z To silence some shutdown messages on the console, pass -z to reboot(8) or halt(8). -D Prevents shutdown from detaching from the tty with fork(2)/ exit(3). time Time is the time at which shutdown will bring the system down and may be the word now or a future time in one of two formats: +number, or [[[[[cc]yy]mm]dd]hh]mm, where the century, year, month, day, and hour may be defaulted to the current system values. The first form brings the system down number minutes from the current time; the second brings the system down at the absolute time specified. If the century is not specified, it defaults to 1900 for years between 69 and 99, or 2000 for years between 0 and 68. A leading zero in the ``yy'' value is not optional. message ... Any other arguments comprise the warning message that is broadcast to users currently logged into the system. - If - is supplied as the only argument after the time, the warning message is read from the standard input. BEHAVIOR
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on the terminals of all users logged in. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are dis- abled by creating /etc/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1) prints its contents and exits. The file is removed just before shutdown exits. At shutdown time, a message is written in the system log containing the time of shutdown, who initiated the shutdown, and the reason. Next a message is printed announcing the start of the system shutdown hooks. Then the shutdown hooks in /etc/rc.shutdown are run, and a message is printed indicating that they have completed. After a short delay, shutdown runs halt(8) or reboot(8), or sends a terminate signal to init(8) to bring the system down to single-user mode, depending on the choice of options. The time of the shutdown and the warning message are placed in /etc/nologin and should be used to tell the users why the system is going down, when it will be back up, and to share any other pertinent information. FILES
/etc/nologin tells login(1) not to let anyone log in /fastboot tells rc(8) not to run fsck(8) when rebooting /etc/rc.shutdown System shutdown commands SEE ALSO
login(1), wall(1), fastboot(8), halt(8), init(8), poweroff(8), reboot(8), rescue(8) BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility. HISTORY
The shutdown command appeared in 4.0BSD. BSD
October 4, 2011 BSD
All times are GMT -4. The time now is 09:18 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy