similar to: WHATSNEW-3.0.3pre1

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

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,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.3 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes and new features added since 3.0.2a that we feel it is important make it available to the Samba community for wider testing. Common bugs fixed in this preview

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a preview release of the Samba 3.0.3 code base and is provided for testing only. This release is *not* intended for production servers. However, there have been several bug fixes and new features added since 3.0.2a that we feel it is important make it available to the Samba community for wider testing. Common bugs fixed in this preview

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

I have some weird error with one of my samba installation. When modifying samba password using smbpasswd, samba seems trying to add same attribute (instead of delete and add again), pls see the "MOD" from log file (from different domain) : UNSUCESSFULL Mar 15 17:10:53 hurricane slapd[27056]: conn=29489 op=1 MOD dn="uid=pwreka,ou=people,ou=purwakarta,dc=indorama,dc=com" Mar 15

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]

I just receive a copy of the official samba 3 howto, to be honest i'm rather disapoint with the content and layout. Well with free online version, i can't complaint, but with 'paid' version maybe i can complain to the author :-). Most of the contents are still the old documentation with few 'little' updation for samba3. Imo, its better if it can be rewrite from scratch

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

Hi I have a NAS with rsync 3.0.3pre1. I know that is not new, but a NAS is not easy to update. This usually works fine. I have set up jobs to backup various stuff to another NAS. This is the statistics of one run. Though there were seen files (file size, vmware images) it finished almost immediately which lead to the funny transfer speed. receiving incremental file list Number of files: 125

-----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"

I was wondering if anyone knows if there are any plans to fix Bug #1139 (reproduced below) in version 3.0.3. I haven't tried 3.0.3pre1 yet, but from what I read of the changes it doesn't look like this bug has been addressed. Is there some other work around? This bug is quite annoying as some of our users/administrators would like to use Windows to modify ACLs and we recently

On Wed, Jan 06, 2016 at 08:33:12PM +0100, Andreas Maier wrote: > Am 06.01.2016 um 20:10 schrieb Jeremy Allison: > >On Wed, Jan 06, 2016 at 07:58:32PM +0100, Reindl Harald wrote: > >> > >>Am 06.01.2016 um 19:35 schrieb Andreas Maier: > >>>Am 06.01.2016 um 19:28 schrieb Jeremy Allison: > >>>>Can't reproduce this on latest 4.3.x (and I just

Okay, I realize at this point that's it's certainly easier for me to just compile 3.0.1 from scratch, but I'm irritated that I can't get patch to work right. Maybe somebody will lead me in the right direction. I've scoured the archives and Google for answers to this, to no avail so far. I'm running Samba 3.0 on Solaris 9. I'm hoping that the new release will help me

I have a question I hope one of you can help me with. In what version did Samba begin to include support for SMB signing? It looks like 3.0 but I need to be sure. According to http://de.samba.org/samba/whatsnew/samba-3.0.0rc4.html <http://de.samba.org/samba/whatsnew/samba-3.0.0rc4.html> on line 14 is states: 14) Full support for client and server SMB signing to ensure compatibility

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================== Oplocks are strange -- Volker Lendecke ============================================================== Release Announcements ===================== This is a release candidate of the 3.0.20 code base and is provided for