Re: FreeBSD Port: samba46-4.6.8

[Timur I. Bakeyev]

Thanks Carmel for understanding!

The truth is that 4.6.9 is broken for the ZFS, at the top of all other
brokenness and I just don't want to increase the entropy.

See the https://bugzilla.samba.org/show_bug.cgi?id=6133 for more details.

With regards,
Timur.

P.S> I wonder, why Dutch always write my name like Timor :)? Not even
Timoer, which would be more correlated :)


On Sat, Oct 28, 2017 at 10:47 AM, Carmel NY  wrote:

> On Sat, 28 Oct 2017 01:58:33 +0200, Dutchman01 stated:
>
> >Hello timor,
> >
> >
> >
> >Would you please have a look and upgrade this port to 4.6.9 release
> please,
> >
> >it really has some nice bug fixes/patches.
>
> I believe it was only released Oct 25. I think we should allow the port
> maintainer a few days to work on it before pestering him.
>
> https://www.samba.org/samba/history/samba-4.6.9.html
>
> --
> Carmel
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba44-4.4.8

[Timur I. Bakeyev]

On Thu, Dec 29, 2016 at 9:32 PM, Adam Weinberger  wrote:

> > On 29 Dec, 2016, at 13:24, Timur I. Bakeyev  wrote:
> >
> >> On Thu, Dec 29, 2016 at 8:52 PM, Adam Weinberger 
> wrote:
> >> > On 28 Dec, 2016, at 7:51, Timur I. Bakeyev  wrote:
> >> >
> >> > Hi, CVB!
> >> >
> >> > At the moment I can't connect to svn.freebsd.org on whatever
> reason... BTW,
> >> > anyone knows, what has changed in recent 12 hours?
> >> >
> >> > You can apply the following patch manually:
> >> >
> >> > With best regards,
> >> > BaT
> >>
> >> Timur,
> >>
> >> No packages for samba are being built because configure with the
> default option set fails. Samba can't depend on openldap-sasl if its
> databases/ldb dependency depends on openldap (without sasl).
> >>
> >> Either samba needs to depend on openldap without sasl, or ldb needs to
> depend on openldap-sasl.
> >>
> >> # Adam
> > Hi, Adam!
> >
> > I've seen the reports and think to upgrade ldb to work with ldap-sasl
> version instead. In general, handling of SASL in LDAP package isn't
> graceful, while libraries by themselves are interchangeable, pkg sees them
> as entirely different ones :(
>
> Agreed, it's really ugly. Does samba require SASL-enabled OpenLDAP? Keep
> in mind that if ldb and samba* require openldap-sasl, then every port that
> depends on either of them might require adding WANT_OPENLDAP_SASL too.
>

Luckily, there aren't many ports that directly depend on samba* or ldb*. I
believe most of the time samba is run dependency rather that build
dependency.

Regards,
Timur.

P.S> I really wonder, what was the problem with svn.freebsd.org(213.138.116.72)
yesterday, so I couldn't connect for half a day.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba44-4.4.8

[Timur I. Bakeyev]

Hi, Adam!

I've seen the reports and think to upgrade ldb to work with ldap-sasl
version instead. In general, handling of SASL in LDAP package isn't
graceful, while libraries by themselves are interchangeable, pkg sees them
as entirely different ones :(

Sorry for the mess this update created.

With best regards,
Timur.

On Thu, Dec 29, 2016 at 8:52 PM, Adam Weinberger  wrote:

> > On 28 Dec, 2016, at 7:51, Timur I. Bakeyev  wrote:
> >
> > Hi, CVB!
> >
> > At the moment I can't connect to svn.freebsd.org on whatever reason...
> BTW,
> > anyone knows, what has changed in recent 12 hours?
> >
> > You can apply the following patch manually:
> >
> > With best regards,
> > BaT
>
> Timur,
>
> No packages for samba are being built because configure with the default
> option set fails. Samba can't depend on openldap-sasl if its databases/ldb
> dependency depends on openldap (without sasl).
>
> Either samba needs to depend on openldap without sasl, or ldb needs to
> depend on openldap-sasl.
>
> # Adam
>
>
> --
> Adam Weinberger
> ad...@adamw.org
> https://www.adamw.org
>
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba44-4.4.8

[Timur I. Bakeyev]

Hi, CVB!

At the moment I can't connect to svn.freebsd.org on whatever reason... BTW,
anyone knows, what has changed in recent 12 hours?

You can apply the following patch manually:

Index: Makefile
===
--- Makefile(revision 429692)
+++ Makefile(working copy)
@@ -3,7 +3,7 @@

 PORTNAME?= ${SAMBA4_BASENAME}44
 PORTVERSION?=  ${SAMBA4_VERSION}
-PORTREVISION?= 0
+PORTREVISION?= 1
 CATEGORIES?=   net
 MASTER_SITES=  SAMBA/samba/stable SAMBA/samba/rc
 DISTNAME=  ${SAMBA4_DISTNAME}
@@ -197,7 +197,7 @@
 .else
 GDB_CMD=   true
 CONFIGURE_ARGS+=   --without-ntvfs-fileserver
-PLIST_SUB+=DEVELOPER="@comment " NTVFS="@comment"
+PLIST_SUB+=DEVELOPER="@comment " NTVFS="@comment "
 .endif
 ##
 # XXX: That will blow up your installation


With best regards,
BaT


On Wed, Dec 28, 2016 at 11:56 AM, Konstantin V Bekreyev <201...@bekreyev.ru>
wrote:

>
> Hello,
>
> samba44 cannot be installed from ports at FreeBSD 11:
>
> ==
> [root@server /usr/ports/net/samba44]# make reinstall
> ===>  Installing for samba44-4.4.8
> ===>   samba44-4.4.8 depends on package: libarchive>=3.1.2 - found
> ===>   samba44-4.4.8 depends on package: py27-dnspython>=1.9.4 - found
> ===>   samba44-4.4.8 depends on package: py27-iso8601>=0.1.11 - found
> ===>   samba44-4.4.8 depends on package: talloc>=2.1.6 - found
> ===>   samba44-4.4.8 depends on package: tevent>=0.9.28 - found
> ===>   samba44-4.4.8 depends on package: tdb>=1.3.8 - found
> ===>   samba44-4.4.8 depends on package: ldb>=1.1.26 - found
> ===>   samba44-4.4.8 depends on file: /usr/local/bin/python2.7 - found
> ===>   samba44-4.4.8 depends on executable: python2 - found
> ===>   samba44-4.4.8 depends on shared library: libpopt.so - found
> (/usr/local/lib/libpopt.so)
> ===>   samba44-4.4.8 depends on shared library: libinotify.so - found
> (/usr/local/lib/libinotify.so)
> ===>   samba44-4.4.8 depends on shared library: libgnutls.so - found
> (/usr/local/lib/libgnutls.so)
> ===>   samba44-4.4.8 depends on shared library: libsunacl.so - found
> (/usr/local/lib/libsunacl.so)
> ===>   samba44-4.4.8 depends on shared library: libsunacl.so - found
> (/usr/local/lib/libsunacl.so)
> ===>   samba44-4.4.8 depends on shared library: libreadline.so.6 - found
> (/usr/local/lib/libreadline.so.6)
> ===>   samba44-4.4.8 depends on shared library: libfam.so.0 - found
> (/usr/local/lib/libfam.so.0)
> ===>   Registering installation for samba44-4.4.8
> pkg-static: cannot parse keyword: cannot open file /usr/ports/Keywords/
> commentlib/samba4/private/libntvfs-samba4.so.ucl: No such file or
> directory
> pkg-static: unknown keyword commentlib/samba4/private/libntvfs-samba4.so:
> @commentlib/samba4/private/libntvfs-samba4.so
> pkg-static: cannot parse keyword: cannot open file /usr/ports/Keywords/
> commentlib/shared-modules/service/smb.so.ucl: No such file or directory
> pkg-static: unknown keyword commentlib/shared-modules/service/smb.so:
> @commentlib/shared-modules/service/smb.so
> *** Error code 74
>
> Stop.
> make[2]: stopped in /usr/ports/net/samba44
> *** Error code 1
>
> Stop.
> make[1]: stopped in /usr/ports/net/samba44
> *** Error code 1
>
> Stop.
> make: stopped in /usr/ports/net/samba44
> ==
>
> [root@server /usr/ports/net/samba44]# freebsd-version -uk
> 11.0-RELEASE-p2
> 11.0-RELEASE-p6
>
> ==
> [root@server /usr/ports/net/samba44]# cat /var/db/ports/net_samba44/
> options
> # This file is auto-generated by 'make config'.
> # Options for samba44-4.4.5_1
> _OPTIONS_READ=samba44-4.4.5_1
> _FILE_COMPLETE_OPTIONS_LIST=ACL_SUPPORT ADS AD_DC CUPS DEBUG DEVELOPER
> DNSUPDATE DOCS EXP_MODULES FAM LDAP MANPAGES PTHREADPOOL QUOTAS SYSLOG UTMP
> NSUPDATE BIND99 BIND910 AVAHI MDNSRESPONDER
> OPTIONS_FILE_SET+=ACL_SUPPORT
> OPTIONS_FILE_UNSET+=ADS
> OPTIONS_FILE_UNSET+=AD_DC
> OPTIONS_FILE_UNSET+=CUPS
> OPTIONS_FILE_UNSET+=DEBUG
> OPTIONS_FILE_UNSET+=DEVELOPER
> OPTIONS_FILE_UNSET+=DNSUPDATE
> OPTIONS_FILE_SET+=DOCS
> OPTIONS_FILE_UNSET+=EXP_MODULES
> OPTIONS_FILE_SET+=FAM
> OPTIONS_FILE_UNSET+=LDAP
> OPTIONS_FILE_UNSET+=MANPAGES
> OPTIONS_FILE_SET+=PTHREADPOOL
> OPTIONS_FILE_SET+=QUOTAS
> OPTIONS_FILE_SET+=SYSLOG
> OPTIONS_FILE_SET+=UTMP
> OPTIONS_FILE_UNSET+=NSUPDATE
> OPTIONS_FILE_UNSET+=BIND99
> OPTIONS_FILE_UNSET+=BIND910
> OPTIONS_FILE_UNSET+=AVAHI
> OPTIONS_FILE_UNSET+=MDNSRESPONDER
> ==
>
> can you help with this problem?
>
> --
> With best regards,
> Konstantin V Bekreyev
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinf

Re: Samba 4.2.3 exited on signal 4

[Timur I. Bakeyev]

It possibly crashes, cause you didn't downgrade tdb/ldb libs. There is a
patch for them in Samba's bugzilla, need to be pushed to the ports.

On Wed, Aug 26, 2015 at 6:02 PM, Loïc BLOT 
wrote:

> I notice exactly the same bug on my installation. I tried different
> option compilation and rollback to 4.2.2 and the same bug occurs, samba
> crashes.
> Samba doesn't crash if it wasn't a domain controller.
> --
> Best regards,
> Loïc BLOT,
> UNIX systems, security and network engineer
> http://www.unix-experience.fr
>
>
>
> Le mardi 18 août 2015 à 22:11 +0200, Timur I. Bakeyev a écrit :
> > Hi, Stefan!
> >
> > Was it a recent case? I belive this problem with md5.so was addressed
> > while
> > ago in the upstream.
> >
> > With regards,
> > Timur Bakeyev.
> >
> > On Tue, Aug 18, 2015 at 5:58 PM, Stefan Esser  wrote:
> >
> > > Am 18.08.2015 um 14:07 schrieb Timur I. Bakeyev:
> > > > Could be that you are affected by
> > > > https://bugzilla.samba.org/show_bug.cgi?id=11455
> > > >
> > > > Can you, please, verify, that it is the case?
> > >
> > > A good test is to install the pre-compiled package and compare
> > > ldd output for the port compiled by you and the package binaries
> > > (i.e. strip off the addresses and compare only the filenames that
> > > ldd reports for either smbd binary).
> > >
> > > In my case the smbd and smbclient where linked against a wrong
> > > MD5 library (/usr/local/lib/libmd5.so from www/libwww) instead
> > > of the system library (/usr/lib/libmd.so). This was due to the
> > > configure script preferring libmd5.so over libmd.so ...
> > >
> > > Regards, STefan
> > > ___
> > > freebsd-ports@freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > > To unsubscribe, send any mail to "
> > > freebsd-ports-unsubscr...@freebsd.org"
> > >
> > ___
> > freebsd-ports@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> > To unsubscribe, send any mail to "
> > freebsd-ports-unsubscr...@freebsd.org"
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Samba 4.2 crashes

[Timur I. Bakeyev]

You possibly hit the bug in the libtdb/libldb/etc libraries code, which was
brough by the latest update of those libs. Please, wait until maintainer
commit the fix.

The problem was introduced by upstream.

Regards,
Timur.

On Tue, Aug 25, 2015 at 7:53 PM, Stefan Esser  wrote:

> Am 25.08.2015 um 18:02 schrieb Andrea Venturoli:
> > Hello.
> >
> > I'm trying to upgrade from samba 3.6 to 4.2 (mainly because the former
> > is deprecated, so I don't want AD, just plain old functionality).
> >
> > I started with simpler installations and had almost no problem.
> > However, in a just a little bit more complex case (PDC+BDC with LDAP
> > backend), smbd and/or winbindd keep crashing.
> >
> > I started by upgrading the PDC; everything should be fine (config files,
> > rc.conf, database directory, connection to LDAP, etc...).
> > However I'm getting lots of the following messages:
> >
> >> kernel: pid 50545 (smbd), uid 0: exited on signal 6
> >
> >> winbindd[89801]: stack overflow detected; terminated
> >
> >> winbindd[89801]: stack overflow detected; terminated
>
> I have seen that kind of failure when the port was built on a system
> that had www/libwww installed. In that case libmd5.so from libwww is
> linked to samba in preference of the system's libmd.so.
>
> I sent a note to the port's maintainer, a few weeks ago, but apparently
> he did not apply the patch I included, which fixes the port.
>
> In case you have libwww installed, you can simply temporarily deinstall
> it while you build samba42.
>
> Or apply the attached patch (copy it to the samba42 port's files
> directory and rebuild the port).
>
> Best regards, STefan
>
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Samba 4.2.3 exited on signal 4

[Timur I. Bakeyev]

Hi, Stefan!

Was it a recent case? I belive this problem with md5.so was addressed while
ago in the upstream.

With regards,
Timur Bakeyev.

On Tue, Aug 18, 2015 at 5:58 PM, Stefan Esser  wrote:

> Am 18.08.2015 um 14:07 schrieb Timur I. Bakeyev:
> > Could be that you are affected by
> > https://bugzilla.samba.org/show_bug.cgi?id=11455
> >
> > Can you, please, verify, that it is the case?
>
> A good test is to install the pre-compiled package and compare
> ldd output for the port compiled by you and the package binaries
> (i.e. strip off the addresses and compare only the filenames that
> ldd reports for either smbd binary).
>
> In my case the smbd and smbclient where linked against a wrong
> MD5 library (/usr/local/lib/libmd5.so from www/libwww) instead
> of the system library (/usr/lib/libmd.so). This was due to the
> configure script preferring libmd5.so over libmd.so ...
>
> Regards, STefan
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Samba 4.2.3 exited on signal 4

[Timur I. Bakeyev]

Could be that you are affected by
https://bugzilla.samba.org/show_bug.cgi?id=11455

Can you, please, verify, that it is the case?

With best regards,
Timur


On Tue, Aug 18, 2015 at 1:43 PM, Enrique Ayesta Perojo <
eaye...@portugalete.uned.es> wrote:

> Hello,
>
> I have updated a Samba 4.1 installation to latest Samba 4.2.3 from ports
> and it doesn't start anymore, it seems to start but after a while (it
> seems that it's reading or trying to read from disk) it suddenly stops
> with signal 4 (Illegal instruction).
>
> Has anybody have the same problem or have any idea what could be the
> reason?
>
> Thanks
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Swat2

[Timur I. Bakeyev]

Swat isn't a part of Samba4 anymore. Looking at the dates in the GIT
repository I'd say it's been given up(for good).

Regards,
Timur.

On Tue, Jul 14, 2015 at 8:34 PM, Carmel NY  wrote:

> I understand that there is a "swat2" available for Samba4*. I have not seen
> it in the ports system thought. Is it available for FreeBSD?
>
> https://wiki.samba.org/index.php/SWAT2
>
> --
> Carmel
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba4* build dependencies

[Timur I. Bakeyev]

Speaking of the garbage in a system - why to add Samba in the first place
:)?

On Wed, Jun 10, 2015 at 10:19 PM, Horatiu MOLDOVAN  wrote:

> Hi,
> Trying to replace samba 3.6 i've observed some disturbing things on samba
> 4.x build:
> - security/cyrus-sasl2, security/libgcrypt and security/gnutls are
> mandatory lib dependencies - is there a reason to add garbage to the system?
> - OpenLDAP is built unconditionally regardless of the LDAP option setting
> - again, is there a reason to add more garbage to the system?
> not sure why dns/py-dnspython is a build dependency...
>
> (Test build options: ACL AIO FAM PTHREADPOOL QUOTAS UTMP)
>
> Can someone clarify these?
> Thank you,
> ---
> H.
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba41 4.1.18 fails to build with MAKE_JOBS

[Timur I. Bakeyev]

I didn't experience anything like this on my test build but I can point to
the few places, that make 4.1.18 port different from 4.1.17.

I've, possibly wrongly, added 'fakeroot' facility to the USES line. For me
it worked fine, but I've tested in the live environment and it may behave
strangly in poudre. In general, the need for 'fakeroot' is questionable, so
if you can remove it and verify port build in poudre it would be nice.

Next suspect would be python, as WAF is depend on it if there been any
changes to it, especially in multithreaded part that could affect build as
well.

Also, MAKE_ARGS/_MAKE_JOBS possibly different from the previous version due
recent addition WAF as a supported build system, but I don't think that
should have any impact.

I'd say that 'fakeroot' is the most suspicios addition to the port build
proccess. I didn't add it tho the samba4 port and, seems you don't have
problems with it?

With best regards,
Timur Bakeyev.

On Wed, Jun 3, 2015 at 5:54 PM, Ben Woods  wrote:

> Since net/samba41 was updated to 4.1.18, it has been failing to build
> in poudriere with MAKE_JOBS (when /usr/local/etc/poudriere.conf has
> ALLOW_MAKE_JOBS_PACKAGES=samba*).
>
> The issue is a stage-runaway (>> Killing runaway build after 7200
> seconds with no output).
>
> The failing poudriere logs for version 4.1.18 with MAKE_JOBS can be found
> here:
>
> http://woodsb02.no-ip.org/poudriere/data/101amd64-default/2015-06-02_01h00m00s/logs/errors/samba41-4.1.18.log
>
>
> However, if I do not allow MAKE_JOBS, then 4.1.18 builds fine:
>
> http://woodsb02.no-ip.org/poudriere/data/11amd64-default/2015-06-03_22h00m32s/logs/samba41-4.1.18.log
>
>
> Version 4.1.17 used to build fine with MAKE_JOBS:
>
> http://woodsb02.no-ip.org/poudriere/data/101amd64-default/2015-05-20_01h00m00s/logs/samba41-4.1.17.log
>
>
> Any ideas? If it makes any difference, poudriere will be using 8
> parallel jobs when MAKE_JOBS is allowed.
>
> Regards,
> Ben
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg install kodi does not like samba

[Timur I. Bakeyev]

Well, it's all said in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=177786. I've added
samba36-nmblookup as a courtesy for the xmbc/kodi project while ago so it's
not depend on full samba package, but now it's going too far in the request
to drop nmblookup from samba36 itself..

The real solution(are we done with GSOC projects for this year already?)
would be ability to build multiple packages out of one port, since we
already have stagedir. So, only one extra step is required, similar the way
it's done in Debian.

On Tue, May 26, 2015 at 7:38 PM, Andriy Gapon  wrote:

>
> Not sure if this is a problem with multimedia/kodi port or if it is with
> pkg or
> both:
> $ pkg install kodi
> Updating FreeBSD repository catalogue...
> FreeBSD repository is up-to-date.
> Updating poudriere repository catalogue...
> poudriere repository is up-to-date.
> All repositories are up-to-date.
> Checking integrity... done (1 conflicting)
> Checking integrity... done (0 conflicting)
> The following 13 package(s) will be affected (of 0 checked):
>
> Installed packages to be REMOVED:
> samba36-3.6.25
>
> New packages to be INSTALLED:
> kodi: 14.2 [FreeBSD]
> tinyxml: 2.6.2_1 [FreeBSD]
> samba36-nmblookup: 3.6.25 [FreeBSD]
> libnfs: 1.3.0_1 [FreeBSD]
> libcec: 2.2.0 [FreeBSD]
> libbluray: 0.7.0,1 [FreeBSD]
> libbdplus: 0.1.2 [FreeBSD]
> libaacs: 0.8.0 [FreeBSD]
> libass: 0.12.1 [FreeBSD]
> sdl2: 2.0.3_4 [FreeBSD]
> shairplay: 0.9.0.20140422 [FreeBSD]
> lzo2: 2.09 [FreeBSD]
>
> So, pkg wants to replace samba36 with samba36-nmblookup.
> I think that those packages conflict because samba36 provides a superset
> of what
> samba36-nmblookup provides.  So, there should be no reason to not just use
> samba36.
> Finally, why do we need net/samba-nmblookup at all?  Seems like kodi is
> its only
> user and it is not a light-weight port already.
>
> --
> Andriy Gapon
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Port net/samba36-3.6.24 has problems

[Timur I. Bakeyev]

Hi!

Looks like you have one of the Kerberos ports installed, while still having
base system Kerberos. That greatly confuses Samba configure :(

You may try to set KRB5_HOME=/usr/local for MIT or HEIMDAL_HOME=/usr/local
for Heimdal in /etc/make.conf, but I have no idea, would it really help.
Other option is to remove port version of Kerberos.

Or you can try to go through configure.log and find out where does it pick
the wrong headers and libs.

With regards,
Timur.



On Tue, Jun 24, 2014 at 2:33 PM, Schuendehuette, Matthias <
matthias.schuendehue...@siemens.com> wrote:

> Hello,
>
> I tried to upgrade from samba36-3.6.23 to samba36-3.6.24 using
> 'portupgrade net/samba36' and got the following problem:
>
> *
> libsmb/clikrb5.c: In function 'get_krb5_smb_session_key':
> libsmb/clikrb5.c:942: warning: 'krb5_auth_con_getremotesubkey' is
> deprecated (declared at /usr/local/include/krb5/krb5.h:5906)
> libsmb/clikrb5.c:945: warning: 'krb5_auth_con_getlocalsubkey' is
> deprecated (declared at /usr/local/include/krb5/krb5.h:5901)
> libsmb/clikrb5.c:1691:2: error: #error
> UNKNOWN_KRB5_ENCTYPE_TO_STRING_FUNCTION
> The following command failed:
> cc -O2 -pipe -fno-strict-aliasing -DLDAP_DEPRECATED -I.
> -I/usr/ports/net/samba36/work/samba-3.6.24/source3
> -I/usr/ports/net/samba36/work/samba-3.6.24/source3/../lib/iniparser/src
> -Iinclude -I./include  -I. -I. -I./../lib/replace -I./librpc -I./..
> -DHAVE_CONFIG_H  -Iinclude -I./include -I. -I. -I./../lib/replace
> -I./librpc -I./.. -I./../lib/popt -DLDAP_DEPRECATED
>  -I/usr/ports/net/samba36/work/samba-3.6.24/source3/lib -I..
> -D_SAMBA_BUILD_=3 -I/usr/local/include -D_SAMBA_BUILD_=3 -fPIC -DPIC -c
> libsmb/clikrb5.c -o libsmb/clikrb5.o
> gmake: *** [libsmb/clikrb5.o] Fehler 1
> gmake: *** Warte auf noch nicht beendete Prozesse...
> ===> Compilation failed unexpectedly.
> *
>
> This error occurs with Heimdal as well as with MIT Kerberos.
>
>
> Revision of the portstree is '359060'
>
> My system is: 'FreeBSD blnn719x.ww004.siemens.net 9.3-BETA3 FreeBSD
> 9.3-BETA3 #36 r267564: Tue Jun 17 13:14:47 CEST 2014'
>
> What should I do to avoid this?
>
>
>
> with best regards
>
> Matthias Schündehütte
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba41 port compiles nmbd as a shared object, not executable

[Timur I. Bakeyev]

On Fri, May 9, 2014 at 8:20 PM, Craig Rodrigues wrote:

>
> On 05/08/14 15:10, John Hixson wrote:
>
>>
>> So, fix what ?
>> We were seeing that smbd was not dumping core. It would claim to be
>> dumping
>> core but wasn't. It appears this is completely unrelated. The issue
>> turns out to be the kern.sugid_coredump sysctl. Once this is set, smbd
>> will core fine.
>>
>>
>
> OK, so after discussions with John, I understand what is going on.
> The net/samba41 port is fine, and nothing needs to be changed in it.
>
> We just need to verify in our application that kern.sugid_coredump=1 is
> set,
> in order to get debuggable coredumps from Samba.
>

Ok, nice to know this. As I understand, iXsystems now fully moved to Samba
4.1?

I those thinking, guys, that you may wanted to create at the top of FreeNAS
Samba4 appliance, similar to the one, provided by SerNet, only FreeBSD
based. So, it can act as a Windows AD replacement in certain environments.
In general, we have everything in ports to make the one.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: samba-4.1.6 FreeBSD 10 cannot read from share.

[Timur I. Bakeyev]

Hi, Johan!

On Wed, Mar 26, 2014 at 10:42 AM, Johan Hendriks wrote:

> Hello all.
>
> I am using samba 3.x.x for a long time to share files across the network
> as a domain member server.
> All is working like it should. Lately i tried the samba 41 port and
> package to do the same job.
> However I am not able to get it working.
>
> Everything seems to work, i can browse the share, i can write to the share
> and i can delete files from the share. But as soon as I want to read from
> the share windows explorer hangs. wbinfo -u works, id  works. I have
> rebuild samba41, i installed a new FreeBSD 10 machine and installed
> samba41, I also tried the package of samba but the issue remains. Also i
> tried to trim down the smb4.conf file.
>
> The error i get is this (translated from dutch)
> There is a problem accessing the file I:\data\filetocopy
> Make sure your computer is connected to the network and try again.
>
> In my logs i do not see a lot of strange things , i do see this
>
> Mar 25 15:47:50 freetest smbd[80071]: [2014/03/25 15:47:50.679688, 0,
> pid=80071, effective(0, 10004), real(0, 0)] ../source3/smbd/reply.c:3079(
> fake_sendfile)
> Mar 25 15:47:50 freetest smbd[80071]: [2014/03/25 15:47:50.680200, 0,
> pid=80071, effective(0, 10004), real(0, 0)] ../source3/smbd/smb2_read.c:
> 235(smb2_sendfile_send_data)
> Mar 25 15:47:50 freetest smbd[80071]:   smb2_sendfile_send_data:
> fake_sendfile failed for file ubcd526.iso (Socket is not connected).
> Terminating
>
>
> Could someone point me in the right direction, i have no idea how to
> overcome this.
> If i revert back to 3.6.xx all is fine.
>
>
Can't tell you much, but that 'fake_sendfile' looks weird, we do have real
one. Can you send be the config.log file?

Regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[Timur I. Bakeyev]

Hi, Oliver!

Did you get any progress on that? I asked you for the output of:

# rcorder /etc/rc.d/* /usr/local/etc/rc.d/*

Did you get one?


Regards,
Timur Bakeyev.



On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann wrote:

> On CURRENT, I receive this error message when trying to start net/samba36:
>
> ERROR: lock directory /var/run/samba/ does not exist
>
> System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014 amd64
>
> Filesystem /var/run is tmpfs and resides on a SSD!
>
> I'm confused. Years ago, I had a similar problem with samba3[46] when I
> intriduced myself
> to tmpfs-backed /var/run. The start-script of sambe residing in
> /usr/local/etc/rc.d/samba
> wasn't capable of checking the existence of /var/run/samba so startup
> failed. in the
> meanwhile, I thought this was fixed - the problem I report in is present
> somehow since
> January, but I can not be more specific.
>
> I deleted /usr/local/etc/rc.d/samba and reinstalled net/samba36. After
> reinstallation,
> samba can be started on a regular basis. But after a reboot, it couldn't.
>
> I have no clue what is happening here. Any suggestions?
>
> Oliver
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Accommodating the security/heimdal port on FreeBSD10

[Timur I. Bakeyev]

Kerberos5 support in the ports needs love and it's own .mk infrastructure.
Wish I have enough overview of what is needed by various ports in that
respect.

With regards,
Timur Bakeyev.


On Wed, Mar 19, 2014 at 2:57 AM, Dewayne Geraghty <
dewayne.gerag...@heuristicsystems.com.au> wrote:

> Some port maintainers on FreeBSD 10 are modifying various ports to
> accommodate gssapi use from heimdal base.  Typically the change is
> something like
> ...
> LDFLAGS+=   -lgssapi_krb5
> ..
> which works for heimdal in the base system, but prevents a package (or
> port build) because in security/heimdal the content of libgssapi_krb5 is
> contained within libgssapi; and so doesn't exist as a separate library.
>
> Would it be possible to wrap this dependency within a
> .if !defined(HEIMDAL_HOME)
> LDFLAGS+=   -lgssapi_krb5
> .endif
>
> Its fairly standard practice to test for HEIMDAL_HOME which invariably
> implies that the security/heimdal port is being used, and incidentally
> identifies where the libraries are located.
>
> Though a better solution, which also reflects the real dependency upon
> the security/heimdal port
> .if defined(HEIMDAL_HOME)
> BUILD_DEPENDS+=
> ${HEIMDAL_HOME}/lib/libgssapi.so:${PORTSDIR}/security/heimdal
> RUN_DEPENDS+=
>  ${HEIMDAL_HOME}/lib/libgssapi.so:${PORTSDIR}/security/heimdal
> .else
> LDFLAGS+=   -lgssapi_krb5
> .endif
>
> As this also adds the heimdal port dependency into +COMMENTS (& possible
> MANIFEST?), as well as build dependency.
>
> I'm not a port maintainer/committer, but for those that are, there are a
> few ports that might be useful as a reference regarding use of the
> heimdal port:
> security/cyrus-sasl2-gssapi
> net/samba3
> dns/bind99
>
> I don't have heimdal from base installed, which is why I noticed that
> mail/dovecot2 was the most recent port that needed some additional
> lines, so I figured it might help others rather than my patching just my
> ports tree.
>
> Regards, Dewayne.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[Timur I. Bakeyev]

Sorry, I made a typo:

 rcorder /etc/rc.d/* /usr/local/etc/rc.d/*

You can check yourself - see, where samba in that output relative to... Hm,
what would start your /var/run - /etc/rc.d/var I guess?


On Tue, Mar 18, 2014 at 6:33 PM, O. Hartmann wrote:

> On Tue, 18 Mar 2014 18:13:20 +0100
> "Timur I. Bakeyev"  wrote:
>
> > Hi, Oliver!
> >
> > Please check in the rc.d/samba function samba_start_precmd(). It should
> > contain valid /var/run/samba path.
>
> Checked - and it contains the propper path.
>
> >
> > Is this problem occurs  only on restart(reboot) of the server? If you
> start
> > samba manually after the boot - does it run?
>
> It doesn't start on reboot, it starts on manauel issuing the command
> "service samba
> start".
>
> >
> > It could be, that in FreeBSD 11 rc order has changed somehow and samba
> > starts before /var/run is mounted. What does:
> >
> > # rcorder /etc/rc.d/* /usr/local/etc.rc.d/*
>
> /etc/rc.d/sysctl
> /etc/rc.d/hostid
> /etc/rc.d/zvol
> /etc/rc.d/dumpon
> /etc/rc.d/ddb
> /etc/rc.d/initrandom
> /etc/rc.d/geli
> /etc/rc.d/gbde
> /etc/rc.d/ccd
> /etc/rc.d/swap
> /etc/rc.d/fsck
> /etc/rc.d/root
> /etc/rc.d/mdconfig
> /etc/rc.d/hostid_save
> /etc/rc.d/mountcritlocal
> /etc/rc.d/zfs
> /etc/rc.d/var
> /etc/rc.d/cleanvar
> /etc/rc.d/FILESYSTEMS
> /etc/rc.d/kldxref
> /etc/rc.d/kld
> /etc/rc.d/addswap
> /etc/rc.d/random
> /etc/rc.d/postrandom
> /etc/rc.d/adjkerntz
> /etc/rc.d/atm1
> /etc/rc.d/hostname
> /etc/rc.d/ip6addrctl
> /etc/rc.d/netoptions
> /etc/rc.d/sppp
> /etc/rc.d/ipfilter
> /etc/rc.d/ipnat
> /etc/rc.d/ipfs
> /etc/rc.d/serial
> /etc/rc.d/netif
> /etc/rc.d/devd
> /etc/rc.d/ipsec
> /etc/rc.d/atm2
> /etc/rc.d/pfsync
> /etc/rc.d/pflog
> /etc/rc.d/pf
> /etc/rc.d/stf
> /etc/rc.d/ppp
> /etc/rc.d/faith
> /etc/rc.d/routing
> /etc/rc.d/mroute6d
> /etc/rc.d/nsswitch
> /etc/rc.d/rtsold
> /etc/rc.d/resolv
> /etc/rc.d/local_unbound
> /etc/rc.d/static_ndp
> /etc/rc.d/static_arp
> /etc/rc.d/bridge
> /etc/rc.d/route6d
> /etc/rc.d/mrouted
> /etc/rc.d/routed
> /etc/rc.d/defaultroute
> /etc/rc.d/ipfw
> /etc/rc.d/NETWORKING
> /etc/rc.d/netwait
> /etc/rc.d/mountcritremote
> /etc/rc.d/newsyslog
> /etc/rc.d/syslogd
> /etc/rc.d/ntpdate
> /etc/rc.d/rpcbind
> /etc/rc.d/devfs
> /etc/rc.d/ipmon
> /etc/rc.d/mdconfig2
> /etc/rc.d/watchdogd
> /etc/rc.d/savecore
> /etc/rc.d/ldconfig
> /etc/rc.d/archdep
> /etc/rc.d/abi
> /etc/rc.d/SERVERS
> /etc/rc.d/nisdomain
> /etc/rc.d/ypserv
> /etc/rc.d/ypxfrd
> /etc/rc.d/ypupdated
> /etc/rc.d/ypbind
> /etc/rc.d/ypset
> /etc/rc.d/yppasswdd
> /etc/rc.d/wpa_supplicant
> /etc/rc.d/virecover
> /etc/rc.d/accounting
> /etc/rc.d/nfsclient
> /etc/rc.d/amd
> /etc/rc.d/atm3
> /etc/rc.d/auditd
> /etc/rc.d/auditdistd
> /etc/rc.d/casperd
> /etc/rc.d/tmp
> /etc/rc.d/cleartmp
> /etc/rc.d/ctld
> /etc/rc.d/dmesg
> /etc/rc.d/hastd
> /etc/rc.d/iscsid
> /etc/rc.d/iscsictl
> /etc/rc.d/kerberos
> /etc/rc.d/kadmind
> /etc/rc.d/keyserv
> /etc/rc.d/kpasswdd
> /etc/rc.d/nfsuserd
> /etc/rc.d/gssd
> /etc/rc.d/quota
> /etc/rc.d/mountd
> /etc/rc.d/nfsd
> /etc/rc.d/statd
> /etc/rc.d/lockd
> /etc/rc.d/pppoed
> /etc/rc.d/pwcheck
> /etc/rc.d/DAEMON
> /etc/rc.d/utx
> /etc/rc.d/ugidfw
> /etc/rc.d/ubthidhci
> /etc/rc.d/timed
> /etc/rc.d/apm
> /etc/rc.d/apmd
> /etc/rc.d/bootparams
> /etc/rc.d/hcsecd
> /etc/rc.d/bthidd
> /etc/rc.d/local
> /etc/rc.d/lpd
> /etc/rc.d/motd
> /etc/rc.d/mountlate
> /etc/rc.d/nscd
> /etc/rc.d/ntpd
> /etc/rc.d/powerd
> /etc/rc.d/rarpd
> /etc/rc.d/rctl
> /etc/rc.d/sdpd
> /etc/rc.d/rfcomm_pppd_server
> /etc/rc.d/rtadvd
> /etc/rc.d/rwho
> /etc/rc.d/LOGIN
> /etc/rc.d/syscons
> /etc/rc.d/swaplate
> /etc/rc.d/sshd
> /etc/rc.d/sendmail
> /etc/rc.d/cron
> /etc/rc.d/jail
> /etc/rc.d/localpkg
> /etc/rc.d/securelevel
> /etc/rc.d/power_profile
> /etc/rc.d/othermta
> /etc/rc.d/nfscbd
> /etc/rc.d/natd
> /etc/rc.d/msgs
> /etc/rc.d/moused
> /etc/rc.d/mixer
> /etc/rc.d/kfd
> /etc/rc.d/inetd
> /etc/rc.d/hostapd
> /etc/rc.d/gptboot
> /etc/rc.d/geli2
> /etc/rc.d/ftpd
> /etc/rc.d/ftp-proxy
> /etc/rc.d/dhclient
> /etc/rc.d/bsnmpd
> /etc/rc.d/bluetooth
> /etc/rc.d/bgfsck
>
>
> >
> > say?
> >
> > With regards,
> > Timur Bakeyev.
> >
> >
> > On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann <
> ohart...@zedat.fu-berlin.de>wrote:
> >
> > > On CURRENT, I receive this error message when trying to start
> net/samba36:
> > &g

Re: net/samba36: ERROR: lock directory /var/run/samba/ does not exist

[Timur I. Bakeyev]

Hi, Oliver!

Please check in the rc.d/samba function samba_start_precmd(). It should
contain valid /var/run/samba path.

Is this problem occurs  only on restart(reboot) of the server? If you start
samba manually after the boot - does it run?

It could be, that in FreeBSD 11 rc order has changed somehow and samba
starts before /var/run is mounted. What does:

# rcorder /etc/rc.d/* /usr/local/etc.rc.d/*

say?

With regards,
Timur Bakeyev.


On Tue, Mar 18, 2014 at 3:11 PM, O. Hartmann wrote:

> On CURRENT, I receive this error message when trying to start net/samba36:
>
> ERROR: lock directory /var/run/samba/ does not exist
>
> System: FreeBSD 11.0-CURRENT #1 r263252: Sun Mar 16 22:27:29 CET 2014 amd64
>
> Filesystem /var/run is tmpfs and resides on a SSD!
>
> I'm confused. Years ago, I had a similar problem with samba3[46] when I
> intriduced myself
> to tmpfs-backed /var/run. The start-script of sambe residing in
> /usr/local/etc/rc.d/samba
> wasn't capable of checking the existence of /var/run/samba so startup
> failed. in the
> meanwhile, I thought this was fixed - the problem I report in is present
> somehow since
> January, but I can not be more specific.
>
> I deleted /usr/local/etc/rc.d/samba and reinstalled net/samba36. After
> reinstallation,
> samba can be started on a regular basis. But after a reboot, it couldn't.
>
> I have no clue what is happening here. Any suggestions?
>
> Oliver
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Problems with samba-* ports on arm

[Timur I. Bakeyev]

File a PR. The problem is that I don't have ARM box around, so it's hard to
debug.

There is an attempt to address a problem with the ARM in the port:
.if ${ARCH} == "arm"
CONFIGURE_ARGS+=--disable-pie
.endif

But it never was tested live.




On Mon, Nov 5, 2012 at 1:09 PM, Łukasz  wrote:

> Hello everyone,
>  I'm not sure whether this is the correct list, but I would like to
> report my efforts to build and run samba on ARM machine (sheevaplug) -
> # uname -mopr
> FreeBSD 8.3-STABLE arm arm
>
> samba36-3.6.9
> nmbd - works fine
> smbd - core dump with bus error
>
>
>  # smbd -V
> Version 3.6.9
>
>  # gdb smbd smbd.core
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "arm-marcel-freebsd"...
> Core was generated by `smbd'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /lib/libcrypt.so.5...done.
> Loaded symbols for /lib/libcrypt.so.5
> Reading symbols from /usr/lib/libpam.so.5...done.
> Loaded symbols for /usr/lib/libpam.so.5
> Reading symbols from /usr/local/lib/libexecinfo.so.1...done.
> Loaded symbols for /usr/local/lib/libexecinfo.so.1
> Reading symbols from /lib/libmd.so.5...done.
> Loaded symbols for /lib/libmd.so.5
> Reading symbols from /usr/local/lib/libiconv.so.3...done.
> Loaded symbols for /usr/local/lib/libiconv.so.3
> Reading symbols from /usr/local/lib/libdmalloc.so.1...done.
> Loaded symbols for /usr/local/lib/libdmalloc.so.1
> Reading symbols from /usr/local/lib/libpopt.so.0...done.
> Loaded symbols for /usr/local/lib/libpopt.so.0
> Reading symbols from /usr/local/lib/libtalloc.so.2...done.
> Loaded symbols for /usr/local/lib/libtalloc.so.2
> Reading symbols from /usr/local/lib/libtdb.so.1...done.
> Loaded symbols for /usr/local/lib/libtdb.so.1
> Reading symbols from /lib/libz.so.5...done.
> Loaded symbols for /lib/libz.so.5
> Reading symbols from /lib/libc.so.7...done.
> Loaded symbols for /lib/libc.so.7
> Reading symbols from /lib/libm.so.5...done.
> Loaded symbols for /lib/libm.so.5
> Reading symbols from /usr/local/lib/libintl.so.9...done.
> Loaded symbols for /usr/local/lib/libintl.so.9
> Reading symbols from /usr/lib/librt.so.1...done.
> Loaded symbols for /usr/lib/librt.so.1
> Reading symbols from /libexec/ld-elf.so.1...done.
> Loaded symbols for /libexec/ld-elf.so.1
> #0  0x208d20b0 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
> (gdb) bt
> #0  0x208d20b0 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
> #1  0x208d1c84 in backtrace () from /usr/local/lib/libexecinfo.so.1
> #2  0x003df308 in log_stack_trace () at lib/util.c:1217
> #3  0x003df4bc in smb_panic (why=0x7cce40 "internal error") at
> lib/util.c:1118
> #4  0x003cde8c in sig_fault (sig=8179264) at lib/fault.c:57
> #5  0x003cde8c in sig_fault (sig=8179264) at lib/fault.c:57
> (gdb)
>
> Below are the options:
> # Options for samba36-3.6.9
> _OPTIONS_READ=samba36-3.6.9
> _FILE_COMPLETE_OPTIONS_LIST= LDAP ADS CUPS WINBIND SWAT ACL_SUPPORT
> AIO_SUPPORT FAM_SUPPORT SYSLOG QUOTAS UTMP PAM_SMBPASS DNSUPDATE AVAHI
> PTHREADPOOL EXP_MODULES POPT IPV6 MAX_DEBUG SMBTORTURE
> OPTIONS_FILE_UNSET+=LDAP
> OPTIONS_FILE_UNSET+=ADS
> OPTIONS_FILE_UNSET+=CUPS
> OPTIONS_FILE_UNSET+=WINBIND
> OPTIONS_FILE_UNSET+=SWAT
> OPTIONS_FILE_SET+=ACL_SUPPORT
> OPTIONS_FILE_UNSET+=AIO_SUPPORT
> OPTIONS_FILE_UNSET+=FAM_SUPPORT
> OPTIONS_FILE_SET+=SYSLOG
> OPTIONS_FILE_UNSET+=QUOTAS
> OPTIONS_FILE_UNSET+=UTMP
> OPTIONS_FILE_UNSET+=PAM_SMBPASS
> OPTIONS_FILE_UNSET+=DNSUPDATE
> OPTIONS_FILE_UNSET+=AVAHI
> OPTIONS_FILE_UNSET+=PTHREADPOOL
> OPTIONS_FILE_UNSET+=EXP_MODULES
> OPTIONS_FILE_SET+=POPT
> OPTIONS_FILE_SET+=IPV6
> OPTIONS_FILE_SET+=MAX_DEBUG
> OPTIONS_FILE_UNSET+=SMBTORTURE
>
> For samba35-3.5.18 there is completely the same problem.
>
> samba34-3.4.17
>
> ===>  Building for samba34-3.4.17
> cd /usr/ports/net/samba34/work/samba-3.4.17/source3 && make pch
> rm -f
> /usr/ports/net/samba34/work/samba-3.4.17/source3/include/includes.h.gch
> make
> /usr/ports/net/samba34/work/samba-3.4.17/source3/include/includes.h.gch
> cc -O -pipe -g -g -Wall -Wshadow -Wpointer-arith -Wcast-align
> -Wwrite-strings -DDEBUG_PASSWORD -DDEVELOPER
> -Wdeclaration-after-statement -Werror-implicit-function-declaration
> -Wstrict-prototypes -I.
> -I/usr/ports/net/samba34/work/samba-3.4.17/source3
> -I/usr/ports/net/samba34/work/samba-3.4.17/source3/iniparser/src
> -Iinclude -I./include  -I. -I. -I./../lib/replace -I/usr/local/include
>   -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc
> -I./..  -DHAVE_CONFIG_H  -I/usr/local/include -g -Iinclude -I./include
> -I. -I. -I./../lib/replace -I/usr/local/include -I./../lib/tevent
> -I./../lib/tdb/include -I./libaddns -I./librp

Re: FreeBSD Port: samba34-3.4.14

[Timur I. Bakeyev]

On Tue, Apr 10, 2012 at 9:57 AM, Da Rock
 wrote:
> On 04/10/12 16:30, Chuck Swiger wrote:
>>
>> On Apr 9, 2012, at 5:26 PM, Da Rock wrote:
>> [ ... ]

 If you think there is a missing dependency, then doing send-pr with the
 fix is a reasonable procedure.
>>>
>>> I was only thinking the maintainer might want to know and fix and test
>>> themselves before commit. I know I would as a maintainer.
>>
>> Sure-- a PR with a change to a port will be assigned to the maintainer to
>> test and approve.
>
>
> Ah. I wasn't aware that was the case, especially if the maintainer cannot
> specifically commit.
>> Note that I'd gotten the impression that you had installed libnet
>> separately, which would be a library and not just a build dependency...
>
> I am still looking into it as time permits, but I'm not sure I understand
> the difference? I had to install libnet separately in order to build. How
> does that fit in your comment? I'm still a very newbie developer so I'm not
> always accurately understanding the terms, I think.

I'm not sure, which libnet you are referring to. None of the Sambas
should really depend from anything called libnet. At least -
externally.

Also, please show the content of your /etc/make.conf, it could be that
you are mangling include flags.

With regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba34-3.4.14

[Timur I. Bakeyev]

Hi!

Can you show the build output? Port should't directly dipend from
anything like this.

Cheers.

On Fri, Apr 6, 2012 at 3:40 AM, Da Rock
 wrote:
> Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on
> net/libnet. Maybe need to add this to the port?
>
> Cheers
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: "UPDATING" file

[Timur I. Bakeyev]

On Mon, Jun 20, 2011 at 1:41 PM, Jerry  wrote:

> 
> 20110620:
>  AFFECTS: users of net/samba35
>  AUTHOR: ti...@freebsd.org
>
>  A bug, introduced by local patch to pam_winbind.so, that made it coredump
>  was spotted by Martin Minkus. It is fixed in the 3.5.9 version of the
> port.
>  So, if pam_winbind.so strated to work for you - send him kudos.
> 
>
> Interestingly enough, while "strated"
>  might be
> apropos, I think the author meant "started".
>
> Author has sloppy  fingers :)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba-libsmbclient SAMBA_PORT= -> SAMBA_PORT?=

[Timur I. Bakeyev]

Hi!

On Tue, Mar 1, 2011 at 6:46 AM, jhell  wrote:

> Could you please change the SAMBA_PORT= directive in samba-libsmbclient to
> SAMBA_PORT?= samba34 so it can be overridden by make.conf or command line ?

No, I believe it's a bad idea.

> There is probably some bad magic that will happen on a machine with samba35
> installed and libsmbclient34 and I would like to stay as close as I can to
> using the same version of samba that's installed and making the above
> corrections would still allow for the current functionality to be kept while
> allowing an override.

The flexibility in the base port definition is done to ease my life,
as a maintainer,
not to easily switch between the versions.

Code wise libsmbclient in 34 and 35 should be the same, as the library
isn't actively developed
and stable. I don't want people to recompile firefox, for example,
cause  version of
Samba have been bumped again - there is no real need for this. Another story
is that it's hard to guaranty that that between 34, 35 and 36 version
the packaging list
of the port will remain the same.
>
> Specifically I would like to stay away from having to edit anything in the
> ports structure Makefiles as those changes would not be static across port
> snaps.
>
Regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba35-3.5.6_1

[Timur I. Bakeyev]

Hi!

You should distinct between *packages*, which a precompiled ready to
install binaries and *ports*, which are merely recipies how to
assemble binaries with the options you like.

The message stresses that *package* doesn't include ADS functionality
and that you have to compile port yourself.

Regards,
Timur.

On Thu, Feb 3, 2011 at 1:30 AM, David M. Wassman  wrote:
> At the end of the port build there is a message that says ADS support was not 
> included in the build. Does this mean that even if you added ADS support in 
> the port config, it is still not in the build? If so, why the option?
>
> Sent from my iPad
>
>
>
> David M. Wassman, MCSE, CCENT, Security+
>
> Carr, Riggs & Ingram, LLC
> 4010 NW 25th Place
> Gainesville, FL 32606
> Voice: 352-372-6300
> Fax: 352-375-1583
>
> http://www.cricpa.com
>
>
>
> **
>
> In compliance with IRS Circular 230:
>
> Any statements or tax advice that are contained in this email are not 
> intended or written to be used, and cannot be used by any taxpayer, for the 
> purpose of avoiding penalties that may be imposed on the taxpayer.
> The information contained in this message may be privileged and confidential 
> and protected from disclosure. It is intended exclusively for the individual 
> or entity to which it is addressed. This communication may contain 
> information that is proprietary, privileged or confidential or otherwise 
> legally exempt from disclosure. If the reader of this message is not the 
> intended recipient, or an employee or agent responsible for delivering this 
> message to the intended recipient, you are hereby notified that any 
> dissemination, distribution or copying of this communication is strictly 
> prohibited. If you have received this communication in error, please notify 
> us immediately by replying to the message and deleting it from your computer. 
> Thank you. Carr, Riggs & Ingram LLC
>
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [Samba] Samba upgrade HowTo requested

[Timur I. Bakeyev]

Hi, Volker!

On Sat, Dec 18, 2010 at 10:10 AM, Volker Lendecke
 wrote:
> On Fri, Dec 17, 2010 at 11:26:12AM +0100, Willy Offermans wrote:
>>
>> 20101026:
>>   AFFECTS: users of net/samba35
>>   AUTHOR: Timur Bakeyev 
>>
>>   This is the latest stable release of the Samba3 distribution. It has
>>   been extended with the experimental support of the NFS4-like ACLs on
>>   ZFS partitions, thanks to the sysutils/libsunacl library by Edward
>>   Tomasz Napierala(trasz). This support haven't been tested thoroughly,
>>   so try it on your own risk.
>
> This looks interesting. I just did a portsnap fetch update
> in my FreeBSD 8.1 box, but I don't find that snippet. Where
> can I find those patches?

There are small patches in the port itself to detect and incorporate
libsunacl via configure and build vfs_zfsacl module OOTB. As for the
lib itself - it is situated in /usr/ports/sysutils/libsunacl.

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: samba and zfs|nfsv4 acls

[Timur I. Bakeyev]

Hi!

I've got a patch, that should solve this problem, using new port
devel/libsunacl. It's coming :)

With regards,
Timur.

On Fri, Apr 2, 2010 at 5:58 PM, Greg Byshenk  wrote:
> Does samba on FreeBSD work with ZFS ACLs?
>
> Using the port, it appears that the vfs_zfsacl module is not built, even
> when experimental modules are selected.  I've tried enabling nfs4_acls
> and vfs_zfsacl, but that results in an error (see below).
>
> Will this work if I compile by hand, or do nfsv4 ACLs not work with Samba?
>
>
> Compiling modules/vfs_zfsacl.c
> modules/vfs_zfsacl.c: In function 'zfs_get_nt_acl_common':
> modules/vfs_zfsacl.c:42: error: 'ace_t' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:42: error: (Each undeclared identifier is reported only 
> once
> modules/vfs_zfsacl.c:42: error: for each function it appears in.)
> modules/vfs_zfsacl.c:42: error: 'acebuf' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:47: error: 'ACE_GETACLCNT' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:60: error: expected expression before ')' token
> modules/vfs_zfsacl.c:65: error: 'ACE_GETACL' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:82: error: 'ACE_OWNER' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:85: error: 'ACE_GROUP' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:88: error: 'ACE_EVERYONE' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c: In function 'zfs_process_smbacl':
> modules/vfs_zfsacl.c:106: error: 'ace_t' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:106: error: 'acebuf' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:112: error: expected expression before ')' token
> modules/vfs_zfsacl.c:130: error: 'ACE_EVERYONE' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:133: error: 'ACE_OWNER' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:136: error: 'ACE_GROUP' undeclared (first use in this 
> function)
> modules/vfs_zfsacl.c:148: error: 'ACE_SETACL' undeclared (first use in this 
> function)
> The following command failed:
> cc -O2 -pipe -DLDAP_DEPRECATED -fno-strict-aliasing -I. 
> -I/usr/ports/net/samba34/work/samba-3.4.5/so
> urce3 -I/usr/ports/net/samba34/work/samba-3.4.5/source3/iniparser/src 
> -Iinclude -I./include  -I. -I.
>  -I./../lib/replace -I/usr/local/include   -I./../lib/tevent 
> -I./../lib/tdb/include -I./libaddns -I.
> /librpc -I./.. -DHAVE_CONFIG_H  -I/usr/local/include -Iinclude -I./include 
> -I. -I. -I./../lib/replac
> e -I/usr/local/include -I./../lib/tevent -I./../lib/tdb/include -I./libaddns 
> -I./librpc -I./.. -I./.
> ./lib/popt -I/usr/local/include -DLDAP_DEPRECATED  
> -I/usr/ports/net/samba34/work/samba-3.4.5/source3
> /lib -I.. -I../source4 -D_SAMBA_BUILD_=3 -D_SAMBA_BUILD_=3 -fPIC -DPIC -c 
> modules/vfs_zfsacl.c -o mo
> dules/vfs_zfsacl.o
> gmake: *** [modules/vfs_zfsacl.o] Error 1
> *** Error code 1
>
> Stop in /usr/ports/net/samba34.
> *** Error code 1
>
> Stop in /usr/ports/net/samba34.
>
>
> --
> greg byshenk  -  gbysh...@byshenk.net  -  Leiden, NL
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: samba34 fails building on FreeBSD 8.0-STABLE: Compiling lib/memcache.c, lib/memcache.c:29: error: expected specifier-qualifier-list before 'uint8'

[Timur I. Bakeyev]

Hi, Oliver!

On Sat, Feb 6, 2010 at 4:46 PM, O. Hartmann
 wrote:
> On 02/06/10 16:24, Timur I. Bakeyev wrote:
>> On Fri, Feb 05, 2010 at 11:02:18AM +, O. Hartmann wrote:
>>>
>>> Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the
>>> following error and it seems a bit sticky.
>>
>> Check, that there is no memcache.h somewhere in your include paths, in
>> particular in /usr/local/include.
>>
>> Also, try last update if the port.
>
> thanks for responding. Indeed, their was a port installed, needed by
> www/lighttpd. After temporarily deinstalling libmemcache, the installation
> of the port went all right. I figured that it would be better leaving
> lighttpd's option 'with memcache' untouched and switched off to be on the
> secure side.

Yeh, that's a trap... I hope, that with my last update of the port
Samba won't pick up headers from the /usr/local/include
if it has a local one with the same name. So, should be safe to
combine both ports :)

With best regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba34 does not create all required directories

[Timur I. Bakeyev]

Hi!

It looks like the problem was created by the --with-fhs flag, which
reset cachedir and statedir do it's default values.
With the flag removed those directories are the same as the lockdir.

Not sure, why rundir wasn't created by the package - this is done by
pkg-install script and should work both form port and package.

With regards,
Timur.

On Fri, Feb 5, 2010 at 3:36 PM, Spil Oss  wrote:
> Hi,
>
> Just built net/samba34 (only ACL, AIO, FAM, SYSLOG and POPT enabled)
> and created a package samba34-3.4.5.tbz in my build jail.
>
> Installed the package in a different jail and couldn't start samba.
>
> First error was the pid-files related to /var/run/samba34 not existing
>
> Second error
> "initialise_wins: failed to open wins.tdb. Error was No such file or 
> directory"
> Solved by tempory disabling wins support in smb.conf. After fixing
> third error I re-enabled it and it lives in /var/lib/samba as well
>
> Third error
> "write_browse_list: Can't open file /var/lib/samba/browse.dat"
>
> 1. /var/run/samba34 was not created by the package (was created in the
> build jail)
> 2. /var/lib/samba was not created
>
> smbd -b | grep DIR revealed all directories that must exist when starting 
> samba
>
> Upgrading info is a bit meager, no UPGRADING file and the doc contains
> only a reference to the smbpasswd deprecation.
>
>
> Kind regards,
>
> Spil.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: samba34 fails building on FreeBSD 8.0-STABLE: Compiling lib/memcache.c, lib/memcache.c:29: error: expected specifier-qualifier-list before 'uint8'

[Timur I. Bakeyev]

Hi!

On Fri, Feb 05, 2010 at 11:02:18AM +, O. Hartmann wrote:
> Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the 
> following error and it seems a bit sticky.

Check, that there is no memcache.h somewhere in your include paths, in
particular in /usr/local/include.

Also, try last update if the port.

With best regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: net/samba34 does not create all required directories

[Timur I. Bakeyev]

Hi, Spil!

On Fri, Feb 05, 2010 at 03:42:04PM +0100, Spil Oss wrote:
> On Fri, Feb 5, 2010 at 3:36 PM, Spil Oss  wrote:
> >
> > First error was the pid-files related to /var/run/samba34 not existing
> >
> > Second error
> > "initialise_wins: failed to open wins.tdb. Error was No such file or 
> > directory"
> > Solved by tempory disabling wins support in smb.conf. After fixing
> > third error I re-enabled it and it lives in /var/lib/samba as well
> >
> > Third error
> > "write_browse_list: Can't open file /var/lib/samba/browse.dat"
> >
> > 1. /var/run/samba34 was not created by the package (was created in the
> > build jail)
> > 2. /var/lib/samba was not created
> 
> Changelog contains the following changes
> --with-statedir=DIR   Where to put persistent state files
> --with-cachedir=DIR   Where to put temporary cache files
> 
> Guess these should point to /var/db/samba34 rather than /var/lib/samba
> 
> Just let me know if I need to file a PR

PR's are always better than just random mail to the ML, as they get assigned
to maitainer.

Can you, please, summarize your findings and send them in the PR?

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Samba 3.x build problems with LDAP support

[Timur I. Bakeyev]

Hi, Erik!

I guess the answer lays in the config.log, where it said:

idmap_ldap ... static

So, it is compiled into Samba.

Regards,
Timur.

On Sat, Apr 11, 2009 at 10:39 PM, Erik Van Benschoten
 wrote:
> Hello,
>
> Is anyone else experiencing problems building/installing samba32 or samba33?
> Either port does not seem to install the idmap_ldap backend. I've tried
> uninstalling
> everything and then reinstalling from scratch - no luck. The other idmap
> backends
> (ad, adex, hash, rid & tdb2) are installed fine.
>
> Thanks,
> Erik Van Benschoten
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Samba3 + Jails in FreeBSD

[Timur I. Bakeyev]

Hi!

On Wed, Mar 18, 2009 at 8:34 PM, Felipe Carlo  wrote:
> Hello,
>
> I have one problem with Samba in a Jail.
>
> When I try to start the samba I have this message:
>
> # /usr/local/etc/rc.d/samba.sh start
> %%WINBIND%%#: not found
> %%WINBIND%%#winbindd_enable=YES: not found
> .: Can't open %%RC_SUBR%%: No such file or directory

What version of Samba port do you use? How did you make your
installation? Was it port or package?

In general, I don't think, that Samba will work in jail.

Regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba-libsmbclient-3.0.34_1

[Timur I. Bakeyev]

Hi!

On Wed, Mar 18, 2009 at 3:41 AM, Patrick Strateman
 wrote:
> sudo make clean install 2> ~/stderr.txt >~/stdout.txt
>
>
> $ uname -a
> FreeBSD phantomcircuit.mine.nu 7.1-RELEASE FreeBSD 7.1-RELEASE #0: Thu
> Jan  1 14:37:25 UTC 2009
> r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>
>
> this is the latest version from portsnap

You miss list of the installed ports in your mail, but I can bet from
the error, that you have installed port version of Heimdal or MIT
Kerberos. That doesn't play well together.

Options you have are:

1. Uncheck ADS support for the libsmbclient('make config' if any)
2. Depending from the port you have installed, set either HEIMDAL_HOME
or KRB5_HOME to point to LOCALBASE.

Regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Port Request: gluster

[Timur I. Bakeyev]

Hi, Paul!

I'm working on it for quite a while, but still there are some rough
edges. What is your user experience with it?

With regards,
Timur.

On Wed, Mar 11, 2009 at 10:12 PM, Pathiakis, Paul
 wrote:
> Hi to all!
>
> Has anything progressed on this?
>
> I'm actually building it by hand on a couple of 7.1 machines.  I expect
> it will be interesting.
>
> I still look forward to the port. :-)
>
> Thank you!
>
> Paul Pathiakis
> UNIX/Linux Systems Engineer
> Iron Mountain Digital
> 120 Turnpike Rd.
> Southborough, MA 01772
>
>
> Microsoft - Where do you want to go today?
> Linux - Where do you want to go tomorrow?
> FreeBSD - Will you guys come on already?
>
>
> -Original Message-
> From: Jim Riggs [mailto:po...@christianserving.org]
> Sent: Friday, February 20, 2009 8:31 PM
> To: David N
> Cc: Pathiakis, Paul; po...@freebsd.org; Steven Kreuzer
> Subject: Re: Port Request: gluster
>
> On 02/20/2009 11:40, David N wrote:
>> 2009/2/21 Pathiakis, Paul:
>>> Steven,
>>>
>>> I'm going to start testing it in a pre-production environment.  It
> seems
>>> so straightforward, integrates with ZFS, it has simple configuration
>>> files, all around, I'm hoping that it garners more
>>> clustering/replication for FreeBSD.  Many of the other solutions are
>>> quite tedious and setup complexity is quite annoying.
>>>
>>>
>>>
>>> -Original Message-
>>> From: Steven Kreuzer [mailto:ste...@hudson-trading.com] On Behalf Of
>>> Steven Kreuzer
>>> Sent: Friday, February 20, 2009 11:30 AM
>>> To: Pathiakis, Paul
>>> Cc: po...@freebsd.org
>>> Subject: Re: Port Request: gluster
>>>
>>>
>>> On Feb 20, 2009, at 9:51 AM, Pathiakis, Paul wrote:
>>>
 Hi,



 I'd like to request that the gluster clustering/filesystem software
> be
 ported and supported.  This looks to be a very simple,
> straightforward
 and viable clustering solution which FreeBSD has always lacked.
>>> This looks like a very interesting project. I might be able to take
>>> some time
>>> over the weekend and create a port for this.
>>>
>>> Out of curiosity, have you been using it in production? If so, can
> you
>>> describe your setup
>>> and your experience with it?
>>>
>>> Steven Kreuzer
>>> http://www.exit2shell.com/~skreuzer
>>>
>> Looks promising
>> http://www.gluster.org/docs/index.php/GlusterFS_on_BSD
>
>
> Several weeks ago I actually created a port for glusterfs as I was
> hoping to implement it myself.  I'll have to see if I saved any of my
> work.  I actually had a working port, but I may have dumped it.  I will
> be happy to submit it if I can find it.  I just don't know that I will
> be able to maintain it.
>
> A couple of notes from what I found:
>
> 1. It does not yet integrate with FreeBSD's implementation of ZFS (at
> least not in 7.x) due to the lack of ACL support.  You can use it with a
> UFS partition or a UFS zvol.  (Using a zvol requires a patch pjd@
> recommended for performance improvements.)
>
> 2. Performance in my setup was not very good over 2x1Gb LAGG.  It might
> be better over a faster, dedicated channel of some type.
>
> - Jim
>
>
> The information contained in this email message and its attachments
> is intended
> only for the private and confidential use of the recipient(s) named
> above, unless the sender expressly agrees otherwise. Transmission
> of email over the Internet
>  is not a secure communications medium. If you are requesting or
> have requested
> the transmittal of personal data, as defined in applicable privacy
> laws by means
>  of email or in an attachment to email you must select a more
> secure alternate means of transmittal that supports your
> obligations to protect such personal data. If the reader of this
> message is not the intended recipient and/or you have received this
> email in error, you must take no action based on the information in
> this email and you are hereby notified that any dissemination,
> misuse, copying, or disclosure of this communication is strictly
> prohibited. If you have received
> this communication in error, please notify us immediately by email
> and delete the original message.
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: samba-3.3.1 and pam (sshd)

[Timur I. Bakeyev]

Hi, Johan!

I've started to write, how to test pam modules, but while doing that
found that indeed, pam_winbind.so is missing some symbols :(

I'm looking into that right now. Next time write a PR in such a case :)

With best regards,
Timur.

On Tue, Mar 10, 2009 at 11:03 AM, Johan Hendriks  wrote:
> Hello all
> i have updated my samba-3.2.8 to samba-3.3.1.
> This machine is joined to a windows 2003 server.
>
> I used the following line in my /etc/pam.d/sshd to use pam authentication of 
> some windows users.
> auth            sufficient      /usr/local/lib/pam_winbind.so
>
> This all Works for samba-3.2.x , but after the upgrade i get the following 
> error.
>
> In /var/log/messages the following comes up
>
> Mar 10 10:13:08 intranet sshd[52539]: in openpam_load_module(): no 
> /usr/local/lib/pam_winbind.so found
>
> Mar 10 10:13:08 intranet sshd[52539]: fatal: PAM: initialisation failed
>
>
>
> The file /usr/local/lib/pam_winbind.so  is there?
>
>  after a downgrade from 3.3.1 to 3.2.8 all is working again.
>
>
> regards,
>
> Johan Hendriks
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: FreeBSD Port: samba-3.0.30,1

[Timur I. Bakeyev]

On Thu, Jul 3, 2008 at 5:03 AM, Dmitry <[EMAIL PROTECTED]> wrote:
> Hello. What about samba 3.2.0?

Later, possibly after 3.2.1 - too many problems with it.

Cheers,
Timur,
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: compat-6x does not work when kernel has NO_KSE

[Timur I. Bakeyev]

On Wed, Sep 12, 2007 at 10:21:59AM -0400, Vivek Khera wrote:
> On Sep 12, 2007, at 5:37 AM, Jiawei Ye wrote:
> >On 9/12/07, Jiawei Ye <[EMAIL PROTECTED]> wrote:
> >
> >>[/usr/local/diablo-jdk1.5.0/jre/bin/java]
> >>libpthread.so.2 libthr.so
> >Changing this to libthr.so.2 fixes the problem. Sorry about the noise.
> 
> curious... on 6.1/6.2 I *must* use libpthread as the threading library for 
> diablo jdk. it throws hotspot compiler errors at random if I map it to libthr.

I second Vivek here - there are some weird problems with compiler on
FreeBSD 6.x amd64 if you use libthr as a threading library. It's
difficult to say - why, but the effect was noted both by me and Vivek.

So, beware, there are dragons there.

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: textproc/p5-XML-LibXML Install Error

[Timur I. Bakeyev]

Hi!

On Fri, Aug 31, 2007 at 11:10:08AM -0700, Cy Schubert wrote:
> Has anyone seen this before. This is on the AMD64 platform running FreeBSD 
> AMD64 with most ports (the ones that would build that is) built for AMD64. 
> Perl 5.8.8 was built successfully for AMD64. This builds and installs when 
> the system is booted in IA32 mode using FreeBSD ports built for IA32.
> 
> /Common.so' for module XML::LibXML::Common: /usr/local/lib/perl5/site_perl/5
> .8.8/mach/auto/XML/LibXML/Common/Common.so: Undefined symbol "PL_sv_undef" 
> at /usr/local/lib/perl5/5.8.8/mach/DynaLoader.pm line 230.

This is the cause of the problem - "PL_sv_undef" doesn't resolve with
dynamic linking. Recently I got all sort of problems trying to run 32
binaries  on AMD64 system. In this case, I suspect, linker can't find
appropriate version of libperl, which defines all that symbols.

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: anyone able to build jboss4 on amd64?

[Timur I. Bakeyev]

Hi, Vivek!

Sorry for a long silence, I was AFK.

On Thu, Aug 30, 2007 at 11:33:53AM -0400, Vivek Khera wrote:
> On Aug 30, 2007, at 4:40 AM, Timur I. Bakeyev wrote:
> 
> >Which threading libraries do you use? I remember having similar problem with
> >libthr.so enabled in libmap.conf. As soon as I tried:
> >
> >[java]
> >libpthread.so   libpthread.so
> >libpthread.so.2 libpthread.so.2
> 
> This was the key!  Thanks!
> 
> I added your java-specific map after that and it built to completion without 
> error. Can this be documented somewhere?  Most helpfully it would be a 
> message 
> upon installing the diablo package.

I looked into the logs I still kept from the installation of the kettle
- a Java based warehouse software and apparently I had exactly the same error:

#  Internal Error (4E4D4554484F440E4350500525), pid=41602, tid=0xa04800
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (diablo-1.5.0_07-b01 mixed mode)

So, on amd64 with libthr native 64 Java dies on certain applications. I
think, it should actually be reported as a bug to the freebsd-java team.
Can you do this, while your memory is fresh? I can provide additional
log files, but  don't remember details now, as it was while ago.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: samba 3.0.25b

[Timur I. Bakeyev]

Hi, Johan!

On Thu, Jul 26, 2007 at 01:03:51PM +0200, Johan Hendriks wrote:
> Does anyone know when the latest samba will hit the ports tree?

Cc: me if you want to get an answer in a time fasion :)

> Or is the maintainer busy with the samba, zfs issue on current.

3.0.25b had some issues that made it not worth the upgrading. 3.0.25c is
coming this week, so we'll see, how does it behave. In general, I hear a
lot of complains about recent versions of Samba, so trying to be extra
caucious with simple version bumping.

With regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.25a_1,1

[Timur I. Bakeyev]

Hi, Robert!

On Thu, Aug 02, 2007 at 05:15:51PM +0930, Robert Hettner wrote:
> 
> I tried make clean but still get the following
> 
> bradmann# cd /usr/ports/net/samba3
> bradmann# make
> ===>  samba-3.0.25a_1,1 dynamic DNS updates require ADS support.
> *** Error code 1

When you install the port it says:
===>  ---
===>  Run 'make config' to (re)configure the port
===>  ---

Does it ring a bell :)? 'make rmconfig' may also be useful.

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.25a_1,1

[Timur I. Bakeyev]

Hi, Mads!

On Fri, Jul 20, 2007 at 04:54:57PM +0200, Mads L?nsethagen wrote:
> Hi!
> 
> I've noticed a bug in this recent version of Samba which forced me to
> downgrade to version 3.0.24,1. It has something to do with
> fusefs-unionfs, but I don't know how.

I suspect, this is the sign of the same error we have with other non-UFS 
file systems in Samba3.

See, for example:

https://bugzilla.samba.org/show_bug.cgi?id=4715

There are also similar ports/109160, ports/113158 and few others.

So, the problem known, although there is no real cure for it right now...

With regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [net/samba3] Upgrade to Samba 3.0.25a

[Timur I. Bakeyev]

On Tue, Jun 05, 2007 at 11:37:03AM +0200, Simon L. Nielsen wrote:
> On 2007.06.05 10:22:44 +0200, Timur I. Bakeyev wrote:
> 
> BTW. in cases like this, where the maintainer want to fix a security
> issue but would prefer to wait with a full upgrade, you might want to
> try and poke the FreeBSD Security Team (secteam@) since we might have
> patches to only fix the issue security issue(s).  Specifically for
> Samba we normally do get patches from the Samba developers for their
> security advisories.

As a maintainer I get the patches as well, as well as an early access to
the tarballs. But with such border cases when new release comes with new
features and security fixes all together it's nice to have ability to
provide both versions - old one with just sec fixes and new one with
new features. As we don't have ports versioning yet, employing -devil
suffix could be reasonable solution to provide both versions.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [net/samba3] Upgrade to Samba 3.0.25a

[Timur I. Bakeyev]

On Tue, Jun 05, 2007 at 11:33:35AM +0200, Andrea Venturoli wrote:
> Timur I. Bakeyev wrote:
> 
> >I would like to stress, that after problems with the last Samba releases
> >I decided to delay new port for at least one week to collect feedback
> >from mailing lists and other sources, as well as from developers to see,
> >if there are no fatal problems with the release. Unfortunately, with
> >security updates we can't wait too long, thus 3.0.25 slipped into the
> >ports collection, although it possibly shouldn't.
> 
> Ok, this is however not a fault in the way FreeBSD handles port.
> This time it's samba itself that should be blamed (although I'm not 
> recriminating here).

Unfortunately, Samba3 became so big and hairy, that fixing one problem
there creates few new. So, for the last ~10 releases this was pretty
common situation when erratra release was following very quickly.

> >I'm planning to ressurect net/samba3-devel port to put latest releases there,
> >leaving net/samba3 for proven to work releases.
> 
> I don't think this issues are related.
> If you feel you should, then obviously go ahead, but, as I see it, both 
> 3.0.25 
> and 3.0.25a would have gone into samba3, not samba3-devel.

I want people to have something stable to work with, when new features
may wait. Possibly, both samba3 and samba3-devel will have same ports
in majority of the time, but not always.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [net/samba3] Upgrade to Samba 3.0.25a

[Timur I. Bakeyev]

On Tue, Jun 05, 2007 at 09:31:57AM +0200, Spil Oss wrote:
> Hi All,
> 
> Is anything known on an upgrade of the samba3 port to samba 3.0.25a?
> When the 3.0.25 port was committed, shortly after samba released
> 3.0.25a. There seems to be quite a number of problems fixed in
> 3.0.25a.

And:

Re: ports/113358: MAINTAINER-UPDATE: Update of net/samba3 to 3.0.25a version

just arrived. Fell free to try it and test.

With regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: [net/samba3] Upgrade to Samba 3.0.25a

[Timur I. Bakeyev]

Hi!

On Tue, Jun 05, 2007 at 09:31:57AM +0200, Spil Oss wrote:
> Hi All,
> 
> Is anything known on an upgrade of the samba3 port to samba 3.0.25a?
> When the 3.0.25 port was committed, shortly after samba released
> 3.0.25a. There seems to be quite a number of problems fixed in
> 3.0.25a.

I've just sent a PR with the new port, number is not available yet from
GNATS.

I would like to stress, that after problems with the last Samba releases
I decided to delay new port for at least one week to collect feedback
from mailing lists and other sources, as well as from developers to see,
if there are no fatal problems with the release. Unfortunately, with
security updates we can't wait too long, thus 3.0.25 slipped into the
ports collection, although it possibly shouldn't.

I'm planning to ressurect net/samba3-devel port to put latest releases there,
leaving net/samba3 for proven to work releases.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.23c_2,1

[Timur I. Bakeyev]

Hi, Paul!

On Sat, Nov 04, 2006 at 03:01:22AM +0800, Paul.LKW wrote:
> Dear Samba Port Maintainer:
> I recently find a Error Message as I compile the samba3 port, the message 
> say : 
> 
> ===>  samba-3.0.23c_2,1 broken IPC and code.
> *** Error code 1
> 
> Stop in /usr/ports/net/samba3.
> 
> and I can not build the port any more.
> 
> THX for fix the port.

You should enable options which you really know what are they for :)

To get rid of this error run in the port directory:

$ make config

and uncheck "With SMBSH wrapper for UNIX commands". It doesn't work right now
and more over, seems, going to be dropped from the code.

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ports/103178: [repocopy] net/samba3 -> net/samba

[Timur I. Bakeyev]

Hi Vasil!

On Tue, Sep 12, 2006 at 10:13:36AM +0300, Vasil Dimov wrote:
> 
> >Description:
> 
> Since net/samba (version 2) got purged we can rename net/samba3 to
> net/samba.

The question of renaming Samba3 port arises again and again. This time
you actually did a tremendous work to track down all(?) ports that
somehow connected with Samba3.

Ok, let me state my opinion on this question. I belive, that such
renaming is not necessary and will be more misleading than helpful.

Samba3 is a separate product and can't really be compared to Samba2 and
Samba by the features it delivers and the way it operates. So I'd really
like it stay net/samba3 for the future, untill it'll be discontinued.

Please, also take into account that there is Samba4 coming - I have a
version of port in my private repository, but Samba4 isn't really ready
to hit the road. Possibly, with next tech preview it'll be operational
enough to go into ports. And for Samba4 I'd really like to avoid name
like net/samba-devel. That would be just plainly wrong! There is no
correlation between Samba3 and Samba4, besides intersecting set of
developers. Not to say that we may end up with net/samba4 and
net/samba4-devel for the brave souls.

Actually, I was always questioning, why we didn't have net/samba2 for
the previous version of port. But now it's a history, so I'd just stick
with the current naming schema.

Can you bring any reasons for such renaming besides the fact that it is
avalable now for usage? Cause I don't see any...

With best regards,
Timur Bakeyev.


pgpUmOGEWOQ6U.pgp
Description: PGP signature

Re: FreeBSD Port: samba-3.0.23c,1

[Timur I. Bakeyev]

Hi, Cat!

On Wed, Sep 13, 2006 at 04:02:53PM +0200, CAT wrote:
> HI,
> 
> I had last days big trouble after an update samba 3.0.22 to 3.0.23c,1.
> After the update there was noch chance to get the list of builtin groups
> 
> net groupmap list showed nothing.
> In the logfiles i found:
> 
> Sep 11 18:40:58 gateway smbd[92133]: [2006/09/11 18:40:58, 0] 
> auth/auth_util.c:create_builtin_administrators(785)
> Sep 11 18:40:58 gateway smbd[92133]:   create_builtin_administrators: Failed 
> to create Administrators
> Sep 11 18:40:58 gateway smbd[92133]: [2006/09/11 18:40:58, 0] 
> auth/auth_util.c:create_builtin_users(751)
> Sep 11 18:40:58 gateway smbd[92133]:   create_builtin_users: Failed to create 
> Users

I can't give you much advice here, but if you read WHATSNEW file from the
Samba tarball, you'll see that there were made huge changes in the way how
users and groups are processed. Text between 3.0.23c and 3.0.22 versions
notes take around 45K - so they are really big :)

In particular, pay attention on changes in:

o Improved support for local and BUILTIN groups.

I hope, it'll give you a hint, what to do next. If that fail, I'd advise
you to write a mail to samba@lists.samba.org ML and ask advice there.

With regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Samba and FAM

[Timur I. Bakeyev]

Hi Tom!

On Wed, Sep 13, 2006 at 11:42:06AM -0500, Thomas T. Veldhouse wrote:
> Scot Hetzel wrote:
> >Had a look at the samba configure script, and it doesn't have an
> >option to disable fam/gamin support.
> >
> >So your only option is to uninstall all ports that require fam/gamin.
> >Install samba w/FAM_SUPPORT off, then reinstall the ports that were
> >removed.
> >
> The catch 22 is that Courier-Imap attempts to use FAM even when it is not 
> configured to do so.  So, I have to have FAM installed.  I could get it all 
> working by deinstalling and reinstalling in the right order ... until 
> portmanager comes along and upgrades samba sometime in the future.

I don't see what portmanager have to do here. Also I don't see how Samba
port could be upgraded regarding this problem. The only solution I see
is to alter Samba configure script so it'll be possible to disable
linkage against FAM library.

Regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Samba and FAM

[Timur I. Bakeyev]

Hi guys!

Can you please explain me, what is all that fight about?

On Wed, Sep 13, 2006 at 11:38:19AM -0500, Scot Hetzel wrote:
> On 9/13/06, Scot Hetzel <[EMAIL PROTECTED]> wrote:
> >
> Had a look at the samba configure script, and it doesn't have an
> option to disable fam/gamin support.

If you take a look into configure script itself, you'll find out, that
it not only misses ability to disable FAM support, but also "smart"
enough to make a dependency on it as soon as it'll find any installed
variant of FAM library.

Unfortunatelly, this is a very common behaviour for software developed
with Linux in mind. Samba4 from this side is a nightmare of the porter
and system administrator, as it links against all the found in the
system libraries unconditionaly, without ability to disable such
linking.

> So your only option is to uninstall all ports that require fam/gamin.
> Install samba w/FAM_SUPPORT off, then reinstall the ports that were
> removed.

Should work.

> Then in pre-everything, a test for FORCE_FAM_SUPPORT:
> 
> .if defined(FORCE_FAM_SUPPORT)
> pre-everything::
>   @${ECHO} "Samba will be compiled with File Monitor Support
> (${WANT_FAM_SYSTEM})"
>  @${ECHO}
>   @${ECHO} "If this is not what you want, then you need to
> uninstall all ports depending on ${WANT_FAM_SYSTEM}.  Install Samba,
> and then reinstall all the ${WANT_FAM_SYSTEM} depending ports."
> .endif

I don't really see reasons for such an additional message. Ok, as port
may implicitly switch FAM dependency on, some sort of the message could
be helpful.

But again, I want to stress out, that Samba itself doesn't need FAM
support and this dependency is added only to reflect the fact that it'll
be linked unconditionally against FAM library if it presents in the
system and will prevent you from breaking Samba if you try to remove
such a library later.

The real solution to the problem would be to push normal knob for
configure that will let switch on/off FAM support, but I see a huge
backlog with my other patches in Samba bugzilla, so don't know, how
quick such a thing would happen. But you can give it a try :)

With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: net/samba3 (rc.d weirdness)

[Timur I. Bakeyev]

Hi, Ulrich!

On Wed, Aug 16, 2006 at 09:25:26PM +0200, Ulrich Spoerlein wrote:
> 
> The function "checkyesno" cannot handle undefined variables and will
> thus print an error. This will happen ON EVERY machine that samba3 is
> installed, but there is no samba_enable="YES/NO" line in rc.conf.
> 
> The quick fix is to alter the samba script to set a default value (to
> NO), just like almost every other port does, eg., run
> 
> $ egrep '_enable:?-"?NO' /usr/local/etc/rc.d/*
> 
> 010.pgsql.sh:postgresql_enable=${postgresql_enable:-"NO"}
> privoxy:privoxy_enable=${privoxy_enable-"NO"}
> snmpd:snmpd_enable=${snmpd_enable-"NO"}
> symon:symon_enable=${symon_enable:-"NO"}
> 
> I'll CC the maintainer ...

Thanks for pointing me out on this flaw. IIRC, when I first wrote this
script it did work ok. So, seems, something got broken since then.

I'll try to push the changes ASAP, together with some other minor fixes
to the port.

With best regards,
Timur Bakeyev.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.23,1

[Timur I. Bakeyev]

On Wed, 12 Jul 2006 13:46:52 +0200
 Daniel Dvořák <[EMAIL PROTECTED]> wrote:

Hi Timur,

thank you for your quick answer.

Could you explain, what I lose if SMBSH wrapper is not compilled to 
samba ?


I think this is important option, I tried to search what smbsh 
stands for,

but I did not find any relevant information.


Smbsh is a shell wrapper (implemented via LD_PRELOAD) that makes 
access to /smb magic - by changing into that directory and farther you 
can get access to Samba shares on other machines and files on them. 
That supposed to work implicitly to other programs, so you can for 
example, edit file on a Windows share with vi.


It's sort of userland mount_smb, but unfortunately, there are some 
problems with the implementation, so it doesn't work on FreeBSD. 
Moreover, I was told that in next version of Samba3 it'll be removed.


For more documentation you can chech smbwrapper/ directory in the 
net/samba3 source tree.


With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.23,1

[Timur I. Bakeyev]

On Wed, 12 Jul 2006 14:41:55 +0400
 Vladimir <[EMAIL PROTECTED]> wrote:


I have the same problem.
# make install
===>  samba-3.0.23,1 broken IPC and code.
*** Error code 1

Stop in /usr/ports/net/samba3.

for begin:
make clean
then
make config
and then
make install clean
and nothing work =(
You need to run 'make config' and uncheck AIO and SMBSH options. 


Please, *uncheck SMBSH* option in the configuration dialog.

Cheers,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.23,1

[Timur I. Bakeyev]

Hi, Daniel!

On Wed, 12 Jul 2006 04:28:19 +0200
 Daniel Dvořák <[EMAIL PROTECTED]> wrote:

Hello all,

I wait for samba 3.0.23 for a long time in hope that this ...
===>  samba-3.0.23,1 broken IPC and code.
*** Error code 1


You need to run 'make config' and uncheck AIO and SMBSH options. They 
are broken at the moment and, possibly, won't even compile.
Alternatively, you can just run 'make rmconfig' and compile port with 
the default settings.


With regards,
Timur.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD Port: samba-3.0.22,1 - replaced by 3.0.23

[Timur I. Bakeyev]

Hi Owen!

I'll send a PR with update in a few hours - have to write short sketch 
for UPDATING file.


With regards,
Timur Bakeyev.

On Tue, 11 Jul 2006 12:58:10 +0100 (BST)
 Owen G <[EMAIL PROTECTED]> wrote:

Hi there,


Sorry to bother you . . .  Both Samba 2 and Samba 3.0.22,1 ports for
FreeBSD are marked as uninstallable for security reasons.

I'm just putting a samba server together and would be interested in 
the

rough timescale for the new shiny 3.0.23 to be ported and made
available vis CVS.

Thanks for your volunteer efforts,

Regards,

Owen
(a newbie)







___ 
All new Yahoo! Mail "The new Interface is stunning in its simplicity 
and ease of use." - PC Magazine 
http://uk.docs.yahoo.com/nowyoucan.html


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"