similar to: PATCH to Samba 3.0.0 to allow interactive --set-auth-user for wbinfo

Hi, I'm trying to connect to a Teradata database via RODBC on a Linux 64 machine (Red Hat Enterprise Linux 5). The ODBC driver is properly configured and queries sent via unixODBC's isql tool work properly. However, this is what happens when I try to connect via RODBC: > library(RODBC) > conn = odbcConnect("thedsn", uid="theuid", pwd="thepass") ***

On Dec 4, 2007, at 11:24, Vikram S. Adve wrote: > Is it possible to AddRequired<...> a pass that is dynamically > loaded? This would be very convenient for a course project but the > documentation about pass interactions says nothing about dynamically > loaded passes and vice versa. > > More specifically, to refer to the pass name in AddRequired, I need > to

Ok, I'm using icecast2 (latest cvs as of maybe 3 hours ago) and darkice .9.1 all compiled under debian/sid with gcc 2.95.4. Everything works ok, as long as I'm using ogg123 to listen to my stream. using xmms (1.27 in in debian sid) it'll buffer up to 50% and then start over again seemingly indefinitely. with winamp 2.80 in winxp, I get nothing but silence, I'd normally thing

Is it possible to AddRequired<...> a pass that is dynamically loaded? This would be very convenient for a course project but the documentation about pass interactions says nothing about dynamically loaded passes and vice versa. More specifically, to refer to the pass name in AddRequired, I need to declare it first but then I can't think of a way to load the module

It might help if you view the default directory ACLs using the getfacl utility. These are what will be inherited by stuff created in the lower directories. I would ask yourself if you actually need ACLs at all. The Samba share permissions are pretty thorough and life is far easier without ACLs as you can clearly see what permissions are in use and backups are not an issue. ACLs can quickly

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a tentative release date for 3.0.1 yet? I'd like to go live with an official release as opposed to hand patching all the little fixes I've seen on the mailing list (i.e., sorry about that; here's a patch, will be in 3.0.1). Thank you for all your work! - -Tom Dickson InoStor, Inc. http://www.inostor.com -----BEGIN PGP

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have built RPMs of samba3.0.0beta3, which are parallel-installable with samba-2.2.x (for easy testing, though you can change that by rebuilding the srpm with other options) for Mandrake 8.1 through 9.1, which are available on my site. I hope to get these up on the samba ftp servers soon, but if you desperatly need packages, grab them from the

Hi, the following patch has been suggested by Mark Bradshaw <bradshaw at staff.crosswalk.com>. The simple concatenation of filenames in sftp client and server results in creating filenames beginning with double slashes when the cwd is the root directory: cwd: "/bar/baz" file: "foo" cwd + "/" + file = "/bar/baz/foo" cwd: "/" file:

Hi - [problem] mount.smbfs is not working on 3.0.0beta3; it has been working thru 3.0.0beta2. When I re-install 3.0.0beta2, it works again. [configuration] *Linux host <hanako> Linux version 2.4.20-4GB-athlon (root@Athlon.suse.de) (SuSE Linux 8.2)) #1 Fri Jul 11 20:16:51 UTC 2003 *samba-3.0.0beta3 complied from source, with configuration option '--with-smbmount'. (same

Hi - My messages may not be reaching this list. Would someone at least confirm receipt of this message even if you have no suggestions/ comments re its content? I have sent several messages concerning mount.smbfs and I guess no one is using smbfs to mount a Windows machine -or- no one has encountered my problem. To recap the problem and give a solution: [problem] mount.smbfs is not working on

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the third (and possible last) beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, you should be reminded that this is a non-production release provided for testing only. If all goes well, we will move onto a series of Release Candidate (RC)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

Hello I am currently setting up a new domain structure at work, and am trying to set up samba to authenticate against my Active directory domain. What I am having trouble doing is joining the Linux system to the domain. The system is running Redhat 8.0, no updates with samba-3.0.0beta3 Here is the error I get [2003/07/29 09:32:53, 3] libads/sasl.c:ads_sasl_spnego_bind(190) got

By logging into a smbd server with the username "HAENGINEERS\KMR", we are able to cause a smbd panic every time. Other usernames ("HAENGINEERS\_TestME") work. The stack trace is below, full logs and smb.conf are available on request (don't want to saturate the list.) I can't post to bugzilla as I can't register a new account as my incoming mail is crippled by

Hello, I originally posted this on samba-technical (http://lists.samba.org/pipermail/samba-technical/2003-July/046076.html), but I just verified that I'm also seeing the same error message with samba-3.0.0beta3. I have not tested if I'm also getting disconnects and Word saving problems that way. But, people using 2.2.7 must have also seen this. Here are some messages I've seen in

About a month ago, I setup a Windows 2000 native-mode domain, and had a couple of Linux machines join the active directory. I followed the steps outlined in the Samba 3.0 docs regarding winbind/PAM/NSS. The machines joined the domain fine, and 'wbinfo -t', as well as 'wbinfo -u/-g' and 'getent passwd/group' return expected results. Connecting from other Windows clients

Hi, 'smbd' and 'nmbd' do behave well however 'smbclient' does not, so some of the other binaries neither i suppose. Running 'smbclient -s /etc/samba-pdc/config' gives me: params.c:OpenConfFile() - Unable to open configuration file "/opt/samba-3.0.0beta3/lib/smb.conf": No such file or directory bin/smbclient: Can't load

I'm really desperate for some quick help in getting the samba-3.0.0beta3 compiled with ldap on Solaris 8. I'm working from the tarball and I'm trying to use this configure command: ./configure --prefix=/opt/samba --disable-xmltest --disable-mysqltest --with-privatedir=/var/opt/samba --with-lockdir=/var/lock/samba --with-piddir=/var/run --with-configdir=/etc/opt/samba