USB mouse stops working Post: 302354885

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

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

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?

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

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

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

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

LEARN ABOUT DEBIAN

doveadm-log

DOVEADM-LOG(1)							      Dovecot							    DOVEADM-LOG(1)

NAME

       doveadm-log - Locate, test or reopen Dovecot's log files

SYNOPSIS

       doveadm [-Dv] log errors
       doveadm [-Dv] log find [directory]
       doveadm [-Dv] log reopen
       doveadm [-Dv] log test

DESCRIPTION

       The  doveadm  log commands are used to locate and reopen the log files of dovecot(1).  It's also possible to test the configured targets of
       the *log_path settings.

OPTIONS

       Global doveadm(1) options:

       -D     Enables verbosity and debug messages.

       -v     Enables verbosity, including progress counter.

COMMANDS

   log errors
       doveadm log errors

       The log errors command is used to show the last	- up to 1,000 - errors and warnings.  If no output is generated, no errors  have  occurred
       since the last start.

   log find
       doveadm log find [directory]

       The  log  find  command	is used to show the location of the log files, to which dovecot(1) sends its log messages.  If dovecot(1) logs its
       messages through syslogd(8) and doveadm(1) could not find any log files, you can specify the directory where your syslogd  writes  its  log
       files.

   log reopen
       doveadm log reopen

       This command causes doveadm to reopen all log files, configured in the log_path, info_log_path and debug_log_path settings.  These settings
       are configured in /etc/dovecot/conf.d/10-logging.conf.
       This is for example useful after manually rotating the log files.

   log test
       doveadm log test

       This command causes doveadm to write the message "This is Dovecot's priority log (timestamp)" to the configured log files.  The used prior-
       ities are: debug, info, warning, error and fatal.

EXAMPLE

       This example shows how to locate the log files used by dovecot(1).

       doveadm log find
       Looking for log files from /var/log
       Debug: /var/log/dovecot.debug
       Info: /var/log/mail.log
       Warning: /var/log/mail.log
       Error: /var/log/mail.log
       Fatal: /var/log/mail.log

REPORTING BUGS

       Report  bugs,  including doveconf -n output, to the Dovecot Mailing List <dovecot@dovecot.org>.	Information about reporting bugs is avail-
       able at: http://dovecot.org/bugreport.html

SEE ALSO

       doveadm(1)

Dovecot v2.1							    2012-02-22							    DOVEADM-LOG(1)