search for: intruduced

...the logs, so I　didn't copy those. http://zanshin.tsumelabs.com/ The system was working a couple days ago until I had the server rebooted. there are 2 zap cards, both are working fine, all lines are able to recieve phone calls. The problem is callers call the building and they are intruduced to the weekday message, then when they hit 1 they are placed in a queue for appointments. They are always on hold and the receptionist phone doesn't ring. What could be the problem? receptionist == 101 Tsume

Hello, trying to update to the latest kexec version I'm blocked by the lack of basename() and vfscanf() in klibc. I've noticed it only recently because I'm building almost exclusively for arm. This commit intruduced the issue: http://git.kernel.org/cgit/utils/kernel/kexec/kexec-tools.git/commit/kexec/arch/i386/x86-linux-setup.c?id=3bf0213789d56054f601c5a06372f78567aacdd9 Has anybody already a fix? Suggestions? TIA Andrea

Ok, I'm sure you've answered this more then once, but still here it is : I have a FoxPro 2.0 for Lan application that used to run on DOS boxes connected to a Novell server (and of course with Novel client). Both FoxPro .exe, .prg and database/index files reside on the shared disk, and the client only maps a shared drive and starts the FoxPro application from there. Due to some

.... I take the raw 44100 Hz on my mac and just do a loop averaging every 5.5 samples to 1 sample to get 8018.18 Hz, and feed that to speex in 160 sample buffers. I realize that this introduces some aliasing, and I may try the new speex resampler, but I find it hard to believe that the noise intruduced would be higher than normal background anyway, and it sounds clear enough when I just do playthrough for testing. The problem is, this uses nibbling, which means the input jitters in time in relation to the output. I also don't know what Apple does under the hood for playback, they al...

Hi everyone, How can I introduce some distortion, echo, chopping sound and all other bad quality things that can happen to a SIP trunk? I have plenty of bandwidth and crisp clear lines so the only thing that I can think of is to limit bandwidth but even that requires quite some scripting work. Is there any easy way to simulate a distorted SIP line temporarily for testing? I am appreciate

...rror: failed build dependencies: db1-devel is needed by openssh-3.6.1p1-1 caused by this part of the specfile: %if ! %{build6x} BuildPreReq: glibc-devel, pam %else BuildPreReq: db1-devel, /usr/include/security/pam_appl.h %endif There is no db1 package in Redhat 6.x, db1 was intruduced in 7.x. In Redhat 6.x the contents of db1 are part of the glibc package. It seems like that the condition is the wrong way around. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Hi, I have been doing some work on a fixed-point port and it is now in CVS. All of the CPU-intensive parts should now be using only integer operations. Now, it's in a state where even non-coders can help: find bugs. With all these changes, there are probably several bugs and some may show up only under specific circumstances. Please test to see if the fixed-point behaves the same as the

Hello everyone, ff123 compiled Monty's branch of the RC1 encoder, see his post on r3mix.net forum: http://66.96.216.160/cgi-bin/YaBB.pl?board=c&action=display&num=994299736&start=30 Anyway it only supports ~128kbps mode, so I did a quick listening test with some files that bugged vorbis beta4. grace.wav - the right channel is still a bit watery, and I think this can be seen

...e: > Initially Bourne was used because it was typically a static binary, > because the boot process didn't have access to any shared libraries. > When that changed it became a bit of a moot point, and you started to > see other interpreters being used. When dynamic linking was intruduced in 1988, people did kno know what we now know and provided sh, mv, tar, ifconfig and mount as statib binaries in "/sbin". Since Solaris 10 we know better and there is no static binary anymore. BTW: the real Bourne Shell is now 100% portable and enhanced since a longer time. If you lik...

It was the mid/late-90s, but I seem to recall Bourne being the default shell, although sh/ksh/csh were all available with a typical install. On Fri, Apr 24, 2015 at 8:32 AM, Scott Robbins <scottro at nyc.rr.com> wrote: > On Fri, Apr 24, 2015 at 08:02:56AM -0400, mark wrote: > > On 04/24/15 06:57, Pete Geenhuizen wrote: > > > > > >On 04/24/15 06:07, E.B. wrote:

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

...assed to the SMB_VFS_NTIMES() VFS function. VFS modules can check whether any of the time values inside a struct smb_file_time is to be ignored by calling is_omit_timespec() on the value. 'io_uring' vfs module --------------------- The module makes use of the new io_uring infrastructure (intruduced in Linux 5.1), see https://lwn.net/Articles/776703/ Currently this implements SMB_VFS_{PREAD,PWRITE,FSYNC}_SEND/RECV and avoids the overhead of the userspace threadpool in the default vfs backend. See also vfs_io_uring(8). In order to build the module you need the liburing userspace library and i...

Hi everyone! I've been silently working on the previous exception handling proposal I published last year (http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-November/027311.html). However, there were some major deficiencies in it. After discussing this further with Jim Grosbach and John McCall, we've come up with another proposal. As you can see, it incorporates the idea of