Displaying 20 results from an estimated 200 matches similar to: "[Samba] [Announce] Samba 4.7.8 Available for Download"
2018 Sep 04
3
authentication performance with 4.7.6 -> 4.7.8 upgrade (was: Re: gencache.tdb size and cache flush)
On Wed, 2018-08-29 at 15:36 +0200, Peter Eriksson via samba wrote:
> For what it’s worth you are not alone in seeing similar problems with Samba and gencache.
>
> Our site has some 110K users (university with staff & students (including former ones), and currently around 2000 active (SMB) clients connecting to 5 different Samba servers (around 400-500 clients per server). When we
2005 Jun 21
0
smbd crash
A few times in the last couple months we have had our production Samba
3.0.14a-1server crash. We did not have detailed logging turned on at
the time so the attached output of our log is the best process tracking
I can give at the time of the crash.
What will happen is our shares will no longer be accessible, and all the
smbd processes will be hung. We can ssh to the server and do a restart
2019 Nov 20
0
Learning ham/spam with IMAPSieve: sa-learn-ham.sh terminated abnormally, signal 11
Hi,
> You can attach GDB to imap with follow-fork-mode set to 'child', so you
> can maybe see what causes the segfault.
now I am confused. Hopefully, I used GDB correctly, but as far as I can
see, everything seemed to work.
The only difference I can see is that I executed the whole thing as
root, but I would hope doveadm uses the correct user (vmail). At least
on the file
2019 Nov 20
2
Learning ham/spam with IMAPSieve: sa-learn-ham.sh terminated abnormally, signal 11
Op 20-11-2019 om 8:50 schreef Jens Rey via dovecot:
> Hi,
>
>> You can attach GDB to imap with follow-fork-mode set to 'child', so
>> you can maybe see what causes the segfault.
>
> now I am confused. Hopefully, I used GDB correctly, but as far as I
> can see, everything seemed to work.
>
> The only difference I can see is that I executed the whole thing
2018 Sep 04
0
authentication performance with 4.7.6 -> 4.7.8 upgrade (was: Re: gencache.tdb size and cache flush)
I’m going to try to upgrade from 4.7.6 to 4.7.7 on one of our servers soon and see if things break or not. With 4.7.6 things are stable at least.
Our file servers are in a Microsoft Windows domain (consisting of 6 Microsoft Windows 2016 AD servers).
The graphs (logarithmic time scale) below are login times from a probe station that times a connect using “smbclient” with a Kerberos ticket and
2018 Jun 22
0
Samba 4.7.8 Available for Debian Stretch (amd64/i386)
Hai.
I've finished the 4.7.8 package for Debian Stretch.
You can find them in the repo stretch-unstable.
(Note, these are not unstable, but a bad choice of words was made here.)
This version is alligned with the debian samba patches up to 4.8.2, but adapted in this 4.7.8.
The Build logs can be found here:
http://downloads.van-belle.nl/samba4/Buildlogs/stretch/
So, i've made a few
2018 Sep 04
1
authentication performance with 4.7.6 -> 4.7.8 upgrade (was: Re: gencache.tdb size and cache flush)
On Tue, 4 Sep 2018 15:13:10 +0200
Peter Eriksson via samba <samba at lists.samba.org> wrote:
> I’m going to try to upgrade from 4.7.6 to 4.7.7 on one of our servers
> soon and see if things break or not. With 4.7.6 things are stable at
> least.
>
> Our file servers are in a Microsoft Windows domain (consisting of 6
> Microsoft Windows 2016 AD servers).
>
>
>
2018 Oct 01
1
migrating DC from 4.7.8 on SUSE to 4.7.6 on Ubuntu
Having some trouble with this migration, everything runs on the fresh install. Once I copy in the contents of the previous /var/lib/samba samba-ad-dc now fails to start. This is all the journal gives me:
samba[5917]: [2018/10/01 18:36:19.094420, 0] ../source4/smbd/server.c:448(binary_smbd_main)
samba[5917]: samba version 4.7.6-Ubuntu started.
samba[5917]: Copyright Andrew Tridgell and the
2003 Jun 05
2
Slow connection performance - ssh2
Using ssh2 via agent to connect through proxy to sshd host. Each
connection (client to proxy, proxy to host) takes an average of 22
seconds, totaling approximately 44 seconds for a complete connection.
Debug logging with vmstat directed to the same file indicates two points
where a majority of time is spent (have looked at the similar postings):
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP (*6
2018 Jun 26
0
[Announce] Samba 4.8.3 Available for Download
========================================================
"The dads across the soccer
field looked at me as a dad
just like them. And I was very
grateful."
Garth Brooks
========================================================
Release Announcements
---------------------
This is the latest stable release of the Samba 4.8 release series.
Changes since 4.8.2:
2018 Jun 26
0
[Samba] [Announce] Samba 4.8.3 Available for Download
========================================================
"The dads across the soccer
field looked at me as a dad
just like them. And I was very
grateful."
Garth Brooks
========================================================
Release Announcements
---------------------
This is the latest stable release of the Samba 4.8 release series.
Changes since 4.8.2:
2018 Mar 13
0
Samba 4.8.0 and Schema 69 support (including replication)
Hey folks,
Has anything changed with 4.8.0 with respect to replication with a Win2KR2 server?
In particular, can Samba 4.8 join a Windows 2012R2 domain (schema 69) as a DC? Will replication work properly?
Thank You!
----- Mail original -----
De: "Karolin Seeger via samba" <samba at lists.samba.org>
À: samba-announce at lists.samba.org, samba at lists.samba.org, samba-technical
2018 Apr 26
0
[Announce] Samba 4.8.1 Available for Download
Hai, i've looked it up.
/quote Rowland.
> > I'll go search for this a bit, and start with the build of 4.8.1
> > while doing that.
>
> I would hang on with that, Denis has just asked if the 'don't upgrade
> to 4.8.0 bug' has been fixed, it isn't mentioned in the release notes.
> It seems to have gone in, just not mentioned in the release notes
2018 Jul 04
3
user's home shares doesn't work with Samba 4.8.3
>
> We had something similar very recently and the only difference between
> 4.8.2 & 4.8.3 that could be causing this was:
>
> https://bugzilla.samba.org/show_bug.cgi?id=13369
>
> The OP was asked to open a bug report, but I cannot see where a bug
> report was added and without the bug report, it will not get fixed.
> Perhaps you would care to open a bug report here:
2018 Mar 01
2
[Announce] Samba 4.8.0rc4 Available for Download
Release Announcements
=====================
This is the fourth release candidate of Samba 4.8. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.8 will be the next version of the Samba suite.
UPGRADING
=========
New GUID Index mode in sam.ldb for
2018 Mar 01
2
[Announce] Samba 4.8.0rc4 Available for Download
Release Announcements
=====================
This is the fourth release candidate of Samba 4.8. This is *not*
intended for production environments and is designed for testing
purposes only. Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.8 will be the next version of the Samba suite.
UPGRADING
=========
New GUID Index mode in sam.ldb for
2018 Apr 26
3
[Announce] Samba 4.8.1 Available for Download
========================================================
"The past, like the future, is
indefinite and exists only as
a spectrum of possibilities."
Stephen Hawking
========================================================
Release Announcements
---------------------
This is the latest stable release of the Samba 4.8 release series.
Changes since 4.8.0:
2018 Apr 26
3
[Announce] Samba 4.8.1 Available for Download
========================================================
"The past, like the future, is
indefinite and exists only as
a spectrum of possibilities."
Stephen Hawking
========================================================
Release Announcements
---------------------
This is the latest stable release of the Samba 4.8 release series.
Changes since 4.8.0:
2003 Aug 19
1
Problem with * server and FWD
I have a small HUGE problem with *.
I have installed * but I have 2 problems.
1 - Making call to FWD.
2 - Receiving call from FWD
More info of the problem at the end.
Here is the sip.conf file.
;
; SIP Configuration for Asterisk
;
[general]
port = 5060 ; Port to bind to
bindaddr = 0.0.0.0 ; Address to bind to
context = sip ;default Default for incoming calls
register =>
2017 Oct 17
0
Updates for today VIrt SIG meeting
Hi,
I won't be able to attend today Virt SIG meeting.
On KVM side, there should be a RHEL update in the coming days, an update to
qemu-kvm-ev will follow (https://bugzilla.redhat.com/show_bug.cgi?id=1501910
).
On oVirt side, upstream is finalizing 4.1.7 release and 4.2.0 beta; Virt
SIG repos will be update after the releases.
The oVirt 4.2 testing repos are now live on