Re: [Samba] uids/gids changed after upgrade from 3.021c to 3.023
On Wed, Jul 19, 2006 at 11:02:31AM -0500, Gerald (Jerry) Carter wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard Santiago wrote: Hi Jerry, Yes, I've upgraded through yum with the rpm. The platform is Fedora Core 4. The package may be broken. I'm not convinced yet that this is our problem. Is the yum upgrade coming from an official Fedora mirror? Jay, did the package layout for the Samba rpms in FC4 change ? Specifically, moving the $(lockdir) from /var/cache/samba to /var/lib/samba ? Looking at my spec file, I see --with-lockdir=/var/cache/samba so I don't think so. :-) Hmm. Looking at download.fedora.redhat.com, I see that FC4 shipped with samba-3.0.14a-2.src.rpm, and only has a single update to samba-3.0.23-1.fc4.src.rpm, so I'm kinda curious where the 3.0.21c rpms came from. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbmount
On Sun, Jun 11, 2006 at 09:22:20AM -0400, Douglas Corner wrote: I am moving FROM: RH EL AS 3.0, Kernel is 2.1.21-4, Samba is 3.0.0-14.3E (This is what came with the RH distribution) TO: Fedora Core 5 Kernel is 2.6.16-1.2122_FC5 Samba is 3.0.22-1.fc5 (Both kernel and samba have been upgraded from the distribution.) I can't find the smbmount (or smbumount) command. The FC5 kernel ditched smbfs in favor of cifs. I'm pretty sure we mentioned it in the release notes. You can use mount -t cifs ... to mount remote SMB filesystems using the Liunx CIFS filesystem. Further information about the Linux CIFS filesystem can be found at http://linux-cifs.samba.org/ Bug reports about the Linux CIFS filesystem in Fedora 5 should go to bugzilla.redhat.com under the kernel component. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Fedora Core 5 CIFS - please help!
Did you get the most recent FC5 update kernel? Try running yum update and see how many packages on your system have updates avaliable. Note that cifs has almost nothing to do with Samba--I packaged mount.cifs there because mount.smbfs was already there, but the actual cifs code is in the kernel. If you go to report a bug in cifs at bugzilla.redhat.com, remember to file it against the kernel component and not Samba. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Limit of group membership for a user?
On Mon, Mar 13, 2006 at 07:09:51PM -0500, Cybionet wrote: Greeting all, Sorry, I previously send my message in a wrong topic. I have a strange problem between Samba and OPenLDAP. Here the version. Samba: 3.0.21 OpenLDAP: 2.2.28 Problem: My Windows user can login to the domaine by a Samba PDC, but when the user try to enter a sharing ressouces on the same server nothing append. This user have all the good permission. Solution: After some research (in samba log), I found that this user was in 76 differents groups (Don?t ask why, it is a special case lol), and the fact is samba don?t seem to support this. If I remove the user of 12 groups then samba authorise the user to access to share again. Question: My question is, why samba do not seem to support a user in 76 differents groups, but support 64? And yes I have the log and can reproduce this problem again . You haven't said anything about which operating system you are using. Different unix-like operating systems have different maximum numbers of groups that a user can be a member of. I would guess that the OS that you are using has a 64-group limit. Contact your operating system vendor and find out. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Help for problem samba between linux and windows
On Mon, Nov 21, 2005 at 11:04:18AM +0100, Christelle Ronce wrote: Hi, Excuse my poor english !! I have a problem samba between linux and windows. I explain my actual situation : - windows 2000 SP4 - share a directory my_windows : d:\jagodin\partage - linux Redhat ES 4 - kernel version 2.6.9-5 in /etc/fstab : //my_windows/partage /export/home/cerit/jagodin/partage smbfs username=tomcat,password=x,rw,uid=tomcat,gid=tomcat,codepage=cp850,iocharset=utf8 0 0 That's a Linux Kernel SMBFS problem, not a Samba problem. The first thing to try is the Linux CIFS filesystem instead. See http://www.samba.org/samba/Linux_CIFS_client.html or man mount.cifs but it may be as simple as replacing smbfs with cifs in your /etc/fstab. If that doesn't help, contact your Red Hat support person, or an appropriate Linux kernel mailing list. Unfortunatly, I don't think smbfs has an upstream maintainer, so switching to cifs really is the best option. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Path issues in share name
On Sat, Nov 12, 2005 at 11:55:51AM -0500, Barry Johnson wrote: I did check the permissions of the directory and everything looks good. [EMAIL PROTECTED] home]# ls -l total 413528 drwxr-xr-x 2 baj baj 4096 Nov 12 10:35 baj drwxrwxrwx 4 root root 4096 Nov 12 11:35 samba It also isn't mounting my home dir on the windows xp machine, same error as before with the obvious changes in the error message, and those permissions look good too. I'll mention that I didn't make any changes to the home dir section of the config file. I did a ps of the smb process and it still looks like it runs as root, does it spawn children that run as some other user that could be causing this problem??? You probably have SELinux enabled, and didn't adjust the Samba policy to allow access to that directory. The easy workaround is to disable SELinux or put it in permissive mode. The correct solution is to change the policy and/or the security context for /home/samba. Please submit a bug report at bugzilla.redhat.com against the selinux-policy-targeted component. Unfortunatly, it's impossible to create a SELinux policy for Samba that will work for all configurations out of the box, because the configuration for Samba is so site-specific. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Seg from net ads join
On Sun, Aug 07, 2005 at 11:39:17AM -0500, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
NIGGEMYER Brant wrote:
FYI updated kerberos libs from krb5-libs-1.4-3 to krb5-libs-1.4-5;
problem still existed.
==26396== Invalid free() / delete / delete[]
==26396==at 0x1B909743: free (vg_replace_malloc.c:152)
==26396==by 0x3DAABA: remove_error_table (in /lib/libcom_err.so.2.1)
==26396==by 0x4D98C3: (within /usr/lib/libkrb5.so.3.2)
==26396==by 0x4D95C6: (within /usr/lib/libkrb5.so.3.2)
==26396==by 0x52A9D9: (within /usr/lib/libkrb5.so.3.2)
==26396==by 0x1B8F2057: _dl_fini (in /lib/ld-2.3.5.so)
==26396==by 0x238C68: exit (in /lib/libc-2.3.5.so)
==26396==by 0x222DED: __libc_start_main (in /lib/libc-2.3.5.so)
==26396==by 0x2FD44: (within /usr/local/samba/bin/net)
==26396== Address 0x53BDB0 is not stack'd, malloc'd or (recently)
free'd
Jay, Can you give me some feedback on the krb issues
we are seeing in FC4? I've got 3 or 4 reports that all
appear to be bugs in the krb-1.4.1 code.
I don't see any recent mention of problems on the MIT
mailing list either.
According to Nalin, who is our krb5 expert, it isn't actually a bug in
our krb5, but in e2fsprogs, which is where the error_table handling
code ended up. Apparently it isn't correctly distinguishing between a
dynamically allocated error table (which it can free), and a
statically allocated one (boom!). You can work around the problem by
removing all the calls to initialize_krb5_error_table() (in
source/libads/kerberos{_verify,_keytab,}.c), but I think that makes
debugging krb5-related error significantly more difficult.
-- JF
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.12pre1 build failure
On Tue, Mar 01, 2005 at 12:57:54PM -0600, Rex Dieter wrote: Gerald (Jerry) Carter wrote: Rex Dieter wrote: | $ grep interpret_long_unix_date */*.[ch] | | It's there in samba-3.0.12pre1/source/smbd/trans2.c: | BUILD/samba-3.0.12pre1/source $grep -r interpret_long_unix_date * | smbd/trans2.c: tvs.actime = | interpret_long_unix_date(pdata+8); | smbd/trans2.c: write_time = | interpret_long_unix_date(pdata+16); | smbd/trans2.c: changed_time = | interpret_long_unix_date(pdata+24); That's not our 3.0.12pre1 I don't think. Did you get it from Fedora ? I downloaded the source from us4.samba.org. I'll go get it again, and compare. Is your spec file applying the 64bit_timestamps patch? As of 3.0.12pre1 it's obsolete, because interpret_date() changed. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Fedora Core 3 and Samba
On Tue, Nov 23, 2004 at 12:49:06PM -0600, Paul Espinosa wrote: snip I know it's not a samba problem per se. I'm giving a heads up in case this is a purposeful shift by Redhat and also in case other distros go this route also. And yes, I've logged a bug with RedHat. I see a changelog entry for shadow-utils in rawhide saying - re-allow $ as last char for the sake of samba (#132782) The bug number appears to be wrong, but it's probably worth trying shadow-utils-4.0.3-42 to see if the problem is actually fixed. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Possible passdb corruption on upgrade to 3.0.6?
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=132077 is a bug report saying that the UWX flags are lost when the passdb.tdb file is upgraded from 3.0.4 to 3.0.6. Has anyone else seen this behavior? Could this be responsible for some of the trouble folks are having with 3.0.6 upgrades? Will someone who's better at passdbs and tdbs look into this before I get a round tuit? -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Redhat AS 3
On Wed, Mar 31, 2004 at 05:07:27PM -0800, jamie wrote: Does anyone know if on Redhat AS 3, The Samba 3 Rpms have ldapsam_compat compiled in? I am trying to get it working and so far not having any luck. - They don't. Red Hat never shipped a 2.2 version of Samba with LDAP support, so there was no requirement for the 3.0 RPMS to support it. You can always grab the .spec file from the source RPM and look at the configure line in it. The spec file can tell you everything you need to know about how the binary RPMs were made. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] how many users?
On Mon, Nov 17, 2003 at 03:25:02PM +, John H Terpstra wrote: On Mon, 17 Nov 2003, Pirkka Luukkonen wrote: Hi! Can anyone tell how many users with different uids can you add to samba/gnu linux/ldap -environment? Is 5-20 users possible? The key limitation is how many users your UNIX/Linux system can handle. If UID/GID has a maximum value of 65535 (an unsigned int) then that is the limit you can use. That would be an unsigned short on a 32-bit machine (I hope you're not still using a 16-bit machine these days). I don't know about other Linux distributions, but Red Hat Linux (Fedora Core these days) and Red Hat Enterprise Linux have a bug where smbfs doesn't work with uids 16 bits. AFAIK, everything else works fine. -- JF P.S. I will be very happy when cifsfs replaces smbfs forever. C'mon 2.6! -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Backup from Linux onto Win2K-share
On Mon, Nov 17, 2003 at 12:28:33PM +0100, [EMAIL PROTECTED] wrote: No, I'm not really taring. Right now I'm using following command to mount a share on the windows box: smbmount //ntsrvsr3/cmdhp5 /mnt/backupsmb -o username=kwhadm,dmask=777 I also tried mount -f smbfs ; but this failed as well. Some more descriptions: I have a Windows-2000-domain with ten W2K servers. One of the servers is my backup server which has a share for each of the other servers where they can put their database-backups. As well I have a Linux box running a database; it also has to put its database backup to a share (named above). A few words on my database: I'm running SAP DB 7.3. It has the option to backup the database either on a tape or on into a file. If using file-backup this file can be anywhere on the linux, either in the local file system or in NFS or in SAMBA. SAP DB does not care on that as long as it can use a mount. In Windows this works out perfectly for me (same technique). Ive tried FTP, SAMBA and NFS: nothing can backup more than 2 or 4 Gigabyte. Ive tried Suse Enterprise 8, Suse 8.2, Mandrake 8.1: same problem everywhere. At home I tried to manage it with XP-Professional and Suse Linux 8.2; there I've tested a new compiled kernel and samba 3.0.1: same problem. Sorry, but I'm getting frustrated. You're using the Linux Kernel smbfs file system module, which is a part of the Linux kernel and not really part of Samba per se (although the smbmount helper program is included in Samba). Some versions of it have a 2G file size limit. There are patches that you can apply to your Linux kernel (and possibly your Samba as well) to. Can you try using the smbclient command to copy the file to your server? The other alternative is to try installing the Linux CIFS filesystem module. See http://www.samba.org/samba/Linux_CIFS_client.html -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] nmbd -n option is ignored in samba-3.0.0rc3?
One of my users is reporting that his Samba configuration is behaving differently now that I've upgraded to 3.0.0rc3. He is using nmbd -n to set the netbios name of the machine. With samba-2.2.x, this worked as he expected, and the machine name seen when browsing from Windows clients whas the name he set with -n. With 3.0.0rc3, the machine name reverts to the hostname of the machine. Using netbios name = in the smb.conf file works as expected with 3.0.0rc3. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Testparm with two arguments in 3.0.0rc3
What should testparm do if you provide only two arguments to it (a config file and either an IP address or a hostname)? According to the manual page, it needs both a hostname and an IP address. With the 3.0.0rc3 testparm, if you provide only two arguments, it ignores the second one. With the testparm in 2.2.7, it performed the access testing, and possibly returned bogus results if a hostname was given, but the access control was by IP address, or vice versa. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Trouble building samba-3.0.0rc3 on Red Hat Linux AMD64 machine
It the Makefile, the installclientlib target calls
-$(INSTALLCLIENTCMD_SH) bin/[EMAIL PROTECTED]@ $(DESTDIR)${prefix}/lib
and
-$(INSTALLCLIENTCMD_A) bin/libsmbclient.a $(DESTDIR)${prefix}/lib
However, on the AMD64 platform, ${prefix}/lib (/usr/lib) is reserved
for 32-bit compatability libraries, and these 64-bit libraries should
be installed in /usr/lib64/
To make matters more confusing, my build environment doesn't have a
/usr/lib directory, so these libraries get installed on top of each
other as a file named lib in the /usr directory.
@libdir@ is set to /usr/lib64/samba (because --with-fhs is set) so we
can't simply use it here. I don't see any convenient macros that
expand to /usr/lib64, which is probably why /usr/lib was hardcoded
there.
My current workaround is to rm -f /usr/lib and install the libraries
by hand in the correct location in my Red Hat samba.spec file. It's
ugly. Can someone come up with a better fix?
-- JF
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] domain controller = in packaging/RedHat/smb.conf in samba-3.0.0rc3
Can someone remove this obsolete parameter from packaging/RedHat/smb.conf before it confuses more people? -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Findsmb manual page now lies because the output of smbclient -L changed?
In 2.2.8a days, findsmb would print the OS and Server version of the machines it found, like this: *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION - 192.168.49.247 WINQA1 [QATEST] [Windows 5.0] [Windows 2000 LAN Manager] 192.168.49.250 WINQA2 +[QATEST] [Windows 5.0] [Windows 2000 LAN Manager] The man page for findsmb in 3.0.0rc2 claims that findsmb will still do so, but the actual output is always more like: IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION - 192.168.49.247 WINQA1 [QATEST] 192.168.49.250 WINQA2+[QATEST] without any OS or server version information. After reading the source to findsmb, I discovered it was using open(SMB,$SAMBABIN/smbclient -N -L $name -I $ip -U% |) to get the information, and sure 'nuff, the samba-2.2.8a smbclient says: added interface ip=192.168.48.121 bcast=192.168.51.255 nmask=255.255.252.0 Domain=[QATEST] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] Sharename Type Comment - --- Error returning browse list: NT_STATUS_ACCESS_DENIED Server Comment ---- WINQA1 WINQA2 WorkgroupMaster ---- QATEST WINQA2 While the 3.0.0 smbclient says: Sharename Type Comment - --- Error returning browse list: NT_STATUS_ACCESS_DENIED Server Comment ---- WINQA1 WINQA2 WorkgroupMaster ---- QATEST WINQA2 And I haven't found anything in the smbclient manpage about restoring the 2.2.x style verbose behavior. So what's the right thing to do? a) Find a way to make smbclient verbose again so findsmb will work as documented. b) Change the findsmb documentation (and code) to match the new smbclient behavior. And why hasn't anyone noticed this before now? Oh, and there's a braino in the smbclient man page. --- smbclient.1.orig2003-09-04 19:33:00.0 -0400 +++ smbclient.1 2003-09-04 19:33:09.0 -0400 @@ -157,7 +157,7 @@ .TP -V -Prints the version number for \fBsmbd\fR\. +Prints the version number for \fBsmbclient\fR\. .TP -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] How to share the tape drive in samba server for windowsuser
On Wed, Jun 18, 2003 at 09:46:52AM -0700, Jonathan Johnson wrote: If you're looking to share the tape drive so you can use Windows' native backup utility to write directly to the tape, sorry -- can't be done with Samba. This is because a tape drive is not seen by the system as a disk drive; the software wants to communicate directly with the drive. A tape drive is a sequential, exclusive access device, not a random access device. That means that only one process can read/write to the drive at a time, and the tape is written/read from front to back. You could probably do something clever with a magic script in the Samba config, but it still wouldn't work with native Windows backup utilities. (Are there native Windows backup utilities that can access a remote tape drive?) You could probably get it to work with tar under Cygwin if you tried hard enough. But if Cygwin's tar doesn't have remote-tape access disabled, you'd be better off using that instead--it's much lower overhead. ... A quick search reveals this software to look at: NovaNet (www.network-backup.com), Arkeia (www.arkeia.com), NetVault Workgroup Edition (www.bakbone.com), (Veritas BackupExec not available for Linux,) anyone know of open-source, multi-platform network-aware backup software? There's always Amanda (http://www.amanda.org/). It can back up Windows clients in one of several ways. The three obvious ones are: 1: build the Amanda client software under Cygwin. See http://randomnotes.pwp.blueyonder.co.uk/Amanda-Cygwin-HOWTO.html for instructions. I use this method to back up my Windows 2K laptop. 2: use Amanda's smbclient interface as described in the Amanda documentation. 3: smbmount (or other network filesystem) the Windows client drive on a Unix/Linux/BSD machine and have Amanda back that up. There's been some effort to create a native Windows Amanda client, but I don't think it's completed or usable yet. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba Sage Line 50 Accounting
On Thu, Jun 05, 2003 at 03:33:01PM +, [EMAIL PROTECTED] wrote: On Thu, Jun 05, 2003 at 11:35:20AM +0100, Louis Sabet wrote: Hi all, Having a very specific problem here: I have a working RedHat9 server running Samba 2.2.7 (the release that comes with RH9), acting as a PDC/File Server to around 15 WinXP Pro client workstations. This all works nicely, apart from our accounting package, Sage Line 50, which depends on its data being stored on a network share. Previously, when the data was stored on a WinNT4 share, there was no problem, several users could concurrently connect into the database and work simultaneously. Now, using samba, this isn't possible. Sage will only allow one user to log in and access the DB at any one time. As soon as that user logs out, the next user can log in. This isn't normal Sage behaviour. Can you give the exact error message please. Also please upgrade to Samba 2.2.8a for security reasons. Or at least the samba-2.2.7a-security-rollup-fix which is conveniently avaliable from updates.redhat.com or via Red Hat Network. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Does the SWAT tool come with the Red Hat 8.0distribution?
On Mon, Mar 10, 2003 at 02:10:04PM -0500, David Jackson wrote: To get back to SWAT, how do i get SWAT running on my Red Hat 8 Server? Is the rpm located on one of the CDs or how else do i install it? Thank you Open Source Community It's located in the samba-swat RPM. After you install it, you need to edit /etc/xinetd.d/swat and change disable = yes to disable = no, then have xinetd reload it's config with the command service xinetd reload. I suspect there's a simple gui way to do this, but I don't know it. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Slow performance with lots of files in one directory
On Thu, Jan 09, 2003 at 04:19:27PM -0200, Roberto João Lopes Garcia wrote: At 15:04 09/01/2003, Chris Palmer wrote: Anders Nordby writes: I've got performance problems with copying small files over to a Samba share in a directory that has lots of small files (1 to 2 files). It takes too long time to copy new files (they drip in at a fast pace), and smbd eats a lot of CPU time. This could be not so much a Samba problem as a Unix kernel problem. Traditional Unix filesystems (UFS, FFS, ext2, et c.) do not deal well with very full directories. See Maurice Bach's book *Design of the Unix Operating System* and M. K. McKusick's *Design and Implementation of the 4.4BSD Operating System*. These are both just great books. If you are on Linux, try using one of the new filesystems like ReiserFS, XFS or JFS. Among other abilities, they can handle extremely full directories better. What about EXT3 file system? EXT3 uses the same linear directory structure as EXT2. Therefore, it suffers the same performance penalty when dealing with large directories. -- JF -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
