similar to: Name mangling problem

----- Forwarded message from "John T. Guthrie" <guthrie@counterexample.org> ----- From: "John T. Guthrie" <guthrie@counterexample.org> Subject: Comment on a web page Date: Fri, 23 Aug 2002 19:20:06 -0400 To: webmaster@samba.org To Whom It May Concern, I was just looking at your Samba Printing Support Page: http://us1.samba.org/samba/docs/man/printer_driver2.html

Hello all, When I try to add a user to my secrets.tdb file on my Samba 3.2.0 PDC, the users are always added under the local machine domain, not the global domain. That is, if my PDC machine name is srv1, and it is PDC for the domain DOM1, then whenever I add a user using "pdbedit -a -u username", then that user gets placed under the local domain SRV1, not the global domain DOM1. So my

'Twas brillig, and Colin Guthrie at 06/12/10 15:10 did gyre and gimble: > 'Twas brillig, and Sherief N. Farouk at 06/12/10 14:52 did gyre and gimble: >> How much latency are we talking about? It seems that this issue cannot be >> easily pinpointed, but if it turns out to be related to the Speex Resampler >> let me know and I will put it on my task list. > > Will

How much latency are we talking about? It seems that this issue cannot be easily pinpointed, but if it turns out to be related to the Speex Resampler let me know and I will put it on my task list. - Sherief -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On Behalf Of Colin Guthrie Sent: Monday, December 06, 2010 9:47 AM To: speex-dev at

If you can produce a simple minimal repro that exhibits this issue on some procedural signal (sine wave, etc) I'd love to look into it some more - I'm maintaining a hardened version of the Speex Resampler and would be very concerned if this bug made it into production. - Sherief -----Original Message----- From: speex-dev-bounces at xiph.org [mailto:speex-dev-bounces at xiph.org] On

Colin, If you're using stereo audio with the resampler, there is a bug that can occur under certain situations (and maybe that's what's been happening to you). Check out: http://lists.xiph.org/pipermail/speex-dev/2009-August/007406.html With that patch, I've used the resampler extensively in many situations without any problems. John Ridges On 12/3/2010 1:00 PM,

Hi Everyone, Just wanted to let people know that we've uncovered some problems with the speex resamplers in PulseAudio The problem generally manifests itself when having the following setup. * Server Sample Rate: 44100 * Resampler: speex-* (both fixed and float) * Playing a 48000 stream The problem only really manifests itself in the first 500ms or so of the stream and then generally

'Twas brillig, and Sherief N. Farouk at 06/12/10 14:29 did gyre and gimble: > If you can produce a simple minimal repro that exhibits this issue on some > procedural signal (sine wave, etc) I'd love to look into it some more - I'm > maintaining a hardened version of the Speex Resampler and would be very > concerned if this bug made it into production. Well at present,

As part of our deployment of FC updates we have upgraded our office server from 3.0.24-3 to 3.0.24.4. We got some strange results. Shares that have the same name as the users home directory and/or the same name as their users id became inaccessible. For example, my user id is kens, my home directory is in /home/kens and there was a share of it called kens. There is also a common share

In response to --> Date: Thu, 28 Sep 2006 20:42:28 +0100 From: Colin Guthrie <gmane@colin.guthr.ie> Subject: [compiz] Re: beryl fork To: compiz@lists.freedesktop.org Message-ID: <efh8fc$7u2$1@sea.gmane.org> Content-Type: text/plain; charset=ISO-8859-1 ---------- I want to comment on the fork too. I apologize if this isn't the right venue, but it's my response to

Hello all, Got a problem with samba (from what I can tell) and is similar to some KB items here: With version 3.0.4-6.3E of Samba, why do completed print jobs stay in the print queue when printing to a Samba-shared printer from other Samba or Windows clients? And I have Samba version 3.0.24 installed. Why do completed print jobs stay in the print queue when printing to a Samba-shared printer

I threw together a very rough draft of a script: (See my compiz-script git repo: http://gitweb.beryl-project.org/?p=users/kristian/compiz-scripts;a=summary ) It's not too pretty, and only really adjusted for nVidia, so it's pretty useless at this point. I've only ever actually used nVidia with direct rendering, so I'll need some input from people with other setups than mine. On

Hi, I have an issue with how I have setup one of my shares. I have a file system on one of my boxes that sync's to a cygwin repository on the net. I eventually will have my internal windows workstations do a weekly (or some frequency) sync to my internal cygwin repository. When at a workstation I often do this cygwin sync by hand to make sure the user has the latest cygwin files. When I run

Hey list, Having a strange issue on a new File server. This system is running the 64-bit version of Fedora 5 running kernel 2.6.20-1.2300.fc5 and version 3.0.24-1.fc5 of Samba. This system is functioning as a backup to a primary system that is configured the same way. Same OS, hardware, etc. After moving data over and setting up the users and groups, I moved over the smb.conf file as well. In

We're having a problem with a combination of NFS and Samba that I'm hoping someone here has seen before and knows the solution for. In this case, the Samba server is an NFS client, and the Samba share is actually an NFS mount to an NFS server. The problem we see is when a Windows client tries to open a file on the Samba share, the application hangs, and eventually comes back saying

We are attempting to setup an automated system to build some Linux systems. We have utilised the PXELINUX bootloader after encountering the PXE 512Kb limit with bootp. We now have another issue which you may have already run into. In the DHCP configuration we specify pxelinux.0 as the bootfile, this works reasonable well, we call the Redhat vmlinuz and initrd.img files within the

Hi folks, I am trying to access the shared folders on a Windows XP PC from a Linux (FC5) PC using smbclient. Linux config info: $ locale LANG=en_US.UTF-8 $ rpm -q samba samba-3.0.24-6.fc5 smb.conf: [global] dos charset = CP936 <--- Simplified Chinese unix charset = UTF-8 display charset = LOCALE Now, here is the problem:

I just want to warn people that want to use the new hashing algorithm for mangled names. And that note should also be put in the man page IMO. You must understand that changing the hashing algorithm on a production server may have unwanted side effects (this is why we maintain by default hash and not hash2 and why it was not back ported to 2.2 initially). Windows clients may save all around

Hi all, I'm looking for documentation about the internals of the bridging software. We're putting together a new chip that incorporates, among other things, a core for a managed switch and a processor that will be running Linux. I wanted to have the Linux code (among other things) field SNMP requests and configure the managed switch. I'm hoping that it's as simple as

I want all the file-names to be stored on a samba share from my XP clients to be automatically converted to 8.3 syntax, so that i do not have any further problem while transporting those files over to other networks/servers like netware. As for now i am using these below mentioned lines to support file-name mangling over my samba. --------- #I do not want my filenames to be case sensitive,