Bugzilla Bug 48871

.

(29th Apr, 2004) Samba 3.0.3 Available for Download

Created an attachment (id=31035) [details]
Samba 3.0.4 ebuild

Something to work with until a 'real' ebuild is ready. works4me.

Created an attachment (id=31036) [details]
rediffed Python setup patch (place in files subdir)

*** Bug 50547 has been marked as a duplicate of this bug. ***

I'm committing a new ebuild for samba 3.0.4, along with new initscripts.
Should resolve bugs 30151, 31208, 36465, 33806, 38190, 41796, 42557, 49463.
Ldap and kerberos latest bugs in proceedings, though i should need more feedback on them...

Created an attachment (id=31248) [details]
samba-3.0.4.ebuild (obsoletes previous)

Created an attachment (id=31249) [details]
init script (to be placed in ./files dir)

Created an attachment (id=31250) [details]
init script config (to be placed in ./files dir)

Created an attachment (id=31251) [details]
samba-3.0.4.ebuild (obsoletes previous)

this one should resolve also #43019

Created an attachment (id=31253) [details]
31251: samba-3.0.4.ebuild (obsoletes previous)

'xml2' global use flag support is now active (previously, only 'xml' had
effect)

Could you add this to the ebuild:

        # to work transparently with the standard 'mount' command..
        dodir /sbin
        dosym /usr/bin/smbmount /sbin/mount.smbfs
+       dosym /usr/bin/mount.cifs /sbin/mount.cifs

        # make the smb backend symlink for cups printing support..
        if use cups; then

It will fix part of bug #46680 and make mounting cifs from fstab work.
Thanks.

Created an attachment (id=31575) [details]
samba-3.0.4.ebuild (obsoletes previous)

As per #11: added part of cifs mount support. Thanks

Created an attachment (id=31640) [details]
samba-3.0.4.ebuild (obsoletes previous)

only some minor tweaks in docs install. krb5 (heimdal/mit-krb5) works for me.
Ldap still to be tested properly. did anyone try it?

should someone commit this ?

I'm having some problems with this ebuild with ldap backend

minho sbin # pdbedit -Lv teste
Failed to load /usr/lib/upcase.dat - No such file or directory
Failed to load /usr/lib/lowcase.dat - No such file or directory
creating lame upcase table
creating lame lowcase table
Failed to load /usr/lib/valid.dat - No such file or directory
creating default valid table

Something's broken for me now...it worked for a day or two, but no longer. When
samba starts, the smbd starts OK, but nmbd and winbind report red exclamation
marks. I don't know how to get more detailed error messages, sorry. I can see
processes for both smbd and nmbd running, but /etc/init.d/samba stop says that
samba is not running. How can I find out what errors are being generated?

I am looking forward for a stable ebuild on amd64, is anyone already testing on
that platform?

Johnny

I can try to take care of this, however it will be difficult for me to find
time. I may not be able to simply because of time. I will do my best.

please wait a bit before mergin this... this ebuild as is now currently cause
samba+samba_vscan+clamav to give fatal error on startup... i'm investigating this with the samba_vscan mantainer trying some patches he sent me... 
i'll let you know

bye,
alessandro

Okay, here it is: clamav now works fine with samba (attaching new ebuild)
Thanks to Rainer Link (samba-vscan maintainer) for his help!

PS: I'm going also to open a new bug for samba-3.0.2a-rX ebuilds which have the same bug

Created an attachment (id=32005) [details]
patched samba-3.0.4 ebuild (samba-vscan support is now ok)

patched samba-3.0.4 ebuild (samba-vscan support is now ok)
obsoletes ebuild dated 2004-05-18 01:43 PST

this will become a forum :)

in reply to #16 (Glenn Morse): basically, log locations are configured via your log manager (syslog, syslog-ng, metalog, whatever). Usually most interesting notices concerning daemon<->system aspects are recorded in /var/log/messages, /var/log/debug or /var/log/syslog. Samba keeps his own internal logs under /var/log/samba/*. To 'regain control' of a not properly started init script, just do '/etc/init.d/<script> zap'. Then, after having manally stopped all daemonic :) instances, '/etc/init.d/<script> start' should behave correctly.

in reply to #15 (Ricardo Nuno): as Alessandro Pisani shows for oav support, 3.x ebuilds compile and install manually all aspects of all the packages: this will be difficult to maintain in future. I'm doing a major rewriting of compile and install sections in the ebuild to benefit of the package own install feature, along with some testing. I expect it done in this weekend

In regard to #18, I regret that I no longer have an amd64 system to test with.
This may change in a few weeks.

Gerald Carter released an important post-3.0.4 patchset which fixes these bugs:

* BUG 1315 - wbinfo -t unsuccessful on 3.0.4
* BUG 1319 - Cannot write to a share with write-list users
* BUG 1345 - Macromedia Homesite cannot connect anymore 
             after upgrade to 3.0.4

In view of that, I'm attaching an updated ebuild, and the corresponding patch which should go into ${FILESDIR}.

The patch was sourced from: http://samba.org/~jerry/patches/post-3.0.4/samba-3.0.4.patch

I should also add that I haven't tested 3.0.4 in any capacity (yet).

Created an attachment (id=32147) [details]
samba-3.0.4 + (samba-vscan | post-3.0.4 patches)

This supercedes the last supplied samba-3.0.4 ebuild (attachment 32005 [details]), adding
Gerald Carter's post-3.0.4 patchset.

Created an attachment (id=32148) [details]
Gerald Carter's post-3.0.4 patchset

This should be placed in ${FILESDIR} with regard to the ebuild supplied in
attachment 32147 [details]. Obtained from:
http://samba.org/~jerry/patches/post-3.0.4/samba-3.0.4.patch.

I've just read reports that samba_bug 1345 was also causing problems for users
of Arcserve agent and the robocopy tool from the Win2K/XP resource kits, so
that bug is obviously more irksome than it initially sounds ;)

This ebuild works fine for me on amd64 - I'm using samba as a PDC for XP
professional...

@#28
Sounds good.
How about printing? in 3.0.4 were a few options for cups newly introduced.

I am having the Problem, that printing is possible, but users can't change the properties of a printer, and they can't modify / delete their jobs. But they are authentificated correcrly.

Well, I switched to native cups, as in our Network are only 2 WIN98 Clients left.

Johnny

Created an attachment (id=32370) [details]
samba-3.0.4-r1.ebuild (libs location change, install rewritten)

proposing some fixes in compile and install sections. file hierarchy standard
is not well supported in some subcomponents, causing errors in loading libs not
located in /usr/lib or /lib (most notably, this happens with data files in
/usr/lib/samba).
all contribs in this bug are included. Revision number increased due to change
in lib position and call to samba install method

commit in cvs

Is anybody using samba 3.0.4 on a amd64, or, can we mark samba amd64 stable
without headaches?

Johnny

It is working fine for me - as already indicated...  I'm running 3.0.4-r1.