Sponsored Content
Full Discussion: USB mouse stops working
Operating Systems Linux SuSE USB mouse stops working Post 302354856 by mark54g on Sunday 20th of September 2009 02:53:38 PM
Old 09-20-2009
what does the output of /var/log/messages say? The info may be in messages.1 or messages.2 if it was rotated out.
 

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
strerr(8)						      System Manager's Manual							 strerr(8)

NAME
strerr - Receives error messages from the STREAMS log driver SYNOPSIS
/usr/sbin/strerr [-a sys_admin_mail_name] [-d logdir] PARAMETERS
Specifies the mail name of the user to receive the message via mail. This is the system administrator by default. Specifies the directory to contain the error log file. This is /var/adm/streams by default. DESCRIPTION
The strerr daemon receives error messages from the STREAMS log driver (strlog) for addition to the STREAMS error log files (error.mm.dd) in the STREAMS error logger directory (/var/adm/streams by default). When first called, the strerr daemon creates the log file error.mm.dd. This is a daily log file, where mm indicates the month and dd indicates the day of the logged messages. The strerr daemon then appends each error message that it subsequently receives from the STREAMS log driver to the log file. STREAMS error log messages have the following format: seq_num std_time ticks_time flags mod_ID sub_ID msg_text where: The error sequence number. The time the message was sent, in the format hh:mm:ss. The time the message was sent, measured in machine ticks since the last boot. Can be any of the following indicators: Indicates that the message has also been saved in the process's trace log. Indi- cates that the message signaled a fatal error. Indicates that the message is to be sent to the system administrator or specified user via mail. The module identification number of the trace message source. The subidentification number of the trace message source. The trace message text. The strerr daemon will run continuously until terminated by the user. FILES
The error log file or files on which strerr operates. NOTES
Only one strerr process can open the STREAMS log driver at a time. This restriction is intended to maximize performance. The STREAMS error logging mechanism works best when it is not overused. The strerr daemon can degrade STREAMS performance by affecting the response, throughput, and other behaviors of the drivers and modules that invoke it. The daemon will also fail to capture messages if drivers and modules generate messages at a higher rate than its optimum read rate. Missing sequence numbers among the messages in a log file indicate that messages have been lost. RELATED INFORMATION
Interfaces: strlog(7). delim off strerr(8)
All times are GMT -4. The time now is 06:27 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy