Arch log problem

Dear all,
There is not much activity in the database. but archive logs are filling the disk.. How can I resolve this issue ?
Kai

Aren't we jumping to conclusions here without having cross-checked if it is the statistics gathering job only which is resulting in large number of archive files?
Its definitely not recommended to disable this job. If you want to disable this, then you need to come up with your own job to gather statistics at regular intervals.
You can change the schedule for this job to run at off-peak times though.

Similar Messages

Arch logging errors (/var/logs)

i got two problems i'd like to solve maybe their cause is the same.
first: is global arch logging. that's my ls -l of /var/log/
-rw-r--r-- 1 root root 0 Apr 21 11:27 acpid.log
-rw-r--r-- 1 root root 0 Apr 7 22:13 acpid.log.1
-rw-r--r-- 1 root root 0 Apr 21 11:27 auth.log
-rw-r--r-- 1 root root 0 Apr 7 22:14 auth.log.1
-rw-r--r-- 1 root root 1092 Nov 7 02:52 boot
-rw------- 1 root root 1152 Mar 17 08:06 btmp
drwxr-xr-x 2 root root 72 Nov 7 16:56 ConsoleKit
-rw-r--r-- 1 root root 0 Apr 7 22:14 crond
-rw-r--r-- 1 root root 0 Apr 21 11:27 daemon.log
-rw-r--r-- 1 root root 0 Apr 7 22:18 daemon.log.1
-rw-r--r-- 1 root root 39494 Apr 22 13:18 dmesg.log
-rw-r--r-- 1 root root 0 Apr 21 11:27 errors.log
-rw-r--r-- 1 root root 0 Apr 7 22:18 errors.log.1
-rw-r--r-- 1 root root 0 Apr 21 11:27 everything.log
-rw-r--r-- 1 root root 0 Apr 7 22:18 everything.log.1
-rw------- 1 root root 32032 Apr 22 12:03 faillog
drwxrwx--T 2 root gdm 1392 Apr 22 13:18 gdm
drwxr-xr-x 2 root root 368 Apr 21 11:27 httpd
-rw-r--r-- 1 root root 0 Apr 21 11:27 kernel.log
-rw-r--r-- 1 root root 0 Apr 7 22:19 kernel.log.1
-rw-r--r-- 1 root root 292292 Apr 22 12:03 lastlog
-rw-r--r-- 1 root root 0 Apr 21 11:27 messages.log
-rw-r--r-- 1 root root 0 Apr 7 22:19 messages.log.1
drwxr-xr-x 2 root root 48 Feb 26 06:56 old
-rw-r--r-- 1 root root 151881 Apr 22 13:42 pacman.log
-rw-r--r-- 1 root root 86 Apr 22 13:18 pm-powersave.log
-rw-r--r-- 1 root root 6049 Apr 20 10:21 pm-suspend.log
-rw-r--r-- 1 root root 0 Apr 21 11:27 syslog.log
-rw-r--r-- 1 root root 0 Apr 7 22:19 syslog.log.1
-rw-r--r-- 1 root root 0 Apr 21 11:27 user.log
-rw-r--r-- 1 root root 0 Apr 7 22:19 user.log.1
-rw-rw-r-- 1 root root 407424 Apr 22 13:29 wtmp
-rw-rw-r-- 1 root root 415488 Apr 7 18:36 wtmp.1
-rw-r--r-- 1 root root 13947 Apr 22 13:18 Xorg.0.log
-rw-r--r-- 1 root root 14486 Apr 22 13:17 Xorg.0.log.old
all files, that have dublicate name with .1 at the end, are always empty and as time goes by files with the same name but with .2, .3, .4 appear but also empty. It looks like arch is trying to create logs but something goes wrong and nothing is logged.
second: i got errors from cron if i do run-cron /etc/cron.daily/ related to log files:
sudo run-cron /etc/cron.daily/
error: syslog-ng:1 duplicate log entry for /var/log/crond.log
error: found error in /var/log/messages.log /var/log/auth.log /var/log/mail.log /var/log/kernel.log /var/log/errors.log /var/log/daemon.log /var/log/user.log /var/log/iptables.log /var/log/everything.log /var/log/syslog.log /var/log/acpid.log /var/log/crond.log /var/log/lpr.log /var/log/uucp.log /var/log/news.log /var/log/ppp.log /var/log/debug.log , skipping
looks like the files r corrupted or something. please help find out the reasons and fix things up.

