# cd /usr/ports/net/samba34
# make install clean BATCH=YES
...
Installing bin/smb_traffic_analyzer.so as
///usr/local/lib/samba34/vfs/smb_traffic_analyzer.so
Preserving old module as ///usr/local/lib/samba34/charset/CP850.so.old
Installing bin/CP850.so as ///usr/local/lib/samba34/charset/CP850
the update
mirror out and then update quickly! This one is particularly nasty.
-- WXS
Yes, that was extremely quick update. Thank you Xin Li! But at least for
samba34 I was forced to fetch tarball manually because of "Moved
permanently" messages. Some MASTER_SITE_SUBDIR updates shou
On Tue, Apr 10, 2012 at 11:35:46PM +0400, Ruslan Mahmatkhanov wrote:
> Completely offtopic, but we have a nice unauthenticated remote root
> here: http://www.samba.org/samba/security/CVE-2012-1182
It looks like the ports have just been updated. Please let the update
mirror out and then update qui
Completely offtopic, but we have a nice unauthenticated remote root
here: http://www.samba.org/samba/security/CVE-2012-1182
--
Regards,
Ruslan
Tinderboxing kills... the drives.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailma
On 4/10/2012 06:14, Da Rock wrote:
> On 04/10/12 13:14, Mel Flynn wrote:
>> On 4/10/2012 02:26, Da Rock wrote:
>>
>>> So what should the patch look like? Am I correct in my understanding of
>>> the BUILD_DEPENDS, or have I chased a goose on that one?
>> I'd like to divert your attention to the libn
uot; is useless. I checked, and I have
exactly two lines that reference perl:
# added by use.perl 2012-03-08 19:17:29
PERL_VERSION=5.14.2
Are these the "usual perl stuff" you are referencing? If so, then your
"make.conf" file consists of only three lines; two if you don't cou
On 04/10/12 18:06, Timur I. Bakeyev wrote:
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 o
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
case from
pointyhat, since the builds of samba-3.x worked fine:
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-
> http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log
>>
>> http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log
>>
>> http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log
>
> Hmmm. You
On 04/10/12 13:14, Mel Flynn wrote:
On 4/10/2012 02:26, Da Rock wrote:
So what should the patch look like? Am I correct in my understanding of
the BUILD_DEPENDS, or have I chased a goose on that one?
I'd like to divert your attention to the libnet source directory in
samba distribution. It's b
On 4/10/2012 02:26, Da Rock wrote:
> So what should the patch look like? Am I correct in my understanding of
> the BUILD_DEPENDS, or have I chased a goose on that one?
I'd like to divert your attention to the libnet source directory in
samba distribution. It's built by default and integrated into
rg/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log
Hmmm. You're right.
I can narrow it down to the SWAT or AIO option (most likely g
rocedure. However, you might first want to look into what was
different in your case from pointyhat, since the builds of samba-3.x worked
fine:
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.
On 04/08/12 09:59, Da Rock wrote:
On 04/08/12 00:02, Chris Rees wrote:
On 7 April 2012 13:51, Da
Rock wrote:
On 04/06/12 13:20, Timur I. Bakeyev wrote:
Hi!
Can you show the build output? Port should't directly dipend from
anything like this.
Sorry, it was on a clients system and I couldn't g
On 04/08/12 00:02, Chris Rees wrote:
On 7 April 2012 13:51, Da Rock wrote:
On 04/06/12 13:20, Timur I. Bakeyev wrote:
Hi!
Can you show the build output? Port should't directly dipend from
anything like this.
Sorry, it was on a clients system and I couldn't get the info across. I can
only say
On 7 April 2012 13:51, Da Rock wrote:
> On 04/06/12 13:20, Timur I. Bakeyev wrote:
>>
>> Hi!
>>
>> Can you show the build output? Port should't directly dipend from
>> anything like this.
>
> Sorry, it was on a clients system and I couldn't get the info across. I can
> only say for sure that insta
On 04/06/12 13:20, Timur I. Bakeyev wrote:
Hi!
Can you show the build output? Port should't directly dipend from
anything like this.
Sorry, it was on a clients system and I couldn't get the info across. I
can only say for sure that installing libnet fixed the issue.
The build error was an und
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
__
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
Hi!
> I've just compiled samba35 from ports with the extra config settings
> ADS/SWAT/DNSUPDATE, no default settings were removed.
I looked at the port and
http://www.linuxhacker.at/bugs/all/hoary-samba-idmap-rid.so-error
Maybe this works: do a
make config
and add
with experimental modules
Hello.
I've just compiled samba35 from ports with the extra config settings
ADS/SWAT/DNSUPDATE, no default settings were removed.
After joining the samba as a stand alone server in a windows AD.
settings in smb.conf are
idmap backend = rid:domain=15000-2(edit: idmap_rid:... is
deprecat
ну хоть кто-то наконец-то обратил на это внимание!
___
Well at least someone finally noticed it!
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/net-samba35-build-fails-with-samba34-libsmbclient-installed-tp4685619p4685889.html
Sent from the freebsd-ports
on 10/08/2011 15:21 Andriy Gapon said the following:
>
> net/samba35 build fails with samba34-libsmbclient installed.
Clarification: and samba34-libsmbclient is built with WITH_NETAPI.
> This happens because of the following lines in source3/Makefile:
> LIBNETAPI=bin
net/samba35 build fails with samba34-libsmbclient installed.
This happens because of the following lines in source3/Makefile:
LIBNETAPI=bin/libnetapi.a
LIBNETAPI_LIBS= -lnetapi
...
bin/net: $(BINARY_PREREQS) $(NET_OBJ) $(LIBTALLOC) $(LIBTDB) $(LIBWBCLIENT)
$(LIBNETAPI)
@echo Linking
the sysutils/libsunacl library by Edward
Tomasz Napierala(trasz). This support haven't been tested thoroughly,
so try it on your own risk.
This port reverted back to the pre- net/samba34 layout of the
directories and now they are again $PREFIX/etc/samba, /var/run/samba,
/var/log/samba,
3.4.9 (in ports) is vulnerable.
I see 3.4.13 upstream...
Any plan to upgrade or should we move to 3.5?
bye & Thanks
av.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
I upgraded to samba34 port. The current version is:
samba34-3.4.9 A free SMB and CIFS client and server for UNIX
in my smbd logs I am seeing these strange errors that I cannot fix.
Anyone have a clue how to fix it?
[2010/12/15 09:34:17,2] lib/interface.c:340(add_interface) added
_ad_map_from_alias':
winbindd/idmap_ad.c:1064: error: incompatible types in assignment
winbindd/idmap_ad.c:1071: warning: assignment makes pointer from integer
without a cast
The following command failed:
cc -O2 -pipe -fno-strict-aliasing -I.
-I/usr/ports/net/samba34/work/samba-3.4.8/source3
Hi,
I read that samba3.4 includes some samba4's features.
To enable this feature someone told me that i've to compile the source
with the ' –enable-merged-build'.
Does exist something like this in the port?
or
do you know something about the Windows Vista/7 policies management with
samba3.
Is there any word on what this might be ? or does anyone else know where
to turn this off... ?
Thanks.
On Mon, 8 Feb 2010 13:01, jhell@ wrote:
On Mon, 8 Feb 2010 11:38, jhell@ wrote:
Some how either WITH_MAX_DEBUG is getting set or somewhere in the sources
is overriding and turning on --w
ord? i realized
that this is a necessary step when upgrading from samba 33 to
samba 34 (when using ldapsam as passdb backend)
best regards,
šreinhard
Hello.
Yes, I did, but the problem went away, when I removed all old
/var/db/samba files and folders. Although samba34 created
/var/db/samba34, th
Am Mon, 08 Feb 2010 11:43:12 +
schrieb "O. Hartmann" :
> I have no idea what's going wrong. The authentication is done via
> LDAP. Using samab33 works without problem.
did you use "smbpasswd -w ..." to store the ldap password? i realized
that this is a necessary step when upgrading from samba
On 02/08/10 16:03, jhell wrote:
On Mon, 8 Feb 2010 06:43, ohartman@ wrote:
After upgrading from samba33 to samba34 from most recent ports, no
Windows_XP and Windows_7 client is capable of connecting to the samba
server anymore! I use the same config as before, did a testparm (it
shows this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 8 Feb 2010 11:38, jhell@ wrote:
PGP Command Output
gpg: Signature made Mon Feb 8 11:38:32 2010 EST using RSA key ID 89D8547E
gpg: Good signature from "jhell "
--- Begin PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Why if samba, samba33, samba34 can not be installed together does samba34
decide to use var/db/samba34 var/log/samba34 & local/etc/samba34 when
samba33 just used samba without the version suffix ?
Curious question because now if I wan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Some how either WITH_MAX_DEBUG is getting set or somewhere in the sources
is overriding and turning on --with-profiling-data by default. I have not
worked out where this is at or even if its a ports problem. I have
attached the following patch
On Mon, 8 Feb 2010 06:43, ohartman@ wrote:
After upgrading from samba33 to samba34 from most recent ports, no Windows_XP
and Windows_7 client is capable of connecting to the samba server anymore! I
use the same config as before, did a testparm (it shows this ahaead:
Load smb config files from
After upgrading from samba33 to samba34 from most recent ports, no
Windows_XP and Windows_7 client is capable of connecting to the samba
server anymore! I use the same config as before, did a testparm (it
shows this ahaead:
Load smb config files from /usr/local/etc/smb.conf
max_open_files
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.
hould 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
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, t
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 op
On 02/06/10 16:24, Timur I. Bakeyev wrote:
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
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.
>
>
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
Trying to compile SAMAB 3.4 on FreeBSD 8.0/amd64 STABLE ends up in the
following error and it seems a bit sticky.
Are there any solutions? Thanks,
Regards,
Oliver
===> Building for samba34-3.4.5
cd /usr/ports/net/samba34/work/samba-3.4.5/source3 && make pch
rm -f /usr/ports/net/s
47 matches
Mail list logo
