Gerald (Jerry) Carter
2005-Jul-12 22:08 UTC
[Samba] Samba 3.0.20pre2 Available for Download
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================= Sometimes you have to be someone else in order to be yourself. -- Michael Samuel Finn =============================================================Release Announcements ====================This is a preview release of the Samba 3.0.20 code base and is provided for testing only. This release is *not* intended for production servers. There has been a substantial amount of development since the 3.0.14a stable release (and since the 3.0.20pre1 release as well). We would like to ask the Samba community for help in testing these changes as we work towards the next official, production Samba 3.0 release. This is the last anticipated preX release before moving onto the Release Candidate state of testing. Additional features introduced in Samba 3.0.20pre2 include: ~ o Experimental, asynchronous IO file serving support. ~ o Completed Support for Microsoft Print Migrator. ~ o New Winbind IDmap plugin (ad) for retrieving uid and gid ~ from AD servers which maintain the SFU user and group ~ attributes. ~ o Rewritten support for POSIX pathnames when utilizing ~ the Linux CIFS fs client. What happened to 3.0.15 - 3.0.19? ================================= After some discussion it was deemed that the amount of changes going into the next Samba 3.0 release needed something to catch people's attention. Skipping several releases was chosen as the best solution with the least overhead. There will be no 3.0.15 - 3.0.19 ever released. The next production release following 3.0.20 should be 3.0.21. The original announcement about the version number change can be found in the samba mailing list archives: http://marc.theaimsgroup.com/?l=samba&m=111721010206997&w=2 Support for Microsoft Print Migrator =================================== Samba 3.0.20pre2 includes full support for migrating printers from Windows servers or other Samba servers via the Microsoft Print Migrator tool. Restoring printers requires a working "add printer command" defined in smb.conf. Current; support also allows administrators to create a master list of printer drivers which can be restored in bulk on new (or existing) Samba installations. Asynchronous IO Support ====================== Experimental support for async IO has been added to smbd for certain platforms. To enable this new feature, Samba must be compiled to include the --with-aio-support configure option. In addition, the "aio read size" and "aio write size" to non-zero values. See the smb.conf(5) man page for more details on these settings. ===============Download Details =============== The uncompressed tarballs and patch files have been signed using GnuPG (ID F17F9772). The source code can be downloaded from: http://download.samba.org/samba/ftp/pre/ The release notes are available online at: http://www.samba.org/samba/ftp/pre/WHATSNEW-3-0-20pre2.txt Binary packages are available at http://download.samba.org/samba/ftp/Binary_Packages/ Our Code, Our Bugs, Our Responsibility. (https://bugzilla.samba.org/) --Enjoy The Samba Team -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFC1BJTIR7qMdg1EfYRAkf4AJ9UIZtIQrT+T6RxbCQigBFI0DHFWgCfUskj Q7n+2kcZnm0B56hixh+JL9U=wIfm -----END PGP SIGNATURE-----
Gerald (Jerry) Carter wrote:> This is a preview release of the Samba 3.0.20 code base andSince 3.0.20pre2 samba_vscan 0.3.6 doesn't compile anymore. This has somthing todo with Samba changes, because with 3.0.20pre1 samba_vscan compiles fine (samba_vscan wasn't changed between versions): Compiling global/vscan-fileaccesslog.c with -fPIC global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:156: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:158: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:158: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c:158: warning: preprocessing directive not recognized within macro arg global/vscan-fileaccesslog.c: In function `lrufiles_add': global/vscan-fileaccesslog.c:131: parse error before `#' global/vscan-fileaccesslog.c:142: `found' undeclared (first use in this function) global/vscan-fileaccesslog.c:142: (Each undeclared identifier is reported only once global/vscan-fileaccesslog.c:142: for each function it appears in.) global/vscan-fileaccesslog.c:153: undefined or invalid # directive global/vscan-fileaccesslog.c:154: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:156: parse error before `#' global/vscan-fileaccesslog.c:158: parse error before `#' global/vscan-fileaccesslog.c:158: parse error before `#' global/vscan-fileaccesslog.c:158: parse error before `#' global/vscan-fileaccesslog.c:159: undefined or invalid # directive global/vscan-fileaccesslog.c:160: undefined or invalid # directive global/vscan-fileaccesslog.c:161: undefined or invalid # directive global/vscan-fileaccesslog.c:167: `tmp' undeclared (first use in this function) global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:173: parse error before `#' global/vscan-fileaccesslog.c:174: parse error before `#' global/vscan-fileaccesslog.c:178: parse error before `#' make: *** [global/vscan-fileaccesslog.po] Error 1 Here is /vscan-fileaccesslog.c from line 120 to 180: /** * Adds a new entry, or if the entry already exists, mtime and infected values * are updated * @param fname the file name * @param mtime time the file was last modified * @param infected marks a file as infected or not infected * @return returns a pointer of the new entry, the updated entry or NULL * if no memory could be allocated * */ struct lrufiles_struct *lrufiles_add(pstring fname, time_t mtime, BOOL infected) { struct lrufiles_struct *new, *tmp, *found = NULL; /* check if lru file access was disabled by setting the corresponding value in the configuration file to zero (or below zero) */ if ( lrufiles_max_entries <= 0 ) { DEBUG(1, ("lru files feature is disabled, do nothing\n")); /* do nothing, simply return NULL */ return NULL; } DEBUG(10, ("file '%s' should be added\n", fname)); /* check if file has already been added */ found = lrufiles_search(fname); if ( found != NULL ) { /* has already been added, update mtime and infected only */ DEBUG(10, ("file '%s' in list, update mtime and infected\n", fname)); found->mtime = mtime; found->infected = infected; /* FIXME hm, should we updated it or not?! */ /* found->time_added = time(NULL); */ return found; } else { DEBUG(10, ("alloc space for file entry '%s'\n", fname)); new = (struct lrufiles_struct *)malloc(sizeof(*new)); if (!new) return NULL; ZERO_STRUCTP(new); pstrcpy(new->fname, fname); new->mtime = mtime; new->infected = infected; new->time_added = time(NULL); /* reached maximum? */ if ( lrufiles_count == lrufiles_max_entries ) { DEBUG(10, ("lru maximum reached '%d'\n", lrufiles_count)); /* remove the first one - it really removes only the first one */ tmp = Lrufiles; DEBUG(10, ("removing first entry...")); lrufiles_delete_p(tmp); } DEBUG(10, ("adding new entry to list...\n")); DLIST_ADD_END(Lrufiles, new, tmp); LrufilesEnd = new; lrufiles_count++; DEBUG(10, ("entry '%s' added, count '%d'\n", fname, lrufiles_count)); return new; } } -- der tom
Rainer Link wrote:> Compiling global/vscan-fileaccesslog.c with -fPIC > global/vscan-fileaccesslog.c: In function `lrufiles_add': > global/vscan-fileaccesslog.c:131: error: syntax error at '#' token > global/vscan-fileaccesslog.c:131: error: syntax error before > "DONT_USE_CPLUSPLUS_RESERVED_NAMES"Interesting, I cannot see this message here. Replacing all occurences of "new" with "new_entry" leads to normal compiling and normal behaviour. By the way: After moving the virus file to the quarantine directory the virus file is still visible in the vscan protected share. I have to manual refresh the window to see, that the file is gone. Is it possible to initiate the refresh from samba_vscan? There must be such an funktion in samba, because deleting or moving a file leads to an refresh of the current window. -- der tom
Originally opened bug 2829 against 3.0.20pre1. Same issue seems to exist in 3.0.20pre2 - winbind dumps core shortly after starting. Solaris 9, sparc, gcc 3.2.2, openldap-2.2.24,MIT Kerberos 1.4 Built samba with: LDFLAGS="-L/opt/local/openldap/lib -Wl,-R/opt/local/openldap/lib -L/opt/local/ossl/lib -R/opt/local/ossl/lib" CPPFLAGS=-I/opt/local/openldap/include ./configure --prefix=/opt/local/samba --with-automount --with-profile --with-acl-support --with-utmp --with-winbind --with-ads --with-ldap --with-krb5=/opt/local/kerberos5 --with-pam --enable-debug backtrace from gdb - which isn't much: (gdb) bt #0 0xfee1f82c in _lwp_kill () from /usr/lib/libc.so.1 #1 0xfedd0a24 in raise () from /usr/lib/libc.so.1 #2 0xfedb6ce0 in abort () from /usr/lib/libc.so.1 #3 0x000f3d5c in smb_panic2 (why=0xcbd0c "\235??\220?'?D?\a?D\177??\"\001", decrement_pid_count=32) at lib/util.c:1614 -- *********************************************************************** Bob Martel,System Administrator I met someone who looks a lot like you Levin College of Urban Affairs She does the things you do Cleveland State University But she is an IBM (216) 687-2214 bob@urban.csuohio.edu -Jeff Lynne ***********************************************************************
Hi, I have a samba-3.0.14a + Ldap backend working with roaming profiles all machines are Windows XP fully patched. This is working with no problems for all the machines on the network except mine :\ This is a new PC with a fresh install of XP, first though was that maybe a new update from microsoft borket the profiles so I tryed to logon in another workstation with my user and it worked. I logged on another worstation created a dir on the desktop and logoff then I logon on my PC and the new dir was there then I created another dir called "gasp" and logoff login on another workstation and dir "gasp" didnt appear. So it's not from the user or the smb.conf it's really related with my PC. My PC reads the profile from the samba share but somehow it dont saves it. I already tryed with another user on my machine and the behavior is the same as anyone had a problem like this before? any clues or hints how I can debug this problem? I've already formated the PC *again* and with only XP fully patched the problem remains, I tryed changing to local profile and then change back again to roaming but no go. Please help, regards -- RNuno
Alternatively You can install UPHClean service (User Profile Hive Cleanup service), URL can be found in Samba 3 Official Howto. That service watches for roaming profiles when they have to be deleted on exit.> Hi, > > So it seams that that the problem was related to Nvidia drivers > someone had the same problem you can read all about it here: > > http://www.webservertalk.com/archive214-2004-6-198755.html > > disable the "NVIDIA Driver Service" & reboot and voila it just works > weird problem and it seams that Nvidia just wont fix it. > > thank you all for the help. > > regards, > -- RNuno > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/listinfo/samba >