PGP SIGNED MESSAGE
Hash: SHA1
Done with Fish.
-- John Laroche (Adaptation)
Release Announcements
This is the latest stable release of Samba. This is the version
that production Samba servers should be running for all current
bug-fixes. Please read the following important changes in this
release.
Common bugs fixed in 3.0.21 include:
o Missing groups in a user's token when logging in via kerberos
o Incompatibilities with newer MS Windows hotfixes and
embedded S platforms
o Portability and crash bugs.
o Performance issues in winbindd.
New features introduced in Samba 3.0.21 include:
o Complete NTLMv2 support by consolidating authentication
mechanism used at the CIFS and RPC layers.
o The capability to manage Unix services using the Win32
Service Control API.
o The capability to view external Unix log files via the
Microsoft Event Viewer.
o New libmsrpc share library for application developers.
o Rewrite of CIFS oplock implementation.
o Performance Counter external daemon.
o Winbindd auto-detection query methods when communicating with
a domain controller.
o The ability to enumerate long share names in libsmbclient
applications.
Download Details
The uncompressed tarball and patch files have been signed
using GnuPG (ID 157BC95E). The source code can be
downloaded from:
The release notes are available online at:
Binary packages are available at
Code, Bugs, Responsibility.
(https://bugzilla.samba.org/)
The Samba Team
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
vSj04v58QT0zsSNhK=
=9JAS
PGP SIGNATURE

Hi Jerry ,
are there any special config parameters needed ( in smb.conf)
for this feature

o The capability to manage Unix services using the Win32
Service Control API.
Best Regards

and merry x-mas

Gerald (Jerry) Carter schrieb:

PGP SIGNED MESSAGE
>Hash: SHA1
>
>
> Done with Fish.
> -- John Laroche (Adaptation)
>
>Release Announcements

>
>This is the latest stable release of Samba. This is the version
>that production Samba servers should be running for all current
>bug-fixes. Please read the following important changes in this
>release.
>
>Common bugs fixed in 3.0.21 include:
>
o Missing groups in a user's token when logging in via kerberos
o Incompatibilities with newer MS Windows hotfixes and
embedded S platforms
o Portability and crash bugs.
o Performance issues in winbindd.
>
>New features introduced in Samba 3.0.21 include:
>
o Complete NTLMv2 support by consolidating authentication
mechanism used at the CIFS and RPC layers.
o The capability to manage Unix services using the Win32
Service Control API.
o The capability to view external Unix log files via the
Microsoft Event Viewer.
o New libmsrpc share library for application developers.
o Rewrite of CIFS oplock implementation.
o Performance Counter external daemon.
o Winbindd auto-detection query methods when communicating with
a domain controller.
o The ability to enumerate long share names in libsmbclient
applications.


>Download Details

>
>The uncompressed tarball and patch files have been signed
>using GnuPG (ID 157BC95E). The source code can be
>downloaded from:
>
>
>
>The release notes are available online at:
>
>
>
>Binary packages are available at
>
>
>
Code, Bugs, Responsibility.
>(https://bugzilla.samba.org/)
>
>
>The Samba Team
PGP SIGNATURE
>Version: GnuPG v1.4.2 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>
>vSj04v58QT0zsSNhK=
>=9JAS
PGP SIGNATURE

12/21/05, Gerald (Jerry) Carter <jerry (AT) samba (DOT) orgwrote:
Binary packages are available at

Thankyou so much :-)

but

deb sarge samba

for Sarge mentioned in

does not seem to work :-(

Details

root@backupsrv:~# cat /etc/apt/sources.list |grep XX
deb sarge samba
root@backupsrv:~# apt-get updat
E: Invalid operation updat
root@backupsrv:~# apt-get update
Err http://XX.samba.org sarge/samba Packages
503 Service Unavailable
Ign http://XX.samba.org sarge/samba Release
Hit http://ftp.debian.org stable/main Packages
Hit http://security.debian.org stable/updates/main Packages
Hit http://ftp.debian.org stable/main Release
Hit http://security.debian.org stable/updates/main Release
Hit http://ftp.debian.org stable/main Sources
Hit http://ftp.debian.org stable/main Release
Failed to fetch

503 Service Unavailable
Reading Package Lists Done
W: Couldn't stat source package list http://XX.samba.org sarge/samba
Packages (/%)
- stat (2 No such file or directory)
W: You may want to run apt-get update to correct these problems
E: Some index files failed to download, they have been ignored, or old
ones used instead.
root@backupsrv:~#

What could have possibly gone wrong?

Thanks again

kind Regards

Siju

Ps!!! Sorry!!! I just did not replace XX :-(
So sorry for that!!
12/21/05, Siju George <sgeorge.ml (AT) gmail (DOT) comwrote:
deb sarge samba
for Sarge mentioned in
does not seem to work :-(

Robert Schetterer wrote:

Hi Jerry ,
are there any special config parameters needed ( in smb.conf)
for this feature

o The capability to manage Unix services using the Win32
Service Control API.
Best Regards

and merry x-mas

Yes you have to tell samba which services you want to make available and
how to do the necessary actions (start, stop, restart, etc.). I believe
the option you want is "svcctl list"

In smb.conf you do:

svcctl list = postfix httpd

Then create a svcctl directory in samba's $(libdir) and inside there you
create symbolic links to the necessary init scripts (you could make it a
symbolic link to anything really, just as long as wherever you make the
link to knows how to do the actions).

Dennis B. Hopp schrieb:

Robert Schetterer wrote:
>
>Hi Jerry ,
>are there any special config parameters needed ( in smb.conf)
>for this feature
>>
>o The capability to manage Unix services using the Win32
>Service Control API.
>Best Regards
>>
>and merry x-mas
>
>
>
Yes you have to tell samba which services you want to make available
and how to do the necessary actions (start, stop, restart, etc.). I
believe the option you want is "svcctl list"

In smb.conf you do:

svcctl list = postfix httpd

Then create a svcctl directory in samba's $(libdir) and inside there
you create symbolic links to the necessary init scripts (you could
make it a symbolic link to anything really, just as long as wherever
you make the link to knows how to do the actions).

Hi,
thx for the Info, is it allready in the current faqs?
Regards

Robert Schetterer wrote:

Dennis B. Hopp schrieb:
>
>Robert Schetterer wrote:
>>
Hi Jerry ,
are there any special config parameters needed ( in smb.conf)
for this feature

o The capability to manage Unix services using the Win32
Service Control API.
Best Regards

and merry x-mas
>>
>>
>>
>>
>Yes you have to tell samba which services you want to make available
>and how to do the necessary actions (start, stop, restart, etc.). I
>believe the option you want is "svcctl list"
>>
>In smb.conf you do:
>>
>svcctl list = postfix httpd
>>
>Then create a svcctl directory in samba's $(libdir) and inside there
>you create symbolic links to the necessary init scripts (you could
>make it a symbolic link to anything really, just as long as wherever
>you make the link to knows how to do the actions).
>>
>
>>
Hi,
thx for the Info, is it allready in the current faqs?
Regards

The man page on samba.org (
) is
already update so I imagine the one in the release download is.

Dennis B. Hopp schrieb:

Robert Schetterer wrote:
>
>Dennis B. Hopp schrieb:
>>
Robert Schetterer wrote:

Hi Jerry ,
are there any special config parameters needed ( in smb.conf)
for this feature

o The capability to manage Unix services using the Win32
Service Control API.
Best Regards

and merry x-mas

Yes you have to tell samba which services you want to make available
and how to do the necessary actions (start, stop, restart, etc.). I
believe the option you want is "svcctl list"

In smb.conf you do:

svcctl list = postfix httpd

Then create a svcctl directory in samba's $(libdir) and inside there
you create symbolic links to the necessary init scripts (you could
make it a symbolic link to anything really, just as long as wherever
you make the link to knows how to do the actions).


>Hi,
>thx for the Info, is it allready in the current faqs?
>Regards
>>
>
The man page on samba.org (
) is
already update so I imagine the one in the release download is.

Wow i see just another killing feature which i will test soon
but i am not clear what $(libdir) means , does it mean i.e
/var/lib/samba ( usally the standart path for profiles etc ) ?
Regards

PGP SIGNED MESSAGE
Hash: SHA1

Robert Schetterer wrote:

thx for the Info, is it allready in the current faqs?

I thought I wrote a howto for this but I can't find it now.
In any case, the info has not been integrated into the docs
yet. Dennis' description pretty much covers it all.
Screenshots of a working setup are at
http://www.samba.org/~jerry/screenshots/

cheers, jerry
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

BTuVH9aR4b5G2nFgWIt2Knk=
=K9zT
PGP SIGNATURE

PGP SIGNED MESSAGE
Hash: SHA1

Robert Schetterer wrote:

Wow i see just another killing feature which i will test soon
but i am not clear what $(libdir) means , does it mean i.e
/var/lib/samba ( usally the standart path for profiles etc ) ?
Regards

No. That's the $(lockdir). Run `smbd -b | grep -i LIBDIR` to find
$(libdir) for your installation.

cheers, jerry

Alleviating the pain of Windows(tm) http://www.samba.org
Centeris http://www.centeris.com
"There's an anonymous coward in all of us."
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

cmxc/zNPqK6z7K/t+TU72EE=
=SLrY
PGP SIGNATURE

Gerald (Jerry) Carter schrieb:

PGP SIGNED MESSAGE
>Hash: SHA1
>
>Robert Schetterer wrote:
>

>
>>Wow i see just another killing feature which i will test soon
>>but i am not clear what $(libdir) means , does it mean i.e
>>/var/lib/samba ( usally the standart path for profiles etc ) ?
>>Regards
>
>>
>
>No. That's the $(lockdir). Run `smbd -b | grep -i LIBDIR` to find
>$(libdir) for your installation.
>
>
>
>
>
>cheers, jerry
>
>Alleviating the pain of Windows(tm) http://www.samba.org
>Centeris http://www.centeris.com
>"There's an anonymous coward in all of us."
PGP SIGNATURE
>Version: GnuPG v1.4.2 (GNU/Linux)
>Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
>
>cmxc/zNPqK6z7K/t+TU72EE=
>=SLrY
PGP SIGNATURE

Hi,
works ( path for suse 9.3)
pdc:~ # smbd -b | grep -i LIBDIR
LIBDIR: /usr/lib/samba
pdc:~ #
thx to make all this stuff clear
Regards

Gerald (Jerry) Carter wrote:

o Rewrite of CIFS oplock implementation.

Specifically on the oplock topic:

Does the fact that the Samba team invested in such a rewrite mean that it is time to reevaluate utilizing oplock capabilities with applications that suggest running with them disabled? Desktop
database applications are first in my mind - the Paradox's and Access's of the world. Also accounting packages that share a database file on the server. Peachtree using a Btrieve database on the server.

was this investment in R&D necessary for all of the non database oplock usage, and databases should not attempt to use oplocks?

Are the capabilities considered cross platform, or were specific platforms targeted - such as Windows 2000 and Linux, but not Windows 98 or something bazaar like that?

Wed, Dec 21, 2005 at 09:51:57AM -0500, Michael Lueck wrote:
Gerald (Jerry) Carter wrote:

o Rewrite of CIFS oplock implementation.

Specifically on the oplock topic:

Does the fact that the Samba team invested in such a rewrite mean that it
is time to reevaluate utilizing oplock capabilities with applications that
suggest running with them disabled? Desktop database applications are first
in my mind - the Paradox's and Access's of the world. Also accounting
packages that share a database file on the server. Peachtree using a
Btrieve database on the server.

was this investment in R&D necessary for all of the non database oplock
usage, and databases should not attempt to use oplocks?

Are the capabilities considered cross platform, or were specific platforms
targeted - such as Windows 2000 and Linux, but not Windows 98 or
something bazaar like that?

The rewrite was done by Volker to make some more operations asynchronous,
in preparation for the fully clustered Samba code (with a distributed filesystem
backend) that is to come. It doesn't change the functionality (other than
I think we pass a few more of the "difficult" Win2K3 compatible tests).

Using oplocks with a backend database application is just a risky business
as everything has to work right. If you have perfect Windows clients (is
that an oxymoron ? :-) and a non-lossy network then it should be ok. But
as always, your milage may vary (and you should check what the DB vendor
recommends - Samba will be no different from a Windows server in this
respect).

Jeremy.

Jeremy Allison wrote:
But
as always, your milage may vary (and you should check what the DB vendor
recommends - Samba will be no different from a Windows server in this
respect).
Sounds like we best leave settings as-is, they stay disabled. Thanks for elaborating.

12/21/05, Gerald (Jerry) Carter <jerry (AT) samba (DOT) orgwrote:
PGP SIGNED MESSAGE
Hash: SHA1

Robert Schetterer wrote:

thx for the Info, is it allready in the current faqs?

I thought I wrote a howto for this but I can't find it now.
In any case, the info has not been integrated into the docs
yet. Dennis' description pretty much covers it all.
Screenshots of a working setup are at
http://www.samba.org/~jerry/screenshots/

This is exciting :-)))))

