similar to: "shared mem size" parameter and smbstatus

On Samba 1.9.18p10 and previous versions, each of the multiple users on the same Windows Terminal Server Edition machine would get their own smbd process. With Samba 2.0.x (I'm currently testing 2.0.4b), this has changed so that every user on a WTSE machine uses the same smbd process. File ownerships are assigned correctly, but file locking does not work. If one user on a WTSE machine has a

I just attempted to upgrade from Samba 1.9.18p10 to Samba 2.0.4b, and I have had to revert to 1.9.18p10 in less than a day. I attempted to upgrade to 2.0.1 back in January, and had to back off as well. I was hoping the problems I saw then would be resolved in 2.0.4b. I sent a message to this list back in January or February as well, but saw no responses. My environment is about 210 Win95 PCs

Printing from NT4.0 clients to Samba 2.2.3a using the NT4.0 drivers from HP works fine for me, my only problem has been with W2K clients using the W2K drivers from HP. The drivers from www.hp.com appear to be level 3 drivers, that is where they install, and they are downloaded by W2K drivers if they are available when the NT4.0 drivers are also available. Now, whether these drivers from HP are

Is there any support for file locking in a case where multiple Samba servers are set up with shares for the same NFS mounted filesystem? I don't know how the STATUS..LCK file is used, but for instance, could that file be shared between the multiple Samba servers via and NFS mount? Thanks! -- --------------------------------------------------------------------- Jay D. Anderson

I recently upgraded to Samba 2.0, but I have had to revert back to 1.9.18p10 because of problems I could not resolve. I am running Samba on a Sun Ultra-1 with Solaris 2.6, and I compiled Samba using gcc v2.8.1. The problems I was seeing were with saving Excel files. A user might have a small Excel file and try to save it to their home directory. The save would work for a long time (5 to 10

I have Samba 2.2.3a installed and running successfully on Solaris 8 in a test environment. I manually enter printer shares into the smb.conf file, and then I can upload printer drivers to the Samba server from a Windows session without problems. When I try to print to a print queue on this server from a Windows 2000 SP2 machine, the application I am printing from hangs, the CPU usage of the smbd

I am seeing an odd behavior with NT4.0 SP3 workstations trying to rename files on Samba 1.9.18p2 shares on SunOS 4.1.3 servers. Rename, whether it is run from Explorer, winfile.exe, or command prompt fails with "Access Denied I don't see the problem from Win95 PCs at all, and I don't have the problem with shares from Samba 1.9.18p2 shares on Solaris 2.5.1 servers using identical

I've just upgraded to Samba 3.0.2a from 2.2.8a, and I've run into a problem. We have an automated build process for our Windows PCs where first a Windows XP Pro image is copied onto the machine, then after a reboot the local administrator is autologged on and a drive is mapped from the Samba server using Active Directory domain credentials. At this point the new machine hasn't

This problem appears to be a bug. I am seeing the problem running Samba 3.0.2a on both Solaris 8 and RH Linux ES3. This problem was not present in Samba 2.2.8a. The Samba servers are member servers of an Active Directory domain, and all other file and print sharing is working well. Global section of smb.conf included below. On a Windows XP client that hasn't been added to Active

With Samba 3.0.23c I am unable to join the server to AD. The command and messages return: # ./net ads join createcomputer=OUlevel1/OUlevel2/Servers -Uadminacct adminacct's password: Using short domain name -- DOMAIN Failed to set servicePrincipalNames. Please ensure that the DNS domain of this server matches the AD domain, Or rejoin with using Domain Admin credentials. Disabled account for

I wrote about this problem more than a week ago, but got no response. I upgraded to 3.0.3 hoping this issue would go away, but it hasn't. I am seeing the problem running Samba 3.0.2a or 3.0.3 on both Solaris 8 and RH Linux ES3. This problem was not present in Samba 2.2.8a. The Samba servers are member servers of an Active Directory domain, and all other file and print sharing is working

Hi! I've been struggling with this install of Samba 2.0.4b on Linux/x86 2.0.36. All of the client machines run Windows NT 4, SP 3. I'm exporting /tmp as pub, and if I right click in the folder and create a new folder, it doesn't show up until I go to 'view' and 'refresh'. If I delete something, it doesn't go away until I refresh. Why? Output of testparm:

We have been using samba since 1995 and have found it superb, Thanks to all. Recently I built Samba1.19.17alpha4 on a DECstation 5000 running Ultrix 4.4 and included -DFAST_SHARE_MODES This results in UIST>smbclient -L UIST Session request failed (0,0) with myname=UIST destname=UIST Unspecified error 0x0 Your server software is being unfriendly and ERROR

I'm trying to get a backup system going. I've got a script that will grab all the files I need, but there are several gigs. The command line i'm using now is: smbclient file://server/share XXXXX -Uuser -Tc /usr/tmp/share.tar /var/log* /usr/home* etc... This is taking too long for all of the servers. What is the exact syntax so I can backup changed/updated files in relation to the

Hello again, on CentOS 6 / 64 bit what is please the best way to permanently increase the shared memory? I'd like to give shared_buffers = 4096MB to PostgreSQL 8.4 on my machine with 16 GB RAM, but I currently only have: # sysctl -A|grep shm kernel.shmmax = 33554432 kernel.shmall = 2097152 kernel.shmmni = 4096 and this produces the error in /var/lib/pgsql/pgstartup.log:

Hi, I want some config depending on memorysize. What I tried was if ($memorysize >= 256 * 1024*1024) { ... } But this fails because $memorysize is a string (and contains a "G") and can''t be compared to an int. Are all facts strings? How do I work with numbers? regards, Andreas -- Andreas Kuntzagk SystemAdministrator MDC Berlin / BIMSB Tel.: +49 30 9406 2997 --

On 17/02/16 14:32, Michael H wrote: > Hi, re-posting this with a more appropriate subject for my reply; > >> The easy answer is yes .. glibc requires so many things to be restarted, >> that is the best bet. Or certainly the easiest. >> >> Note: in CentOS 7, there is also a kernel update which is rated as >> Important .. so you should boot to that anyway:

I need to be able to access my Samba network from a DOS floppy. Obviously it must be a tcp/ip client rather than netbeui. Any pointers on doing this? Not *too* cryptic as I'm not expert at this sort of thing. I'm pretty sure I saw some material on the Samba site, but now I cannot find it. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Lindsay Allen

On 02/17/2016 07:08 AM, Michael H wrote: > On 17/02/16 13:01, Johnny Hughes wrote: >> I normally just let the daily announce post to this list show what >> is available for updates, but there is a CVE (CVE-2015-7547) that >> needs a bit more attention which will be on today's announce list >> of updates. >> >> We released a new glibc yesterday for

Hello, I have the following entries in /boot/loader.conf: kern.ipc.shm_use_phys="1" kern.ipc.semmns="500" kern.ipc.semmni="40" kern.ipc.semmap="500" which are set correctly. Unfortunately, the following two entries kern.ipc.shmmax="512000000" kern.ipc.shmall="65526" do not change the corresponding values according to