I think it has to do with the group log having write permissions...
# ls -l /var/log/
total 8240
drwxr-xr-x 2 root root 4096 Mar 31 01:38 ConsoleKit/
drwxr-xr-x 2 root root 4096 Apr 4 03:52 httpd/
drwxr-xr-x 2 http http 4096 Apr 18 03:45 lighttpd/
drwxr-xr-x 2 root root 4096 Feb 25 23:56 old/
-rw-r----- 1 root log 29283 Apr 22 11:05 auth.log
-rw-r----- 1 root log 71395 Apr 18 03:26 auth.log.1
-rw-r----- 1 root log 62225 Apr 11 03:17 auth.log.2
-rw-r----- 1 root log 121945 Apr 4 03:41 auth.log.3
-rw------- 1 root root 0 Mar 29 02:00 btmp
-rw-r----- 1 root log 6622 Apr 22 09:17 crond.log
-rw-r----- 1 root log 10756 Apr 18 03:45 crond.log.1
-rw-r----- 1 root log 10340 Apr 11 03:45 crond.log.2
-rw-r----- 1 root log 8809 Apr 4 03:45 crond.log.3
-rw-r----- 1 root log 63451 Apr 22 11:01 daemon.log
-rw-r----- 1 root log 101060 Apr 18 03:42 daemon.log.1
-rw-r----- 1 root log 103755 Apr 11 03:37 daemon.log.2
-rw-r----- 1 root log 72875 Apr 4 03:36 daemon.log.3
-rw-r--r-- 1 root root 32631 Apr 19 03:27 dmesg.log
-rw-r----- 1 root log 2881 Apr 21 23:22 errors.log
-rw-r----- 1 root log 162980 Apr 17 09:55 errors.log.1
-rw-r----- 1 root log 30491 Apr 9 21:54 errors.log.2
-rw-r----- 1 root log 31213 Apr 3 18:38 errors.log.3
-rw-r----- 1 root log 276636 Apr 22 11:01 everything.log
-rw-r----- 1 root log 1196453 Apr 18 03:45 everything.log.1
-rw-r----- 1 root log 374844 Apr 11 03:45 everything.log.2
-rw-r----- 1 root log 610588 Apr 4 03:45 everything.log.3
-rw------- 1 root root 24144 Apr 22 10:25 faillog
-rw-r----- 1 root log 185643 Apr 22 10:25 kernel.log
-rw-r----- 1 root log 1051728 Apr 18 02:02 kernel.log.1
-rw-r----- 1 root log 250567 Apr 11 03:27 kernel.log.2
-rw-r----- 1 root log 521352 Apr 3 18:38 kernel.log.3
-rw-r--r-- 1 root root 293752 Apr 22 10:25 lastlog
-rw-r----- 1 root log 229278 Apr 22 11:01 messages.log
-rw-r----- 1 root log 959109 Apr 18 03:42 messages.log.1
-rw-r----- 1 root log 309842 Apr 11 03:37 messages.log.2
-rw-r----- 1 root log 489801 Apr 4 03:36 messages.log.3
-rw-r--r-- 1 root root 77695 Apr 22 10:42 pacman.log
-rw-r--r-- 1 root root 86 Apr 19 13:23 pm-powersave.log
-rw-r----- 1 root log 825 Apr 19 03:27 syslog.log
-rw-r----- 1 root log 1387 Apr 15 15:39 syslog.log.1
-rw-r----- 1 root log 738 Apr 9 11:36 syslog.log.2
-rw-r----- 1 root log 1600 Mar 31 00:02 syslog.log.3
-rw-r----- 1 root log 16287 Apr 22 10:15 user.log
-rw-r----- 1 root log 24546 Apr 17 03:45 user.log.1
-rw-r----- 1 root log 626 Apr 11 03:27 user.log.2
-rw-r----- 1 root log 416 Mar 30 04:12 user.log.3
-rw-r----- 1 root log 6622 Apr 22 09:17 uucp.log
-rw-r----- 1 root log 10756 Apr 18 03:45 uucp.log.1
-rw-r----- 1 root log 10340 Apr 11 03:45 uucp.log.2
-rw-r----- 1 root log 8809 Apr 4 03:45 uucp.log.3
-rw-rw-r-- 1 root root 471552 Apr 22 10:25 wtmp
-rw-r--r-- 1 root root 150528 Apr 1 03:21 wtmp.1
-rw-r--r-- 1 root wheel 16308 Apr 22 10:25 Xorg.0.log
-rw-r--r-- 1 root users 23624 Apr 22 10:25 Xorg.0.log.old
Did you chown -R root:root /var/log on Apr 7?

Error logging problem:

