similar to: Sangoma wapipe installation error

Hello Samba experts, I have just successfully replaced the old default Thecus Samba version 3.5.16 on my Thecus NAS (32-bit Intel Atom, 3 GB RAM, i686 Thecus kernel 2.6.33) by a current Samba 4.6.5 build that I have cross-compiled myself from scratch. Note that so far, I am using the unchanged (i.e. exactly identical) old 3.5.16 smb.conf file for 4.6.5. Everything seems to work fine in

My Sangoma Experience in Asterisk: Followup 2005-05-06 original review can be found at: http://astguiclient.sourceforge.net/Sangoma_experience.txt It's now been a month since I finished my last round of tests with the Sangoma A104u board in Asterisk. I have had a lot of conversations with the guys at Sangoma about how my system runs so that they could set up their test systems to try to

Hello Jeremy, thanks a million for your help and interest in tracking this down! :-) Am 13.06.2017 um 18:36 schrieb Jeremy Allison: > Can you get comparitive wireshark traces for the two cases ? > > That would help discover what the bottleneck is. I am not at all a network guy, but I hope that - maybe with a little more help from your part once I have tried to do so in practice - I

Hello, I've got problems with Samba 3.6.0 up to 3.6.6. Forked smbd processes are closing unexpectedly and sometimes smbd server exits. (In Samba 3.5.16 everything works). When invoke smbd from gdb and turn off SIGPIPE passing (by command "handle SIGPIPE nostop nopass") everything works fine. I found out that SigBlk flag of forked smbd processes in /proc/*/status is:

Hello again, Jeremy and other Samba experts, I'm sorry to be such a pain in your neck(s), but I still need your help in looking for help trying to find out why SMB2/3.1.1 in Samba 4.6.5 performs so much worse than SMB/1.5 in Samba 3.6.15 in scenarios with a huge number of small files. As requested by Jeremy, I have done wireshark "pcapng" captures of the four scenarios as

On Thu, 2017-06-08 at 11:28 +0200, awl1 via samba wrote: > Hello Andrew, > > and many thanks for your fast reply! :-) > > Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > > I think the key to avoiding the issue is that you have listed rpc > > modules which are not modules. The only rpc server module is > > rpc_mdssvc_module. > > Ah, OK, I see - so I

=================================================================== "Information's pretty thin stuff unless mixed with experience." Clarence Day ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.16 include: o Fix possible

=================================================================== "Information's pretty thin stuff unless mixed with experience." Clarence Day ================================================================== Release Announcements ===================== This is the latest stable release of Samba 3.5. Major enhancements in Samba 3.5.16 include: o Fix possible

Alan Coopersmith (11): test: skip compressed file tests when --disable-open-zfile is used gitlab CI: build with each of --enable-open-zfile & --disable-open-zfile configure: correct error message to suggest --disable-open-zfile open-zfile: Make compress & uncompress commands optional Require LT_INIT from libtool 2 instead of deprecated AC_PROG_LIBTOOL

On Tue, Jun 13, 2017 at 12:09:41PM +0200, awl1 via samba wrote: > Hello Samba experts, > > I have just successfully replaced the old default Thecus Samba > version 3.5.16 on my Thecus NAS (32-bit Intel Atom, 3 GB RAM, i686 > Thecus kernel 2.6.33) by a current Samba 4.6.5 build that I have > cross-compiled myself from scratch. > > Note that so far, I am using the unchanged

On Thu, 2017-06-08 at 10:09 +0200, awl1 via samba wrote: > Hello again, Samba experts, > > sorry for being such a pain in your necks, but I really need to get a > recent Samba version to compile, and it looks like I definitely need > your help with this. > > In the meantime, I have found that the huge number of "conflicting > types" errors for rpc_*_init(...)

Hello again, Jeremy, first of all, I am terribly sorry for my late reply. I tried to send my posting many times, but my mail has always been silently discarded by the Samba mail servers due to my main mail provider (GMX - a very large German mail provider with millions of customers) having been blacklisted by SORBS. For the time being, SORBS is still unwilling to delist them for unknown

Hello Andrew, and many thanks for your fast reply! :-) Am 08.06.2017 um 11:05 schrieb Andrew Bartlett: > I think the key to avoiding the issue is that you have listed rpc > modules which are not modules. The only rpc server module is > rpc_mdssvc_module. Ah, OK, I see - so I seem to have been wrong when assuming that I could take the output of Samba 3.5.16 "smbd -b" command

Hello Andrew, hello Samba experts, first of all, good news: So I have indeed managed to compile a set co cross-compiled binaries and installed them successfully onto my NAS. Many thanks for your help in getting there! I have now only used --bundled-libraries=ALL \ and left "--with-static-modules" unset (default). From cursorily testing so far, indeed everything

Hello, We recently upgraded to Asterisk 1.8/DAHDI 2.4/WANPipe 3.5.16. This system is connected to a PRI where the provider requires long distance codes. Normally, you dial, see progress and hear a tone (call is still "unanswered" at this point), enter your code, and it starts ringing as a normal call. Since upgrading, we aren't getting the tone anymore and aren't able to enter

===================================================================== "Sing like no one's listening, love like you've never been hurt, dance like nobody's watching, and live like it's heaven on earth." Mark Twain ===================================================================== Release Announcements ===================== This is the latest

===================================================================== "Sing like no one's listening, love like you've never been hurt, dance like nobody's watching, and live like it's heaven on earth." Mark Twain ===================================================================== Release Announcements ===================== This is the latest

Hi there We're having problems with users attaching to our (winbind) Samba servers and being assigned the same UID. Rarely happens - not repeatable - but definitely a pattern Anyway, I've been googling about and I think I've figured out the root cause, so I thought I'd check with the community first, because if I go off an change to my new model, it could take months before I

Hello Samba experts, due to the "SambaCry" issue (CVE-2017-7494), I am trying to update the Samba server installation on my Thecus NAS (dating back to 2011) from version 3.5.16 to the current 4.6.4. So far, I have successfully * created a cross-compiling toolchain for the NAS (i686-nptl-linux-gnu) based on gcc-5.2 * compiled Python and Samba library dependencies for my

Andreas, A few thoughts regarding your system 1) If it's a home system and you're specifically concerned about mitigating CVE 2017-7494, (a) verify that your share isn't mounted 'noexec' - if it's mounted this way then you're safe (b) if not (a), then add the [global] parameter "nt pipe support = no". This will break functionality that relies on support for