For this
http://www.samba.org/~
to work, Should they be on the same domain? I mean I tried to connect
from My Windows 2003 SBS Event Viewer to a Samba Server on a different
workgroup and it did not succeed :-(

What could have gone wrong?

Thankyou so much

Kind Regards

Siju

PGP SIGNED MESSAGE
Hash: SHA1

Siju George wrote:

This is exciting :-)))))

For this
http://www.samba.org/~
to work, Should they be on the same domain? I mean I tried to connect
from My Windows 2003 SBS Event Viewer to a Samba Server on a different
workgroup and it did not succeed :-(

What could have gone wrong?

Access to the eventlog is controlled by the file system permissions
on /var/lib/samba/eventlog/<logname>.tdb. The default is rw- for
root only.

cheers, jerry
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

7x1/Cj/9uZNjpbZL8T1e4Fc=
=lyYA
PGP SIGNATURE

Hi Jerry,
Great news!!! Many thanks!

Just a note, the makerpms.sh patch for building in RHEL4 (CS4) did
not make it into 3.0.21

In case someone wants to build a rpm in these distros, use this micro patch:
makerpms.sh.ori 2005-12-21 21:33:35.000000000 -0300
makerpms.sh 2005-12-21 21:29:35.000000000 -0300
@@ -46,7 +46,7 @@
## now catch the right command to build an RPM (defaults ro 'rpm'
##
case $RPMVER in
- 4.[12]*)
+ 4.[123]*)
RPM="rpmbuild"
;;
esac