error logging problem:
I would like to implement an error logger that will do the following tasks when a error/exception arrises:
- surpress the DacfErrorPopupLogger
- alert the user that an error has occured with a simplified popup (create a global listener then use the ErrorAttributes to create the text of the popup)
- log the error in a file with a timestamp and all error information
- later if the above works....i would like to add the error attributes (time stamp, error type) to a oracle object/ Jdev domain.
Questions:
What is the best technique to use....errorManager, error logger ...?? combination
How do i use the error manager to register listners for the errors?.
In the following code i am not sure how to access the ErrorsAttributes[] array that is returned by loggerReader.getErrors();
Any general tips places to find sample code on errorManager or associated interfaces, will be appreciated
I used the OutPutStreamLogger to write error information to a FileOutputStream then a loggerReader to get the error attributes from the file. The reason i went in this direction is because i found some smple code on the outputStream logger.
package DACVideo;
import oracle.dacf.util.errorloggers.*;
import oracle.dacf.util.errormanager.*;
import oracle.dacf.util.errorloggers.InputStreamLoggerReader.ErrorAttributes;
import java.io.*;
* A Class class.
* <P>
* @author Adam Maddox
public class ErrorLogger extends Object {
static OutputStreamLogger logger = null;
static InputStreamLoggerReader loggerReader = null;
public ErrorLogger() {
System.out.println("==============ErrorLogger Created==============");
//remove default error logger (popup logger)
ErrorManager.removeErrorLogger(ErrorManager.findLoggerByName(DacfErrorPopupLogger.NAME));
try
logger = new OutputStreamLogger(new FileOutputStream("out.dat"));
loggerReader = new InputStreamLoggerReader(new FileInputStream("out.dat"));
catch(java.io.IOException e)
System.err.println("Error!");
try
ErrorManager.addErrorLogger(logger);
catch(NameAlreadyRegisteredException e)
System.err.println("A Logger with this name is already registered.");
private void closeErrorLog()
//close the OutputStream, to force flushing
logger.closeOutputStream();
ErrorManager.removeErrorLogger(logger);
public static void showErrorLog()
ErrorAttributes[] errorArray = loggerReader.getErrors(); <<<<CANNOT GET ERROR ATTRIBUTES ??
null

JDev could you help??

X2-02 log problem

dear members,
I have a log problem with my x2-02, only the last occurrence belonging to a certain contact (in the contacts book), is logged. When a new handling-occurence linked to this contact happened, only this last handling is logged (all the previous are deleted, not there anymore).
This was not the situation before, I did play a little bit through the menu and after that it happened. Of course I did already try the regular solutions, soft reset-hard reset, reinstalling the (latest software). But till now nothing did work.
Can someone assist on this
Greetings
Fiesta
holland

dear members
I would like to contribute the following, I noticed an other bug, which i think occured simultaneously/is linked together. When i go to contacts, and choose the option "View conversations" i see with certain persons, that there are also conversations (sms messages) not pertaining/belonging to that contact (belonging to more different contacts).
Does this bell ring some where?
greetings
fiesta

Why don't we keep Oracle Database ARCH logs in RAW devices

Hi All,
Why don't we keep Oracle Database ARCH logs in RAW devices?
How ARCH process is related to Block Device and Character Device ?
Thanks,
Tusar
Edited by: user11987718 on 26-Jun-2012 09:59

Why don't we keep Oracle Database ARCH logs in RAW devices? 1.This is because raw devices do not enable sequential writing of consecutive archive log files.
http://docs.oracle.com/cd/E11882_01/rac.112/e16795/rman.htm#RACAD320
2.with raw you have to specify the exact size of the file at creation time, in contrast with file system, where you can create file without specifying its size, start writing to it, apending new blocks to it until you are done, and thus creating a file of whatever size it needs to be to hold all information.
http://www.dbasupport.com/forums/archive/index.php/t-16429.html
3.raw file systems are difficult to manage because you cannot run normal os commands on them.(as there is no file systems)
How ARCH process is related to Block Device and Character Device ?A block device would read/write bytes in fixed size blocks, as in disk sectors. Character devices read/write 0 or more bytes, in a stream, such as a TTY or a keyboard.
For more details about what is block and character device type :
http://en.wikipedia.org/wiki/Device_file
And now think, how arch process is related to block and character devices.
Regards
Girish Sharma

Arch log format in asm

I am on single node asm with 10gr3. I changed the arch log format to %t_%s_%r.arc but the files are still getting created as thread_1_seq_90.459.653928775
I have bounced the db already.
SQL> show parameter archive_fo
NAME TYPE VALUE
log_archive_format string %t_%s_%r.arc
SQL>
What else to be setup in order to correct the format?
Thanks.

I believe what you are observing is Alias created by Oracle.
Check logs available at your destination defined by "log_archive_dest_1"
e.g In my case it is +DATA/test
ASMCMD>cd DATA/test
ASMCMD> ls
1_7_653875700.dbf
2_6_653875700.dbf
Now I switch to directory storing alias
ASMCMD>cd ARCHIVELOG
ASMCMD>cd 2008_05_06
ASMCMD>ls
thread_1_seq_7.425.654030021
thread_2_seq_6.363.654040811
Is it clear?
-Amit
http://askoracledba.blogspot.com/

ASM - arch logs

I am using asm for the arch log storage in a two node cluster. I have set parameter log_archive_format to '%t_%s_%r.arc'. But the logs are not getting generated according to the format. Why is that?
Thanks.

Do you use ASM?
log_archive_format....
LOG_ARCHIVE_FORMAT - If you set the LOG_ARCHIVE_FORMAT to an incomplete ASM filename (such as +dgroupA), Oracle will ignore it.

Suggestion for default arch logging behavior

Okay let me throw this out there and see what comes back...
Every Linux distribution I have used (apart from arch) has a boot log file enabled by default, or provides a simple Yes/No flag to turn the feature on.
Arch does not. Moreover, I have searched the forums and posted a question or two myself about the topic. No one seems to know the answer, and a lot of responses seem to indicate that, amongst the arch community, the possibility of a boot log file is treated like: a) something that no one in their right mind would want, or b) something that maybe, might be useful, but that no one can figure out how to implement.
What is this? What is going on? Arch has a bootlogd binary in /sbin/. Presumably there is no reason why it won't actually work, but no one seems to know where to put the call to the binary, or why they would put it there.
This seems like an easy-to-add feature that a developer or moderator (anyone who really knows the system layout well) could make the default for future installs. It just makes a text file that is a) not large, and b) can be very useful at times.
So how about it? Why not make this part of the default arch logging set up? (and of course explain what you did that worked.)

