similar to: Samba 3.0.3pre1 Available for Download

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several issues fixes since the 3.0.2a release and new features have been added as well. See the "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the latest stable release of Samba. This is the version that production Samba servers should be running for all current bug-fixes. There have been several issues fixes since the 3.0.2a release and new features have been added as well. See the "Changes" section for details on exact updates. Common bugs fixed in Samba 3.0.3 include:

Hi all, Please excuse me if this question is not appropriate for this forum: Lets assume that samba server crashed or was shut down abnormally, while users where holding open files in the server. In this case, I've noticed that locking.tdb is not being cleaned when samba is restarting. I was wondering why shouldn't it be cleaned. Thanks, Nir

Hi, Does someone know a document which explains the TDB structure. functionalites, and format of the TDB files etc. I need to understand why some of the TDBs like messages.tdb, unexpected.tdb, brlock if not read_only, locking.tdb, session.tdb, wins.tdb are called with TDB_CLEAR_IF_FIRST tdb flags. Why some TDBs are opend with O_RDWR|O_CREAT flags viz. gencache.tdb, group_mapping.tdb,

Does anyone have any idea what can cause nmbd to begin gobbling CPU? We are running Samba 2.2.4 on HP-UX 10.20, having upgraded from Samba 2.0.10 about a month ago. Our clients are a mixture of NT 4.0 and Win2K. Today, we have begun to see widespread client drive disconnections, and nmbd is averaging 60%+ CPU usage with peaks up to 100%. We have heard reports of network problems at our site

I'm having a problem involving Outlook and .pst files and a lock that is getting "stuck" I believe. Once Outlook crashes in the fashion it does, it is unable to reopen the file, claiming it is already in use. Explorer also does not let me access the file. Rebooting the workstation does not fix it. smbstatus does not show the lock, however hwen I show byte range locks, there is one,

Found interesting info on http://us1.samba.org/samba/ftp/pre/WHATSNEW-3.0.3pre1.txt Gerald (Jerry) Carter <jerry@samba.org> * Fixed iterator in tdbsam. * Fix bug that disabled accounts with a valid NT password hash, but no LanMan hash. Is this means we can have only sambaNTPassword without having sambaLMPassword attribute? it was allowed by the schema anyway. --beast

Hello, I'm using samba416-4.16.11 on FreeBSD 14.1 (on ZFS, in a jail, with quotas on those filesystems, etc) I'm seeing these entries in my logs. Is this something which needs action? If not, I'll start ignoring them. Nov 11 19:00:45 tm samba-dcerpcd[7373]: [2024/11/11 19:00:45.852391, 0] ../../lib/tdb_wrap/tdb_wrap.c:65(tdb_wrap_log) Nov 11 19:00:45 tm samba-dcerpcd[7373]:

Dear *Fabien Chevalier*, I found your message in http://lists.samba.org/archive/samba/2004-February/080990.html I got in the similar problem. Have you solved the problem ? If so, please let me know the solution. Thanks and Best Regards, Tomoo Nomura -- ****** Nomura Technical Management Office Ltd. ***************** Tomoo Nomura nomura@tmo.co.jp http://www.tmo.co.jp/ Phone:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second preview release of the Samba 3.0.3 code base and is provided for testing only. This release is *not* intended for production servers. Use at your own risk. There have been several bug fixes since the 3.0.2a release that we feel are important to make available to the Samba community for wider testings. See the "Changes"

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is the second preview release of the Samba 3.0.3 code base and is provided for testing only. This release is *not* intended for production servers. Use at your own risk. There have been several bug fixes since the 3.0.2a release that we feel are important to make available to the Samba community for wider testings. See the "Changes"

Greetings everyone I finally succeeded in doing the seemingly most difficult thing, "following directions." I got my act together configuring the smb.conf and migrating using net rpc vampire into tdbsam. There are issues with this migration in which computer netbios names which are obviously all uppercase were not being created in /etc/passwd. I put my C cap on and converted the computer

I have made rsync 3.0.3pre1 available for release testing. This is another bug-fix release, with the only "enhancements" being some improved terminology in the rsyncd.conf manpage and some improvements in the testsuite. To see a summary of the changes since 3.0.2, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.3pre1-NEWS You can download the source tar

I have made rsync 3.0.3pre1 available for release testing. This is another bug-fix release, with the only "enhancements" being some improved terminology in the rsyncd.conf manpage and some improvements in the testsuite. To see a summary of the changes since 3.0.2, visit this link: http://rsync.samba.org/ftp/rsync/src-previews/rsync-3.0.3pre1-NEWS You can download the source tar

Hello, I am currently trying to setup Samba 3.0.3pre1 to share my freshly installed LaserJet. I have NOT had any printer until now, so I can't tell you if the behavior was different before 3.0.3pre1. The problem: My smb.conf contains: > [global] > ## Printing > load printers = yes > printcap name = cups > printing = cups > [printers] > comment

Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part Url : http://lists.samba.org/archive/samba/attachments/20040414/e4d94ced/attachment.bin

Hi I already wrote about this problem half a year ago but didn't get an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. But still I often have rsync stall much longer than that. Some examples: 2009/12/14 23:14:35 [8707] io timeout after 11670 seconds -- exiting 2009/12/14 23:14:35 [8707]

Hi All, We have been running Samba (3.0.2), CUPS on SUSE 9 Pro for some time now with no problems. This morning however it all seems to have gone wrong, and the users on site can no longer print. When a user prints a document nothing comes out on the printer and further investigation in the Windows printers folder reveals the printers are sat with 'x' amount of jobs on them and constantly

Hi I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. However sometimes I get very big timeout times like this one: io timeout after 12220 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] rsynd.conf on the receiving side only defines modules, no timing parameters. How can that happen? What can I do to prevent

Hello I have a problem while synching between two NAS boxes with Linux. First NAS: group staff=50 (3.0.3pre1) Second NAS: groups ftp=50, staff=500 (rsync 3.1.1) I synched with -rptgo, without --numeric-ids. The expected result was that the items on the second group would be staff as well even with a different gid. However it looks like the 50 was taken literally and now all staff items are ftp