|
|
Thread Tools | Search this Thread | Display Modes |
10-20-2014, 02:12 PM | #21 | |
Junior Member
Join Date: Oct 2013
Posts: 18
|
Quote:
|
|
10-23-2014, 07:20 PM | #22 |
Junior Member
Join Date: Oct 2014
Posts: 1
|
Have should I write in the report for Apple? I want to file a bug report also but not sure what I should write to make it more accurate and less prone to be rejected.
|
11-08-2014, 09:04 PM | #23 |
Junior Member
Join Date: Nov 2014
Posts: 4
|
I've made a configuration file for ASL to claim all these messages and then ignore them. Seems to be a reasonable solution until such time as a bug fix is available.
http://blog.jamesball.co.uk/2014/11/...nk-driver.html |
11-10-2014, 10:24 AM | #24 |
Junior Member
Join Date: Nov 2014
Posts: 1
|
A finer workaround would be to add
? [= Sender WindowServer] ignore in the first line of asl.conf (in the etc directory) and then restart syslog by issuing kill -hup <PID> where PID is the syslog process pid This will filter out only WindowServer messages instead of cutting all the syslog output |
11-12-2014, 01:48 PM | #25 |
Junior Member
Join Date: Oct 2013
Posts: 18
|
Disregard.
Last edited by BMT; 11-27-2014 at 10:11 PM. Reason: Problem fixed. |
11-12-2014, 06:36 PM | #26 |
Junior Member
Join Date: Nov 2014
Posts: 1
|
I seem to have stopped the log spam by adding this to my asl.conf in /etc at the top of the file
? [= Sender WindowServer] ignore And then performing the sudo kill -HUP [PID of process] Not sure if that's OK, I tried the other way of creating a file under the asl folder and that did nothing for me. Hope this helps, even if its just towards finding a better answer! |
11-13-2014, 05:18 PM | #27 |
Member
Join Date: Aug 2011
Posts: 39
|
I changed it a little bit to:
# WindowServer messages about display context (caused by DisplayLink driver) ? [= Sender WindowServer] [= Level Warning] [A= Message _CGXGLDisplayContextForDisplayDevice] claim only Seems to be working and ensures that any other messages from WindowServer are still going in. |
11-20-2014, 09:42 PM | #28 |
Member
Join Date: Aug 2011
Posts: 39
|
No more messages since I've put this in. Interesting that with all the complaining about this within the forums that DisplayLink was never able to provide this as a solution.
Is it perfect? No. Is it something Apple should fix? yes Does the work-around work? Heck yes. Could DisplayLink provide the work-around? Don't see why not. |
11-21-2014, 08:12 AM | #29 |
Mac Team
Join Date: Feb 2009
Posts: 606
|
Hi ehendrix,
Sorry for going quiet on this one. Yes we think this is a good workaround, we could apply it at install time. We'd use ? [= Sender WindowServer] [=S Message_CGXGLDisplayContextForDisplayDevice] ignore Unless anyone can spot any issue with the approach? Cheers, Carlo |
11-26-2014, 03:43 PM | #30 | |
Junior Member
Join Date: Nov 2014
Posts: 4
|
Quote:
James |
|
Tags |
windowserver |
|
|