search for: upshot

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 's...

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 's...

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 's...

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 's...

Hello, It's been noticed that mailing list monthly rollovers didn't happen because the machine was down when the cronjob to do the rollover would normally have fired. I will trigger them by hand now... upshot is that I'm not bothering to refile the first five days of May in the correct slot. I sincerely hope that no one cares :-) Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 's...

...bly. If we originate the call, we can hang it up. This suggests to me that the Sangoma A200D is sending the correct hangup signaling. This way round, it is 100% reliable. If we accept a call originated elsewhere, then we cannot hang it up. Only the call originator seems to be able to do that. The upshot is that if asterisk hangs-up a line, and then tries to re-use it for an outbound call before the remote has disconnected, we are simply re-connected to the original caller, and start to play DTMF at them! Has anyone experienced this before? Anyone found a solution? Thanks, Steve

Apologies if this is the wrong place to post this question. In that event, please point me in the right direction. My question is whether or not I can use Xen with OpenMosix. The upshot of what I''m attempting to do is this: 1. Build a two to four node cluster using OpenMosix for "raw horsepower" 2. Use Xen on the OpenMosix cluster to divide the "raw horsepower" any way that I need it I am specifically interested in setting up two or more Xen Domains...

...ction is supposed to "behave[s] the same way as the Authenticate application, but the passwords are taken from voicemail.conf." The problem is that it always gives the "comedian mail" prompt and requests the mailbox number, even though I provide the mailbox number already. The upshot is that VMAuthenticate is not working like Authenticate and makes the user think they are connecting to voicemail. My motivation to use VMAuthenticate was to provide for a single password (the voicemail password seemed like a good idea) for users to do various things. Am I missing the point of VM...

Presumably you *know* it was working because of my screenshots page, so I'll answer :) The upshot is Nesticle got broken when the TransGaming stuff started landing in December. The basic problem is that the new code was for DirectX7, while Nesticle is a DX5 app. I believe there's been some work to fix that - I'll check latest CVS later today. -- Ian Schmidt - ischmidt [at] cfl [d...

...ord=PASSWORD --domain=DOMAIN Result: NT_STATUS_OK: Success (0x0) Scenario B: FAILS Type: ntlm_auth --username=USER --domain=DOMAIN password: <PASSWORD> Result: NT_STATUS_WRONG_PASSWORD: Wrong Password (0xc000006a) What's different about the password handling between A and B? The upshot is that the command issued by FreeRADIUS: ntlm_auth = "/usr/sfw/bin/ntlm_auth --request-nt-key --username= %{Stripped-User-Name:-%{User-Name:-None}} --challenge=%{mschap:Challenge:-00} -- nt-response=%{mschap:NT-Response:-00}" the %{} bits become a basic domain free user name, eg "...

.... The cairoDevice package has a few stand-alone functions, plus "asCairoDevice" which depends on RGtk2 and calls require(RGtk2). So cairoDevice lists RGtk2 under "Suggests" in the DESCRIPTION file. It can not Import RGtk2 because that would force all users to install RGtk2. The upshot of this is, if you *import* the RGtk2 namespace into another package and then call asCairoDevice(), RGtk2 is attached to the user's search path. That is significant because RGtk2 exports a large number of objects: -- 7476 to be exact -- which can clog up things like help.search and autocompleti...

...ware that the version of portmap distributed is the enhanced (Wietse Venema) version. That's great, except for two things. The first is documented, but easy to overlook: "In order to avoid deadlocks, the portmap program does not attempt to look up the remote host name or user name...The upshot of all this is that only network number patterns will work for portmap access control." I didn't realize that, and boy did I get bitten when I refused connections from "unknown" hosts (where DNS doesn't reverse correctly). I was using the "same" hosts.allow file I...

...te the use of landing pads for destructing locals. Instead the LSDA would encode the pc liveness ranges of local objects, their location in the stack frame, and their destructor functions. Then the new personality function would iterator through the LSDA and call the appropriate destructors. The upshot is that functions will be smaller (no landing pad code) and there would be no landing pads in the bitcode (except for catch clauses). This is better aligned with the "zero cost" (if not used) exception model then what we currently have. There are a number of details to work out in havi...

I notice that the installation of Asterisk 1.8.8 thru 1.8.10 (probably earlier versions too) remove the group write permissions from /etc/asterisk/. which is different than 1.4. And 1.6. Is this expected behavior? If so, what's the rationale? If not, I'll submit a bug report if someone hasn't beaten me to it. -K -------------- next part -------------- An HTML attachment was

On Monday 11 December 2017 18:50:06 Akemi Yagi wrote: > ?As far as I know, the contents on the CentOS wiki are for CentOS 7.3 (or > earlier) and a patch is needed to use the driver under 7.4. > > You may want to go to the ELRepo article that is referenced on that page ( > http://elrepo.org/tiki/wl-kmod > ? )?. The ELRepo instructions are up to date and should cover EL7.4. >

...how to fix it. > > For those interested, it involved pressing F9 at boot time to select the > boot > menu and selecting the Centos option. This then went through GRUB as normal > and booted. I then used 'eftbootmgr -o' to define the correct boot > sequence. > > The upshot is that I now have a laptop that boots correctly, and that > successfully uses the built in Broadcom WiFi adaptor. > > Thanks everyone for your help > ?Glad to hear things are now working for you. Just wanted to add a note that you can use ELRepo's drivers with SecureBoot enabled...

...te the use of landing pads for destructing locals. Instead the LSDA would encode the pc liveness ranges of local objects, their location in the stack frame, and their destructor functions. Then the new personality function would iterator through the LSDA and call the appropriate destructors. The upshot is that functions will be smaller (no landing pad code) and there would be no landing pads in the bitcode (except for catch clauses). This is better aligned with the "zero cost" (if not used) exception model then what we currently have. > > There are a number of details to work ou...

On Nov 29, 2010, at 12:17 AM, Duncan Sands wrote: >> This is well-formed SSA; the alloca instruction %x is in the entry block and thus dominates both the store in %try and the load in %catch... > > this brings up the question of whether we should allow a catch handler to be > attached to the entry block. My feeling is that it should be disallowed. If > it was allowed then

Hi everbody this is my first post, I have two test server .(Both of them is idle) db1 : RHEL4 OCFS2 db2 : RHEL3 OCFS I test the IO both of them The result is below. db1(Time Spend)db2(Time Spend)OS Test Command dd (1GB) (Yazma)0m0.796s0m18.420stime dd if=/dev/zero of=./sill.t bs=1M count=1000 dd (1GB) (Okuma)0m0.241s8m16.406stime dd of=/dev/zero if=./sill.t bs=1M count=1000 cp

Hi everbody this is my first post, I have two test server .(Both of them is idle) db1 : RHEL4 OCFS2 db2 : RHEL3 OCFS I test the IO both of them The result is below. db1(Time Spend)db2(Time Spend)OS Test Command dd (1GB) (Yazma)0m0.796s0m18.420stime dd if=/dev/zero of=./sill.t bs=1M count=1000 dd (1GB) (Okuma)0m0.241s8m16.406stime dd of=/dev/zero if=./sill.t bs=1M count=1000 cp