tomk:
Sorry to disclose my ignorance, but I'm not sure how to do that.
What I have been doing though is trying to see in more detail how it is done on a debian system which I have access to. Here is what I've learned so far:
There are not that many references to bootlogd on the system, so it might be possible (for me) to track down what is going on:
root@wave32p:/etc# locate bootlogd
/etc/default/bootlogd
/etc/init.d/bootlogd
/etc/init.d/stop-bootlogd
/etc/init.d/stop-bootlogd-single
/sbin/bootlogd
/usr/share/man/man8/bootlogd.8.gz
1) "/etc/default/bootlogd" must be edited (trivially) such that a "No" becomes a "Yes" -- this seems like just a master switch.
2) the man files are exactly the same on the two systems, and the output of "/sbin/bootlogd -v" is the same on the two systems, however the size of the bootlogd binary itself is not the same on both systems (larger on debian64 system). not sure what to make of that, but it is not what I was hoping to see.
3) the script "/etc/init.d/bootlogd" runs with (eg.) a "start/stop" flag, the same as most "functions" under arch that have scripts associated with them.
4) it would seem that I have to grind my way through the above script if I'm going to make any progress. I'm doing that in my spare time at the moment, though it's a challenge since it's been a few years since I've written bash scripts on a regular basis. FYI, here is the /etc/init.d/bootlogd script verbatim (additional note: the option -r (below) is supported on the arch version of the bootlogd binary, but the -c option does not seem to be...interesting? Here is the man page entry for -c: "Attempt to write to the logfile even if it does not yet exist. Without this option, bootlogd will wait for the logfile to appear before attempting to write to it. This behavior prevents
bootlogd from creating logfiles under mount points."):
#! /bin/sh
### BEGIN INIT INFO
# Provides: bootlogd
# Required-Start: mountdevsubfs
# X-Start-Before: hostname keymap keyboard-setup procps pcmcia hwclock hwclockfirst hdparm hibernate-clean
# Required-Stop:
# Default-Start: S
# Default-Stop:
# Short-Description: Start or stop bootlogd.
# Description: Starts or stops the bootlogd log program
# which logs boot messages.
### END INIT INFO
PATH=/sbin:/bin # No remote fs at start
DAEMON=/sbin/bootlogd
[ -x "$DAEMON" ] || exit 0
NAME=bootlogd
DESC="boot logger"
BOOTLOGD_OPTS="-r -c"
[ -r /etc/default/bootlogd ] && . /etc/default/bootlogd
. /lib/init/vars.sh
. /lib/lsb/init-functions
# Because bootlogd is broken on some systems, we take the special measure
# of requiring it to be enabled by setting an environment variable.
case "$BOOTLOGD_ENABLE" in
[Nn]*)
exit 0
esac
# Previously this script was symlinked as "stop-bootlogd" which, when run
# with the "start" argument, should stop bootlogd. Now stop-bootlogd is
# a distinct script, but for backward compatibility this script continues
# to implement the old behavior.
SCRIPTNAME=${0##*/}
SCRIPTNAME=${SCRIPTNAME#[SK]??}
ACTION="$1"
case "$0" in
*stop-bootlog*)
[ "$ACTION" = start ] && ACTION=stop
esac
case "$ACTION" in
start)
# PATH is set above
log_daemon_msg "Starting $DESC" "$NAME"
if [ -d /proc/1/. ]
then
umask 027
start-stop-daemon --start --quiet --exec $DAEMON -- \
$BOOTLOGD_OPTS
ES=$?
else
$DAEMON $BOOTLOGD_OPTS
ES=$?
fi
log_end_msg $ES
stop)
PATH=/bin:/sbin:/usr/bin:/usr/sbin
log_daemon_msg "Stopping $DESC" "$NAME"
start-stop-daemon --oknodo --stop --quiet --exec $DAEMON
ES=$?
sleep 1
log_end_msg $ES
if [ -f /var/log/boot ] && [ -f /var/log/boot~ ]
then
[ "$VERBOSE" = no ] || log_action_begin_msg "Moving boot log file"
# bootlogd writes to boot, making backup at boot~
cd /var/log && {
chgrp adm boot || :
savelog -q -p -c 5 boot \
&& mv boot.0 boot \
&& mv boot~ boot.0
ES=$?
[ "$VERBOSE" = no ] || log_action_end_msg $ES
fi
restart|force-reload)
/etc/init.d/bootlogd stop
/etc/init.d/bootlogd start
status)
status_of_proc "$DAEMON" "$NAME" && exit 0 || exit $?
echo "Usage: $SCRIPTNAME {start|stop|restart|force-reload|status}" >&2
exit 3
esac