HTH,
Regards

Gerald (Jerry) Carter wrote:
PGP SIGNED MESSAGE
Hash: SHA1

Robert Schetterer wrote:


>>thx for the Info, is it allready in the current faqs?

I thought I wrote a howto for this but I can't find it now.
In any case, the info has not been integrated into the docs
yet. Dennis' description pretty much covers it all.
Screenshots of a working setup are at
http://www.samba.org/~jerry/screenshots/

Awesome! what's next (or whats left for samba3)?

Tuesday 20 December 2005 22:45, Gerald (Jerry) Carter wrote:

Done with Fish.
-- John Laroche (Adaptation)

Release Announcements

This is the latest stable release of Samba. This is the version
that production Samba servers should be running for all current
bug-fixes. Please read the following important changes in this
release.

Common bugs fixed in 3.0.21 include:

o Missing groups in a user's token when logging in via kerberos
o Incompatibilities with newer MS Windows hotfixes and
embedded S platforms
o Portability and crash bugs.
o Performance issues in winbindd.

New features introduced in Samba 3.0.21 include:

o Complete NTLMv2 support by consolidating authentication
mechanism used at the CIFS and RPC layers.
o The capability to manage Unix services using the Win32
Service Control API.
o The capability to view external Unix log files via the
Microsoft Event Viewer.
o New libmsrpc share library for application developers.
o Rewrite of CIFS oplock implementation.
o Performance Counter external daemon.
o Winbindd auto-detection query methods when communicating with
a domain controller.
o The ability to enumerate long share names in libsmbclient
applications.

