search for: nosupported

Displaying 9 results from an estimated 9 matches for "nosupported".

Did you mean: notsupported
2005 May 26
0
Review about uid and gid mount option
Hi everybody! I had a problem (now solved) with the UIDs and GIDs assigned to my SMB filesystem once mounted. I have discovered several things and I wanted to send my review to the list, maybe you'll find it usefull or maybe you could add more info. First of all let's describe the problem: I mount my SMB share (SAMBA 3.0.14a server) on my local filesystem (Linux box), but
2008 Nov 23
1
SendImage()
SendImage() in 1.4: ---cut--- SendImage(filename): Sends an image on a channel. If the channel supports image transport but the image send fails, the channel will be hung up. Otherwise, the dialplan continues execution. The option string may contain the following character: 'j' -- jump to priority n+101 if the channel doesn't support image transport This application sets the
2003 Jun 30
0
outgoing calls with packet8 and dta310 problems
...dta310 and from packet8, but I haven't managed to get the phone to actually place invites through asterisk. On the asterisk end with chan_oss.so, I can make it dial and I hear ringing and the first second of conversation, but after that it drops the call with a message along the lines of "nosupported codecs in SDP" or somesuch. If anyone wants it, I can get the full message when I get home. When I try to use the DTA310, asterisk complains about authentication on SUBSCRIBE requests. Here is the relevant info in my sip.conf file: register =>0123456789@packet8.net/0123456789 ;the 01234...
2001 Dec 17
1
CVS update: rsync
On 14 Dec 2001, dwd@samba.org wrote: > open_socket_in was attempting to try all the protocols returned from > getaddrinfo(), but only if a corresponding call to socket() returned one of > three *NOSUPPORT errno codes. A Redhat 6.2 system was observed returning > EINVAL instead so it never went on to try IPv4. This update adds EINVAL to > the list. Question: why not always
2005 Feb 20
0
[LLVMdev] Attempt #1: JIT Thread Safety
This is what I was trying to do when I ran into the HowToUseJIT problem. I've made a first attempt at adding locking to the JIT. Unfortunately, since I do not really understand the structure of LLVM, I could have very easily screwed something up. I touched two classes, the JIT and the ExecutionEngine. I need some help from someone who is more familiar with the code to make sure that I
2004 Nov 15
0
[LLVMdev] Fixes for windows version
Morten, I've applied these patches. Thanks for the updates! Reid. On Mon, 2004-11-15 at 01:26, Morten Ofstad wrote: > Hi, > > when I updated the sources today there were several small problems that > stopped the windows version from compiling, here are the patches > > m. > > > ______________________________________________________________________ > Index:
2004 Nov 15
2
[LLVMdev] Fixes for windows version
Hi, when I updated the sources today there were several small problems that stopped the windows version from compiling, here are the patches m. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: win32patches.txt URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20041115/34634455/attachment.txt>
2004 Dec 03
0
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
On Fri, 3 Dec 2004, Reid Spencer wrote: > Could someone please apply this patch to the Win32 support so that > Morten and Jeff can handle the recent changes? I can't do it because > I"m on the road with only email access. I'd be happy to do it. Can someone send me the patch as an attachment off-list? -Chris > > <Tool > >
2004 Dec 03
2
[LLVMdev] [Fwd: Updated LLVM Visual Studio project files]
Could someone please apply this patch to the Win32 support so that Morten and Jeff can handle the recent changes? I can't do it because I"m on the road with only email access. Thanks, Reid. -----Forwarded Message----- > From: Morten Ofstad <morten at hue.no> > To: Reid Spencer <reid at x10sys.com> > Subject: Updated LLVM Visual Studio project files > Date: Thu,