10-04-2001
more log info
More log info
the log file for the working x contains allthe lines that the unworking log contains it appends them after i leave x the only thing it does say is the
Fatal server error:
Caught signal 11. Server aborting
statement I dont know if thta was caused by my canceling out of run level 5 and returning to the console. Sorry to keep posting so many threads I am just working onthis problem so I keep getting new developments let me know if you have any idea pleaseit must obviouslt work if i could getinto x
7 More Discussions You Might Find Interesting
1. Windows & DOS: Issues & Discussions
Hello guys , i have a big big problem.
At the company that i work for there are like 4 pcs that are sending and recieving a lot of packets to the point that the network is down.
we think that it might be a virus, we run all the antivirus that you could posible think of and nothing so far.
... (2 Replies)
Discussion started by: josramon
2 Replies
2. Debian
Hi. I have problems sometimes going to "My Network Places" in the Windows Explorer. Sometimes works OK and sometimes appears an Explorer.exe Application Popup:
<<The instruction at "0x10004160" referenced memory at "0x10004160". The memory could not be "read">>
and the Explorer go out or is... (0 Replies)
Discussion started by: luisben
0 Replies
3. IP Networking
Hi. I have problems sometimes going to "My Network Places" in the Windows Explorer. Sometimes works OK and sometimes appears an Explorer.exe Application Popup:
<<The instruction at "0x10004160" referenced memory at "0x10004160". The memory could not be "read">> (Event ID: 26 at the Windows... (0 Replies)
Discussion started by: luisben
0 Replies
4. UNIX for Dummies Questions & Answers
After i login i try to start X windows by using the "startx" command. All it does is return "startx: Command not found". Any help would be great.:), By the way I'm using freeBSD. (1 Reply)
Discussion started by: spacebizall
1 Replies
5. UNIX for Advanced & Expert Users
Hello all,
I have encountered a strange question. I installed a Ubuntu 8.10 in the VMware in the XP, and use putty to connect to ubuntu. Everything is fun except I can't use the wget in putty, neither does command "sudo apt-get ***". But they are OK in the VM.
Can someone help me out? Thank... (2 Replies)
Discussion started by: tpltp
2 Replies
6. UNIX for Advanced & Expert Users
Hi I have an issue with a client. He was able to use his mounted Samba share for a long time. However, a couple of days ago, he wasn't able to access all of his files all of a sudden. He still see's the share and majority of the files, but not some that he needs.
I checked with Secure CRT on... (1 Reply)
Discussion started by: zixzix01
1 Replies
7. Solaris
Hi. I'm new here and new at using Solaris and I've been having some problems with file sharing between Windows Server 2012 and Solaris 10. I will really appreciate your help.
So my Windows Server (WS) 2012 has just three activated services: DNS, DHCP and Active Directory. Solaris too three... (1 Reply)
Discussion started by: LauraKtz
1 Replies
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)