Download Details

The uncompressed tarball and patch files have been signed
using GnuPG (ID 157BC95E). The source code can be
downloaded from:

The release notes are available online at:

Binary packages are available at

Packages for Mandrake 10.1 (i586), Mandriva 2005le (i586 and x86_64) and
Mandriva 2006 (i586 and x86_64) are available from
. These packages are
not officially supported by Mandriva (and I haven't been able to do much
testing yet), so please send any feedback to me directly.

Regards,
Buchan

PGP SIGNED MESSAGE
Hash: SHA1

Schulze L. wrote:
Hi Jerry,
Great news!!! Many thanks!

Just a note, the makerpms.sh patch for building in RHEL4 (CS4) did
not make it into 3.0.21

I'm adding this change, but you should probably be using
the Fedora specfile. The single RPM package is really for
RedHat 7 - 9. Eventually it will phase out.

cheers, jerry
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

F5J+kdqybDhrXK8irQ+k=
=zjCD
PGP SIGNATURE

At 06:20 AM Wednesday, 12/28/2005, you wrote
PGP SIGNED MESSAGE
>Hash: SHA1
>
Schulze L. wrote:
Hi Jerry,
Great news!!! Many thanks!

Just a note, the makerpms.sh patch for building in RHEL4 (CS4) did
not make it into 3.0.21
>
>I'm adding this change, but you should probably be using
>the Fedora specfile. The single RPM package is really for
>RedHat 7 - 9. Eventually it will phase out.

Not too soon I hope ;-)

Ed

. . . . . . . . . . . . . . . . .
Randomly Generated Quote (1004 of 1022):
You can fool some of the people all of the time,
and all of the people some of the time,
but you can never fool your Mom.

Gerald (Jerry) Carter wrote:
I'm adding this change, but you should probably be using
the Fedora specfile. The single RPM package is really for
RedHat 7 - 9. Eventually it will phase out.
Many thanks,
will use the Fedora spec instead. Sorry about the confusion.
Cheers,

PGP SIGNED MESSAGE
Hash: SHA1

Schulze L. wrote:
Gerald (Jerry) Carter wrote:
>I'm adding this change, but you should probably be using
>the Fedora specfile. The single RPM package is really for
>RedHat 7 - 9. Eventually it will phase out.
>
Many thanks,
will use the Fedora spec instead. Sorry about the confusion.

The RedHat/Fedora/RHEL-derivatives packaging needs to be
cleaned up. John T. has spent some time building an RHEL
specfile so probably what we'll do is to merge these changes
with the Fedora specfile, rename the directories and add a
RedHat trying to explain everything.

cheers, jerry
PGP SIGNATURE
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

hmSa/aq8ICrkKNSQPUZpDEY=
=+BCj
PGP SIGNATURE