New arch installation, problems with dual monitors

tldr: nvidia setting are not saving when when I leave a session.
yesterday I wiped my computer and went from ubuntu to arch on my desktop (been using arch on laptop for a while). I'm having problems getting my dual monitor settings to save. I configure the settings via nvidia server settings and it works fine but when I go to reboot or log out it goes back down to just one screen and I have reset up nvidia.
gdm has never seen both monitors its always just the single screen.
software
nvidia drivers 280.13
xfce4 v4.8.0
gdm 3.0.4-2
kernal 3.0-arch
my system is up to date with a yaourt -Syu
Sorry if this has been answered but my googlefoo was not strong today.

GDM *should* use a xorg.conf if it exists.... I also noticed that Arch keeps a xorg.conf.d folder, which I'm not sure the nvidia-settings app knows how to handle.
Also, make sure you are running the nvidia-settings app with root privileges, as you'll need those to write a xorg.conf in /etc/X11.

[SOLVED] Just got back to my Arch machine - problems

So, after about a month of not having Internet access, I booted my Arch system today to update everything but of course, I have some problems that are keeping me from doing that. I have Gnome as my DE and when I boot up, I can log in just fine but when I get to the Desktop, I can't click on anything. The mouse moves just fine, the icons even change shade when I put the cursor over them like they can be clicked on but clicking on them does nothing. I have to launch everything with the keyboard, which isn't such a big deal but it's a bit of a nuisance.
The other thing that's bothering me is I have no internet access. I am behind a different router now with an IP of 192.168.1.1 (instead of 192.168.0.1) and I made the appropriate change in the ROUTE variable in rc.conf but it hasn't done anything. I even tried manually adding the default route to the routing table with
#route add -net default gw 192.168.1.1 dev eth0
but that doesn't seem to have done anything either. I have an IP address but I can't ping the router. Oh yeah, and network is listed as a daemon in rc.conf. This is, of course, keeping me from updating my system using pacman.
I may have other problems too but these are the two biggest that I need to get sorted out ASAP so your advice is appreciated. Here is my xorg.conf and a list of processes that are running after boot up.
Section "ServerLayout"
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
# PS/2 Mouse not detected
# Serial Mouse not detected
InputDevice "USB Mouse" "CorePointer"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
EndSection
Section "Files"
RgbPath "/usr/share/X11/rgb"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
# Additional fonts: Locale, Gimp, TTF...
FontPath "/usr/share/fonts/cyrillic"
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" ""
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "Serial Mouse"
Driver "mouse"
Option "Protocol" "Microsoft"
Option "Device" "/dev/ttyS0"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "auto"
Option "ZAxisMapping" "1 2 3 6 7"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mice"
Option "SendCoreEvents" "true"
Option "Protocol" "IMPS/2"
Option "ZAxisMapping" "1 2 3 6 7"
Option "Buttons" "5"
EndSection
# Auto-generated by Archie mkxcfg
Section "Monitor"
Identifier "Monitor0"
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
HorizSync 30.0 - 83.0 # Warning: This may fry old Monitors
VertRefresh 56.0 - 76.0 # Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
# 640x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
# 720x400 @ 85Hz (VESA) hsync: 37.9kHz
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
# 640x480 @ 60Hz (Industry standard) hsync: 31.5kHz
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
# 640x480 @ 72Hz (VESA) hsync: 37.9kHz
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
# 640x480 @ 75Hz (VESA) hsync: 37.5kHz
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
# 640x480 @ 85Hz (VESA) hsync: 43.3kHz
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
# 800x600 @ 56Hz (VESA) hsync: 35.2kHz
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
# 800x600 @ 60Hz (VESA) hsync: 37.9kHz
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
# 800x600 @ 72Hz (VESA) hsync: 48.1kHz
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
# 800x600 @ 75Hz (VESA) hsync: 46.9kHz
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
# 800x600 @ 85Hz (VESA) hsync: 53.7kHz
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
# 1024x768i @ 43Hz (industry standard) hsync: 35.5kHz
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync Interlace
# 1024x768 @ 60Hz (VESA) hsync: 48.4kHz
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
# 1024x768 @ 70Hz (VESA) hsync: 56.5kHz
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
# 1024x768 @ 75Hz (VESA) hsync: 60.0kHz
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
# 1024x768 @ 85Hz (VESA) hsync: 68.7kHz
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
# 1152x864 @ 75Hz (VESA) hsync: 67.5kHz
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
# 1280x960 @ 60Hz (VESA) hsync: 60.0kHz
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
# 1280x960 @ 85Hz (VESA) hsync: 85.9kHz
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
# 1280x1024 @ 60Hz (VESA) hsync: 64.0kHz
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 75Hz (VESA) hsync: 80.0kHz
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
# 1280x1024 @ 85Hz (VESA) hsync: 91.1kHz
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
# 1600x1200 @ 60Hz (VESA) hsync: 75.0kHz
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 65Hz (VESA) hsync: 81.3kHz
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 70Hz (VESA) hsync: 87.5kHz
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 75Hz (VESA) hsync: 93.8kHz
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1600x1200 @ 85Hz (VESA) hsync: 106.3kHz
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
# 1792x1344 @ 60Hz (VESA) hsync: 83.6kHz
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
# 1792x1344 @ 75Hz (VESA) hsync: 106.3kHz
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
# 1856x1392 @ 60Hz (VESA) hsync: 86.3kHz
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
# 1856x1392 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
# 1920x1440 @ 60Hz (VESA) hsync: 90.0kHz
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
# 1920x1440 @ 75Hz (VESA) hsync: 112.5kHz
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
# Additional modelines
ModeLine "1800x1440" 230 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
ModeLine "1800x1440" 250 1800 1896 2088 2392 1440 1441 1444 1490 +HSync +VSync
# Extended modelines with GTF timings
# 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz
ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync
# 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz
ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync
# 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz
ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync
# 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz
ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync
# 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz
ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync
# 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz
ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync
# 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz
ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync
# 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz
ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync
# 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz
ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync
# 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz
ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync
# 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz
ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync
# 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz
ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync
# 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz
ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync
# 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz
ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync
# 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz
ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync
# 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz
ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync
# 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz
ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync
# 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz
ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync
# 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz
ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync
# 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz
ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync
# 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz
ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync
EndSection
# Auto-generated by Archie mkxcfg
Section "Device"
Identifier "Card0"
Driver "ati"
VendorName "All"
BoardName "All"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultColorDepth 16
SubSection "Display"
Depth 1
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1920x1200" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1920x1200" "1024x768" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 32
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
PID TTY TIME CMD
1 ? 00:00:00 init
2 ? 00:00:00 migration/0
3 ? 00:00:00 ksoftirqd/0
4 ? 00:00:00 watchdog/0
5 ? 00:00:00 migration/1
6 ? 00:00:00 ksoftirqd/1
7 ? 00:00:00 watchdog/1
8 ? 00:00:00 events/0
9 ? 00:00:00 events/1
10 ? 00:00:00 khelper
11 ? 00:00:00 kthread
35 ? 00:00:00 kblockd/0
36 ? 00:00:00 kblockd/1
37 ? 00:00:00 kacpid
121 ? 00:00:00 kseriod
140 ? 00:00:00 pdflush
141 ? 00:00:00 pdflush
142 ? 00:00:00 kswapd0
143 ? 00:00:00 aio/0
144 ? 00:00:00 aio/1
651 ? 00:00:00 ata/0
652 ? 00:00:00 ata/1
653 ? 00:00:00 ata_aux
658 ? 00:00:00 scsi_eh_0
659 ? 00:00:00 scsi_eh_1
998 ? 00:00:00 kjournald
1034 ? 00:00:00 ksuspend_usbd
1037 ? 00:00:00 khubd
1053 ? 00:00:00 udevd
2988 ? 00:00:00 kpsmoused
3350 ? 00:00:00 khpsbpkt
3401 ? 00:00:00 knodemgrd_0
4327 ? 00:00:00 kjournald
4330 ? 00:00:00 kjournald
4374 ? 00:00:00 syslog-ng
4401 ? 00:00:00 crond
4414 ? 00:00:00 gdm-binary
4416 ? 00:00:00 gdm-binary
4418 tty7 00:00:03 X
4428 tty1 00:00:00 agetty
4429 tty2 00:00:00 agetty
4430 tty3 00:00:00 agetty
4431 tty4 00:00:00 agetty
4432 tty5 00:00:00 agetty
4433 tty6 00:00:00 agetty
4483 ? 00:00:00 gnome-session
4504 ? 00:00:00 gconfd-2
4507 ? 00:00:00 gnome-keyring-d
4512 ? 00:00:00 dbus-launch
4513 ? 00:00:00 dbus-daemon
4514 ? 00:00:00 dbus-daemon
4516 ? 00:00:00 gnome-settings-
4522 ? 00:00:00 mapping-daemon
4525 ? 00:00:00 metacity
4529 ? 00:00:01 gnome-panel
4533 ? 00:00:00 bonobo-activati
4535 ? 00:00:00 nautilus
4542 ? 00:00:00 gnome-vfs-daemo
4548 ? 00:00:00 wnck-applet
4561 ? 00:00:00 mixer_applet2
4563 ? 00:00:00 notification-ar
4566 ? 00:00:01 gnome-terminal
4569 ? 00:00:00 gnome-pty-helpe
4570 pts/0 00:00:00 bash
4608 pts/0 00:00:01 epiphany
4620 pts/0 00:00:00 pacman
4621 pts/1 00:00:00 bash
4653 pts/1 00:00:00 ps
Last edited by Thrillhouse (2007-07-12 21:34:21)

