Sponsored Content
Full Discussion: USB mouse stops working
Operating Systems Linux SuSE USB mouse stops working Post 302354885 by stansaraczewski on Sunday 20th of September 2009 06:17:01 PM
Old 09-20-2009
There's nothing useful in /var/log/messages. I at first thought this was some sort of system lockup and was watching that log file and 'top' for a few weeks... then noticed disk activity (the led) after what appeared to be another lockup.

Funny thing is that this happens perhaps 7 out of 10 bootups, within the first five or ten minutes then not again.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

USB mouse needs reinstalled every time???

Help! My mouse gave up the ghost, so I connected a USB wheel mouse, and chose it from the list in Suse's Yast2. Also installed it in Windows 98 on the same machine. It works fine in both linux and Windows 98, except for this fact: I have to reinstall it every time I boot into Linux.... (1 Reply)
Discussion started by: Sonshyne5
1 Replies

2. Slackware

how to activate USB mouse

:confused: I am using Linux for a while and now changed to slackware for my study and it is not as good as redhat everytime when you add this or that it needs either configure modules or recompile kernel Now I changed from PS/2 mouse to USB trouble starts it refuse to work I know I can... (3 Replies)
Discussion started by: slackware
3 Replies

3. Solaris

Solaris 10 - init stops working

I have a really strange issue on Solaris 10 running on v490. I'm running Oracle 10g on the box. Everything runs fine and all of a sudden I get a call from a DBA. I check and none of the Oracle processes are running. They were definitely running after the system booted and nobody stopped them. I try... (0 Replies)
Discussion started by: GKnight
0 Replies

4. UNIX for Advanced & Expert Users

ssh-keygen stops working

Hey guys, I was using ssh-keygen settings for a long time to login on remote machines without password. 2 days back it suddenly stops working, i tried by reset all ssh-keygen setting but it not works. what could be the reason of this issue and how can i resolve this? (2 Replies)
Discussion started by: RohitKJ
2 Replies

5. Slackware

Replace PS/2 Trackball with USB optical mouse

Running Slackware 13.37 original without updates. Need to replace my trackball with optical mouse temporarily. There is no xf86config file anylonger but xorg.conf file is produced automatically. I see 2 "xorg.conf" files which can be and were modified on installation: 1) /etc/X11/xorg.conf-vesa... (2 Replies)
Discussion started by: slak0
2 Replies

6. Shell Programming and Scripting

Script stops working after copying it

Hi all, When I cp a script, this section of the code stops reading from a file. if ; then while read dirtoclean do DIRSTOCLEAN=${DIRSTOCLEAN}' '$dirtoclean done < ${BASEDIR}test.conf fi ${DIRSTOCLEAN} doesn't return anything, even though it will work right before... (6 Replies)
Discussion started by: nicksantos1
6 Replies

7. Shell Programming and Scripting

My script stops working when using crontab

I have made a shell script(/bin/sh) that starts a perl script (that I haven't made my self) that's starts a ssh session. The ssh session uses a private/public key to login so no password is needed. The Perl script works perfect. But when I put it in a cronjob (crontab) the ssh connection asks... (6 Replies)
Discussion started by: splinter_cell
6 Replies

8. UNIX for Beginners Questions & Answers

CONFIG_HID=y and logitech usb mouse B185 doesn't work in 5.3.0-RC2

trying to make the best for me with 5.3.0-RC2, everthing's fine, the dell vostro 3558 does what it should - but - and here's the question: how do I get a logitech m185 (wireless mouse) to work; I googled around but couldn't fiind anything usefull; the best I get when using solaar (depreciated?) is:... (2 Replies)
Discussion started by: vanbreukelingen
2 Replies
SHUTDOWN(8)						    BSD System Manager's Manual 					       SHUTDOWN(8)

NAME
shutdown, poweroff -- close down the system at a given time SYNOPSIS
shutdown [-] [-h | -p | -r | -k] [-o [-n]] time [warning-message ...] poweroff DESCRIPTION
The shutdown utility 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. The following options are available: -h The system is halted at the specified time. -p The system is halted and the power is turned off (hardware support required) at the specified time. -r The system is rebooted at the specified time. -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). -o If one of the -h, -p or -r options are specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to init(8). -n If the -o option is specified, prevent the file system cache from being flushed by passing -n to halt(8) or reboot(8). This option should probably not be used. time Time is the time at which shutdown will bring the system down and may be the case-insensitive word now (indicating an immediate shut- down) or a future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system values. The first form brings the system down in number minutes and the second at the absolute time specified. +number may be specified in units other than minutes by appending the corresponding suffix: ``s'', ``sec'', ``m'', ``min''. ``h'', ``hour''. warning-message Any other arguments comprise the warning message that is broadcast to users currently logged into the system. - If '-' is supplied as an option, the warning message is read from the standard input. 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 /var/run/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 to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea- son. The corresponding signal is then sent to init(8) to respectively halt, reboot or bring the system down to single-user state (depending on the above options). The time of the shutdown and the warning message are placed in /var/run/nologin and should be used to inform the users about when the system will be back up and why it is going down (or anything else). A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice). The /var/run/nologin file that shutdown created will be removed automatically. When run without options, the shutdown utility will place the system into single user mode at the time specified. Calling ``poweroff'' is equivalent to running: shutdown -p now FILES
/var/run/nologin tells login(1) not to let anyone log in EXAMPLES
Reboot the system in 30 minutes and display a warning message on the terminals of all users currently logged in: # shutdown -r +30 "System will reboot" COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility. SEE ALSO
kill(1), login(1), wall(1), nologin(5), halt(8), init(8), reboot(8) HISTORY
The shutdown utility appeared in 4.0BSD. BSD
December 15, 2014 BSD
All times are GMT -4. The time now is 03:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy