On Thu, 27 Jan 2011 17:13:13 +
Tom Evans articulated:
> Hi all
>
> I was updating ports one of my boxes last night, and it informed me
> that net/samba3 is no more. Unlike usual, there was no
> /usr/ports/UPDATING entry to tell nubbins like me how to cope with
>
Hi all
I was updating ports one of my boxes last night, and it informed me
that net/samba3 is no more. Unlike usual, there was no
/usr/ports/UPDATING entry to tell nubbins like me how to cope with
this missing port.
There is still net/samba34 and net/samba35. I tried to get portupgrade
to
Regards,
After update from autoconf-2.62 to 2.67, I can't install samba3x ports
on FBSD6 machines, compilation failed with:
(I've tried other versions of samba3/31/32/33/34, problem is the same.
Downgrade of autoconf to version 2.62 helped. Only FBSD6 is affected,
FBSD7
I'm wondering why it installs samba 3.0 instead of the latest
release in the samba 3 branch like other ports do.
Regards
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and i
c/samba
> > EXAMPLESDIR=/usr/local/share/examples/samba WWWDIR=/usr/local/www/samba
> > ETCDIR=/usr/local/etc/samba RC_SUBR=/etc/rc.subr
> >
> That looks normal.
>
> Try:
>
> cd /usr/ports/net/samba3
> make clean
> make patch
> make apply-slist
>
>
ADIR=/usr/local/share/samba
> DOCSDIR=/usr/local/share/doc/samba
> EXAMPLESDIR=/usr/local/share/examples/samba WWWDIR=/usr/local/www/samba
> ETCDIR=/usr/local/etc/samba RC_SUBR=/etc/rc.subr
>
That looks normal.
Try:
cd /usr/ports/net/samba3
make clean
make patch
make apply-slist
T
WINBIND%%#: not found
> >> > %%WINBIND%%#winbindd_enable=YES: not found
> >> > .: Can't open %%RC_SUBR%%: No such file or directory
> >> >
> >>
> >> The %%WINBIND%% and %%RC_SUBR%% are supposed to be replaced with real
> >> val
art 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
>> >
>>
>>
is 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
> >
>
> The %%WINBIND%% and %%RC_SUBR%% are supposed to be replace
>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
>> .: C
: not found
> .: Can't open %%RC_SUBR%%: No such file or directory
>
The %%WINBIND%% and %%RC_SUBR%% are supposed to be replaced with real
values when the net/samba3 port is installed.
How did you install the samba.sh file?
Scot
___
freeb
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 %%R
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
This is the rc.conf of the jail:
# cat
force workaround was to manually add
'lib/samba/vfs/recycle.so' to the '/net/samba3/pkg-plist' file.
I know this is not the proper thing to do, but it works for getting a
package built. I would have preferred a tweak to the Makefile that
would
work for everyone, but I'm afraid
in the package.
> I found a brute force workaround was to manually add
> 'lib/samba/vfs/recycle.so' to the '/net/samba3/pkg-plist' file.
> I know this is not the proper thing to do, but it works for getting a
> package built. I would have preferred a tweak to the M
tory?
Scot
Scot,
The problem was not getting the VFS modules compiled, but rather
getting them installed.
I found a brute force workaround was to manually add 'lib/samba/vfs/
recycle.so' to the '/net/samba3/pkg-plist' file.
I know this is not the proper thing to
On 9/25/08, Erik Van Benschoten <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> I have been looking into setting up a network recycle bin under v3.0.32 of
> Samba. The default configuration does not install/package any of the VFS
> modules from the looks of it. The man pages are there for them, but n
Greetings,
I have been looking into setting up a network recycle bin under
v3.0.32 of Samba. The default configuration does not install/package
any of the VFS modules from the looks of it. The man pages are there
for them, but not the actual binaries. After looking at the Makefile I
trie
solve this?
Tim
===> Building for samba-3.0.28,1
cd /usr/ports/net/samba3/work/samba-3.0.28/source && make pch
rm -f /usr/ports/net/samba3/work/samba-3.0.28/source/include/includes.h.gch
cc -I. -I/usr/ports/net/samba3/work/samba-3.0.28/source -O2
-fn
Uwe Laverenz wrote:
> I know. I'm sorry if you got the impression I wouldn't appreciate your
> work. I guess my English is just too clumsy to be precise enough
> sometimes.
Fair enough. :) Your english is great, and I don't even speak german,
never mind writing it, so I'm not in a position to cri
Hi
I have figured out what went wrong.
I have previously complied samba without ldap support.
There are tdb files in /var/db/samba.
I have just uninstall samba and
remove all tdb files (this instruction was given when run make
deinstall in the samba3 ports, but I didn't follow it before).
On Wed, Jun 06, 2007 at 10:14:56AM -0700, Doug Barton wrote:
> Well boo hoo! If you're smart enough to be useful in testing new
> versions, you're smart enough to modify the port yourself, or build
> the software without the port.
Yes, I guess that's true.
> Sorry to be so flippant, but this who
Uwe Laverenz wrote:
> On Tue, Jun 05, 2007 at 03:54:25PM -0700, Doug Barton wrote:
>
>> I think it's very reasonable, and well in keeping with FreeBSD
>> tradition, to delay upgrading to a new release of ported software
>> until the maintainer is convinced that it's safe to do so. I have
>
> Yes,
Doug Barton wrote:
Timur I. Bakeyev wrote:
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 think it's very reasonable, and we
On Tue, Jun 05, 2007 at 03:54:25PM -0700, Doug Barton wrote:
> I think it's very reasonable, and well in keeping with FreeBSD
> tradition, to delay upgrading to a new release of ported software
> until the maintainer is convinced that it's safe to do so. I have
Yes, but on the other hand it is th
Timur I. Bakeyev wrote:
> 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 think it's very reasonable, and well i
On Tue, 2007-06-05 at 14:14 +0200, Spil Oss wrote:
> On 05/06/07, Timur I. Bakeyev <[EMAIL PROTECTED]> wrote:
> > On Tue, Jun 05, 2007 at 09:31:57AM +0200, Spil Oss wrote:
> > > Is anything known on an upgrade of the samba3 port to samba 3.0.25a?
> > > When the 3
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 Secu
owever 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
On 05/06/07, Timur I. Bakeyev <[EMAIL PROTECTED]> wrote:
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.2
Hi
I have tried to setup freebsd (with samba3 ports), backend is openldap
with smbldap-tools.
After a windows client joined the domain, I tried to right click a
folder to set Security/permission.
The windows client has a popup windows which display:
The program cannot open the required dialog
ting here).
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
On 2007.06.05 10:22:44 +0200, 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 fata
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
>
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
&
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.
Kind regards,
Spil.
___
freebsd
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vizion
> Sent: Saturday, March 24, 2007 9:52 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: samba3 compile failure
>
>
&
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vizion
> Sent: Saturday, March 24, 2007 9:23 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: samba3 compile fail
Vizion wrote:
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] On Behalf Of Vizion
>> Sent: Friday, March 23, 2007 3:37 AM
>> To: [EMAIL PROTECTED]
>> Subject: samba3 compile failure
>>
>> Trying to
Vizion wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vizion
Sent: Friday, March 23, 2007 3:37 AM
To: [EMAIL PROTECTED]
Subject: samba3 compile failure
Trying to compile samba...
Is up with my kerberos?
If so I do not know how to fix it
Begin forwarded message:
From: Garrett Cooper <[EMAIL PROTECTED]>
Date: March 24, 2007 1:29:57 AM PDT
To: freebsd-questions@freebsd.org
Subject: Re: samba3 compile failure
On Mar 23, 2007, at 3:51 PM, Vizion wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED]
> Sent: Friday, March 23, 2007 11:29 AM
> To: freebsd-ports@freebsd.org
> Cc: freebsd-questions@freebsd.org
> Subject: Re: samba3 compile failure
On Fri, 23 Mar 2007, Vizion wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vizion
Sent: Friday, March 23, 2007 8:15 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: samba3 compile failure
Vizion wrote:
I am trying to compile
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vizion
> Sent: Friday, March 23, 2007 8:15 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: samba3 compile failure
>
> Vizion wrote:
> > I am tryin
i.so: undefined reference to `krb5_encrypt_ivec'
> /usr/lib/libgssapi.so: undefined reference to `krb5_storage_emem'
> /usr/lib/libgssapi.so: undefined reference to `krb5_store_data'
> /usr/lib/libgssapi.so: undefined reference to
> `krb5_auth_con_setremoteseqnumber'
>
Vizion wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Vizion
Sent: Friday, March 23, 2007 3:37 AM
To: [EMAIL PROTECTED]
Subject: samba3 compile failure
Trying to compile samba...
Is up with my kerberos?
If so I do not know how to fix it
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Vizion
> Sent: Friday, March 23, 2007 3:37 AM
> To: [EMAIL PROTECTED]
> Subject: samba3 compile failure
>
> Trying to compile samba...
> Is up with my kerberos?
> If
nce to `krb5_principal_get_realm'
/usr/lib/libgssapi.so: undefined reference to `krb5_set_error_string'
/usr/lib/libgssapi.so: undefined reference to `krb5_make_principal'
/usr/lib/libgssapi.so: undefined reference to `krb5_store_keyblock'
*** Error code 1
Stop in /us
On Tue, Oct 24, 2006 at 01:35:51PM -0600, Jason Gretz wrote:
> Hello, I installed samba 3 through sysinstall and it is up and running,
> where is the .conf file I have to edit? Im a little lost.
There are lots of examples in /usr/local/share/examples/samba/; copy
smb.conf.default from that direct
Hello, I installed samba 3 through sysinstall and it is up and running,
where is the .conf file I have to edit? Im a little lost.
-Thanks,
Jason
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.408 / Virus Database: 268.13.11/494 - Release Date: 10/
On 9/14/06, [LoN]Kamikaze <[EMAIL PROTECTED]> wrote:
It strikes me that if ports were named net/samba3 and net/samba4 people
would simply assume that net/samba4 is their way to go.
Maybe a meta port net/samba that always points to the latest stable
release would solve that.
We'v
Timur I. Bakeyev wrote:
> 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
On Thu, Sep 14, 2006 at 02:26:59AM +0200, Timur I. Bakeyev wrote:
> 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/s
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
Greetings!
I have a samba3 installation acting as a domain member server, which
is joined to a samba3 PDC on the same subnet.
If I attempt to restart samba with /usr/local/etc/rc.d/samba restart,
I get the following when I attempt to browse it:
[EMAIL PROTECTED]:~% sudo /usr/local/etc/rc.d
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=&q
ngs when
> called during the rc rotations.
>
> If there are any references to samba in /etc/rc.conf other than
> samba_enable="YES" remove
> them. It should work fine after that.
No, it does not work fine, as the samba rcNG script is triggering a flaw
in the rcNG syste
22:17:48 bsd root: /etc/rc: WARNING: $samba_enable is not set
properly - see rc.conf(5).
I ran into this too. First, net/samba is an old 2* version which should
not be used. Instead use net/samba3 cvsup'd to 3.0.2.3.
Next, remove anything having to do with samba, smbd, nmbd from /e
Mike Jakubik wrote:
The startup script for Samba states:
[...]
However when setting samba_enable="YES" in rc.conf, the restart option
does not function correctly, as it only restarts smbd. If we instead set
the alternative of nmbd_enable="YES" and smbd_enable="YES", we get the
following warni
The startup script for Samba states:
---
#
# Add the following lines to /etc/rc.conf to enable samba:
#
#samba_enable="YES"
#
# or, for fine grain control
#
#nmbd_enable="YES"
#smbd_enable="YES"
#
---
However when setting samba_enable="YES" in rc.conf, the restart option
does not function corre
Since updating the port today from the previous version, I've not been
able to connect to any of my network smb shares... windows hangs as does
smbclient.
I'm researching the problem now, but figured I would give a heads-up
about it.
Anyone else seeing this.
This is on FreeBSD-6.1-STABLE. No
Quoting RW <[EMAIL PROTECTED]> (from Wed, 21 Jun 2006
22:49:30 +0100):
On Wednesday 21 June 2006 20:24, Alexander Leidinger wrote:
Quoting Andriy Gapon <[EMAIL PROTECTED]> (Wed, 21 Jun 2006 21:15:17 +0300):
> It still would be very nice to introduce a concept of "immediate
> dependencies" to
62 matches
Mail list logo