Hello,
I am behind a router and had to do only very minor tweaks to get it going: just enter the value of the gateway and remove the ! before gateway within the routes variable. Here is the (expanded) relevant part of my rc.conf, I hope it helps you:
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available
# interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
lo="lo 127.0.0.1"
eth0="eth0 10.0.0.3 netmask 255.255.255.0 broadcast 10.0.0.255"
INTERFACES=(lo eth0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 10.0.0.2"
ROUTES=(gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network-profiles

[solved] 2.6.20-ARCH - poweroff problems

Hi guys.. i've a problem with the last kernel of Arch..
When i turn off my computer, instead to switch off the power, it reboot my machine
The "old" 2.6.19-ARCH work fine
some info:
~> uname -a
Linux skynet 2.6.20-ARCH #1 SMP PREEMPT Tue Feb 6 10:39:12 CET 2007 i686 Intel(R) Pentium(R) 4 CPU 3.00GHz GenuineIntel GNU/Linux
~> cat /etc/arch-release
Arch Linux 0.8 (Voodoo)
MB: asus P5P800
dmesg is ok.. no one strange error messages
help!
Last edited by slux (2007-02-17 16:19:08)

up
Last shootdown kernel log.. NOTHING!
Feb 10 13:57:02 skynet [drm] Setting GART location based on new memory map
Feb 10 13:57:02 skynet [drm] Loading R200 Microcode
Feb 10 13:57:02 skynet [drm] writeback test succeeded in 1 usecs
Feb 10 13:57:11 skynet eth0: no IPv6 routers present
Feb 10 20:23:46 skynet cdrom: This disc doesn't have any tracks I recognize!
Feb 10 20:35:52 skynet ISO 9660 Extensions: Microsoft Joliet Level 3
Feb 10 20:35:52 skynet ISO 9660 Extensions: RRIP_1991A
the new restart...
Feb 11 09:56:34 skynet Linux version 2.6.20-ARCH (root@Laptop) (gcc version 4.1.2 20061215 (prerelease)) #1 SMP PREEMPT Tue Feb 6 10:39:12 CET 2007
Feb 11 09:56:34 skynet BIOS-provided physical RAM map:
Last edited by slux (2007-02-11 10:45:45)

Windows 7 and Arch (GRUB problem)

Hello I'm a new user in Arch and almost new in linux (well i need to work at university with linux so i'm not such a newb). I was using Windows 7 for a while and i installed Arch linux for programming. Everything installed very well and i really like Arch linux. But there is one problem, when GRUB boots i can choose between Arch and Windows and while i boot Arch everything is Ok, but the problem is when i boot Windows and it disables my GRUB (GRUB is installed in boot partition 200mb) well not disables, but just takes of Boot option (flag?) from boot partition and GRUB doesn't loads. so all the time after Windows usage i must run cfdisk and make boot partition bootable and remove root from windows.
Maybe anyone knos how to solve this problem or they have encountered such problem and fixed it.
If u need any code from GRUB say i will post it later, now i need to finish program in Windows.
P.S. i have surfed/serached forum for few days about such problem and found nothing... (maybe i'm blind?)

Firstly, normal people (atleast those i have communicated) don't critisize for grammar mistakes because everyone makes such mistakes. Second i prefer my mother langue more than other and i don't even bothered to learn english like i learned lithuanian langue.
Secondly, yeah if you would read news about computing and etc. you should know that there isn't full windows 7 there is windows 7 BETA, well i personally just forgot that work(mistake maybe? or i prefer not to say beta words with programm because i work mostly with beta programms).
And yeah Windows 7 was first installed (doh, if you would think more that fact would be clear because i wrote "I WAS using Windos 7 for a while..."

OS X kernel logs problem when USB flash drive connected.

Previously, my Creative Nomad Muvo TX (MP3 player/1GB USB memory stick) worked fine with my Intel Mac mini (10.4.8) until the latest EFI 1.1 update.
Now the USB drive does not mount or appear in finder. It is visible in the System Profiler in the USB section, but the disk utility does not see it.
While the USB stick is plugged in, the system logs the following line repeatedly:
Nov 26 21:32:39 kernel[0]: USBF: 2517.425 AppleUSBEHCI[0x3969000]::Found a transaction past the completion deadline on bus 253, timing out!
Booting in Windows XP (with bootcamp) and plugging in the USB memory stick works fine. So the USB stick and the Mac mini hardware is functioning.
Other USB 2 external harddrives are functioning properly in OS X.
I suspect that the latest Mac OS X or EFI 1.1 firmware update has spoilt my previously happy USB memory stick connection.
Any suggestions?
Thanks in adcvance.
Stephanus

Hi, Stephanus.
1. If Creative does not support that device with a Mac, then that should tell you something. Even if it worked in the past, since they don't support it, there's no guarantee that changes to Mac OS X would render it unusable as you've noted. With that kind of attitude from Creative, I'd think about switching to an iPod...
Since you can use it when booted into Windows with Boot Camp, you might want to consider running Parallels Desktop for Mac. This leverages the virtualization technology of the Intel chips, permitting you to run Mac OS X and Windows simultaneously, rather than having to boot into Windows with Boot Camp. Parallels is cheaper than buying an iPod.
2. The USB message you reported is essentially indicating that the OS detected a USB device but cannot talk to it. This is unlikely to be something you're going to work around, e.g. with Terminal.
3. If you want to pursue this further, you can:3.1. Install the USB debug kit for your version of Mac OS X. Apple provides a variety of Mac OS X USB Software Debug Versions that "are used to provide information about USB device and interface detection, driver and interface matching, driver loading and information generated as a result of normal and abnormal conditions." You could install the package corresponding to the version of Mac OS X you are running and this may help identify if the issue is a USB problem and the exact USB anomaly causing such.
3.2. Take what you've been able to lear from the USB debugger and do one or more of the following:• Join the Apple USB Mailing List. Once your registration is approved, submit a question including the enhanced output from the USB logger and requesting additional advice. That list is monitored by developers of USB devices. Posts are sometimes answered by Apple engineers.
• Join the Apple Developer Connection at the "free" level, then submit a bug report.
• Submit a Mac OS X Feedback.If Creative has their own forums, ala Discussions, you might also want to search or post there for similar reports.Unfortunately, that's about all I have to offer at this point: I don't have the Creative device and hence can't test it.
I think that Creative is disinterested in helping you is a key issue you need to consider.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X

DMEE Log problem

Hi Specialist
I created a payment medium using the transaction F110. In the Log Poporsal I didnt find any error, but in the payment log I found it:
BFIBL02167 Document 2000 1400259728 2011 either not found or reversed, payment not on payment medium
The payment was 04.11.2011 and the reversal on 14.11.2011 .. but in my file I couldnt find some documents according to the error.
After that I investigate in the transaction FBPM ( LOG ERROR Payment medium )
And I found more information:
Document 2000 1400259728 2011 either not found or reversed, payment not on payment medium
Message no. BFIBL02167
Diagnosis
In the payment document validation that you selected in the selection variant of the generic payment medium program SAPFPAYM, the system determines that payment document 2000 1400259728 2011 has either not yet been posted or has already been reversed.
System Response
The payment is not transferred on a payment medium in order to avoid a duplicate payment: the items to be paid remain open and could be paid again with a new payment run.
Procedure
If, for an update termination, you find it is then possible to post the document, you can subsequently create another payment medium only containing this missing document. To do this, in the dynamic selections select only the reference to document 200014002597282011
DO you know why I get this error?? The payment was succesfully but I couldnt find it in my DMEE estructure ( the file ) .
THank you
Regards

Hi , thanks for reply.
Not really. I created the payment method 04.11.2011 and I sent the file to the bank. The problem was the rejection that I received 14 days later.
Then when i check the file again I found this errors.
It means that I generate the and the payment the same day.
Thanks

Hello! console log problem with window server

Hello! I installed today moutain lion, it's all perfect but i have a question...i was checking the console log, and there are a lot of messages like that:
26/07/12 00:04:10,682 WindowServer[89]: CGXRegisterWindowWithSystemStatusBar: window c already registered
26/07/12 00:04:17,796 WindowServer[89]: CGXRegisterWindowWithSystemStatusBar: window c already registered
26/07/12 00:04:42,979 WindowServer[89]: CGXRegisterWindowWithSystemStatusBar: window c already registered
26/07/12 00:04:46,366 WindowServer[89]: CGXRegisterWindowWithSystemStatusBar: window c already registered
everytime i swap to a full-screen app, a new line of that appear..hmm..it's ok or there are some problems?
thanks in advance!

cool! 'cause if i go to the app by mission control, console is clean...if i swap with the gesture..there is the log! maybe it's a feature of mountain lion by the way, pratically there aren't problem, only the massive logging in console..

Arch log problem

Similar Messages

Maybe you are looking for