search for: concequ

...In a particular environment, "WORKGROUP\username" does not have access to the user's home directory. If we add "workgroup =" parameter in smb.conf file, it now passes. Is it valid to always to specify a "" workgroup value in the config file ? Does that have other concequences ? Mike

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Once installed, the python library of Xen are not in the python search path. Concequently, it's impossible to import anything from the xen-utils in another application. The only way to fix it is to do: cd /usr/lib/python2.5/site-packages ln -s /usr/lib/xen-3.2-1/lib/python/xen xen xen-utils-3.2-1 should in fact use the folder /usr/lib/python2.5/site-packages, and not /usr/lib...

...text as well as error messages will definately require translation. I have looked at the gettext article, the new globalization plugin, and the localization plugin. Each appears to have some strengths / weaknesses. Since this is critical to the app and any strategy has potentially far-reaching concequences, I''m looking for input from those who have tried any/all of these solutions. Anyone using these approaches? Pros/cons/gotchas? Any other approaches I might need to consider? TIA, Keith -- Posted via http://www.ruby-forum.com/.

...tton.lid_init_state=open/close 1. button driver sends open/close to input layer after boot/resume 2. button driver sends _LID return value to i915 after boot/resume (PATCH 4) So that i915 can just use the notified value in this patch (PATCH 5). For nouveau, no change has been made for now, and as a concequence, acpi_lid_open() is still kept but marked as deprecated. > > See my reply of PATCH 4. > It seems they trust _LID return value more than what we send to them. > > We can actually send faked "open/close" to them when button.lid_init_state=open/close is specified. >...

Any tips on solving the following performance conundrum: Asterisk 1.8.12.2 running on HP DL360 G5 and G7s tcpdump running to capture UDP 5060/SIP signaling to .pcap files All calls are ultimately B2BUA client -> asterisk -> PSTN Media stays on Asterisk at all times AGI script has exit handler that connects and updates an external database upon BYE from either side. I know that if exit

...appening. > 1. button driver sends open/close to input layer after boot/resume > 2. button driver sends _LID return value to i915 after boot/resume (PATCH 4) > So that i915 can just use the notified value in this patch (PATCH 5). > For nouveau, no change has been made for now, and as a concequence, acpi_lid_open() is still kept but marked as deprecated. > >> >> See my reply of PATCH 4. >> It seems they trust _LID return value more than what we send to them. >> >> We can actually send faked "open/close" to them when button.lid_init_state=open/clo...

On Tue, May 9, 2017 at 9:02 AM, Lv Zheng <lv.zheng at intel.com> wrote: > Since notification side has been changed to always notify kernel listeners > using _LID returning value. Now listeners needn't invoke acpi_lid_open(), > it should use a spec suggested control method lid device usage model: > register lid notification and use the notified value instead, which is the >

...1. button driver sends open/close to input layer after boot/resume > > 2. button driver sends _LID return value to i915 after boot/resume (PATCH 4) > > So that i915 can just use the notified value in this patch (PATCH 5). > > For nouveau, no change has been made for now, and as a concequence, acpi_lid_open() is still kept > but marked as deprecated. > > > >> > >> See my reply of PATCH 4. > >> It seems they trust _LID return value more than what we send to them. > >> > >> We can actually send faked "open/close" to them...

...river sends open/close to input layer after boot/resume >> > 2. button driver sends _LID return value to i915 after boot/resume (PATCH 4) >> > So that i915 can just use the notified value in this patch (PATCH 5). >> > For nouveau, no change has been made for now, and as a concequence, acpi_lid_open() is still kept >> but marked as deprecated. >> > >> >> >> >> See my reply of PATCH 4. >> >> It seems they trust _LID return value more than what we send to them. >> >> >> >> We can actually send faked &qu...