similar to: Samba not using my RAM for shared memory?

Running Samba v2.0.4b on a RedHat v6.0 system, I find that when I log onto the server running Samba my authentication fails twice before succeeding. I get these messages in the Samba log file: [1999/06/16 11:45:11, 1] smbd/password.c:pass_check_smb(532) smb_password_check failed. Invalid password given for user 'steve' [1999/06/16 11:45:13, 1] smbd/password.c:pass_check_smb(532)

I've encountered a new problem that occurred during installation. It happened identically on new installs for both Caldera OpenLinux 2.2 and Red Hat 6.0. These files did not get created: SHARE_MEM_FILE, SHARE_MEM_FILE.processes, and STATUS..LCK. I'm using the smb.conf from another working system that has the identical share layout. The default Samba install was 2.0.3 for both

I'm running Samba v2.0.5a on a RedHat v6.0 system. This server provides SMB shares to Win98, OS/2 and Linux clients. Everything is running fine with the Win98 and OS/2 clients, but I have a few questions regarding Samba and Linux clients. 1. Is there a way for Linux systems to receive SMB messages? Something analogous to Windows' "WinPopup" or OS/2's "Network

When the Win9x and OS/2 machines on my LAN boot-up, they set the local time from the Samba (v2.0.4b) server. Is it possible to do the same thing on a Linux system? If so, how is it done? Yes, I know I can use rdate to accomplish the same goal, but I'm trying to restrict the accessible services on the server to the most minimal possible. Since I have to have Samba services anyways, I

I have posted a few messages earlier redgarding the lack of a STATUS..LCK file. I have progressed a bit further on the advice of some nice people on this list serve. Now, I seem to have the follwing problem with samba 2.0.4b on Linux 2.2.6 runnning on a Motorola StarMax 3000. after executing smbstatus, i get this message: Samba version 2.0.4b Service uid gid pid machine

I'm having a hell of a time mounting Samba shares under Linux. Both server and client are running kernel v 2.2.1x on otherwise RedHat v6.0 systems. The machine running the Samba (v2.0.5a) server is working great. Directories and printers are easily accessable from Win98 and OS/2. It's Linux as a SMB *client* that is giving me problems. I can easily mount shares from a command prompt

I've got a couple problems with Samba<-->OS/2 communications. First, though, here's my environment: Samba machine: Celeron/400 /w 256MB of RAM IDE hard disks 100Mbps 3Com NIC RedHat Linux v6.0 + all RH-released updates + kernel v2.2.13 Samba v2.0.6 filesystem: ext2, cache size: dynamic OS/2 machine: Pentium 3/550 /w 256MB of RAM SCSI hard disks 100Mbps 3Com

I've got a 5-disk CD-ROM changer that I'd like to access via Samba v2.0.4 on my Linux (RedHat v6.0) system. I already have Samba up and running well, but I haven't had to deal with the CD changer until now. The kicker, of course, is while there's 5 disks, there's only 1 read mechanism. That means that the accessing of any given disk may mean first selecting that disk to be

I recently sent the message below to this list, hoping I could get advise on improving Samba (v2.0.6) write performance from an OS/2 client (I got no responses). I subsequently ran the same tests from a Linux client using smbmount, also v2.0.6, and got the same results. The hardware config of the Linux client is the same as the OS/2 client below. Obviously, the problem is not

Hi all, I am trying to create simulated data for exploring reclassfication measures in a logistic setting with two continuous predictors and I would like to set the average population probability of outcome rather than the logistic beta0. Is there a way to find a beta0 that will generate the desired average population probability of outcome given x,y and their odds ratios? #Here is an

Hi, I added these lines to smb.conf: kernel op locks = false op locks = false strict locking = true so I could see some locks from the unix level. It worked sorta, I see the locks for big files (but not the locks I was expecting), but for little files it shows nothing: # ./lock_list /opt/testsambashare/mattest.doc # ./lock_list /opt/testsambashare/contents.doc 0 22086 W

Hello Samba, ???????, 30 ??????? 99, you wrote: sso> SAMBA Digest 2359 sso> For information on unsubscribing see http://lists.samba.org/ sso> Topics covered in this issue include: sso> 1) Re: Unix .TXT vs DOS .TXT files sso> by Gerry Creager N5JXS <gerry@cs.tamu.edu> sso> 2) Switching user share on NT and smbd spawning sso>

When an OS/2 or Win9x client logs into a (Linux) Samba v2.0.6 server the running smbd spawns a copy of itself. That second instance of smbd then handles all the shares for that client machine. In contrast, a Linux client which does multiple smbmounts (also Samba v2.0.6) will cause the server to spawn a copy of smbd for *each* smbmount mountpoint. This has the potential for using up a lot more

When I attempted to build Samba (v2.0.7) on a LynxOS (v3.1) box I was told that configure could determine my operating system. LynxOS, for those that don't know, is a Unix-like RTOS. It comes with a binary version of Samba, but a) it's old and b) it's not built for encrypted passwords which means I can't access it from WinNT. Can anyone advise me on what it would take to build

Hello all, We have a script that does a nightly backup of a windows server to a linux fileserver. The linux system uses smbclient to make a tarball of the share. I get this error when running smbclient: Domain=[OURSERVER] OS=[Windows 5.0] Server=[Windows 2000 LAN Manager] tar: dumped 56781 files and directories Total bytes written: 9800680960 write_data: write failure. Error = Connection

Hey guys, I've got another C7 problem I was hoping to solve. I installed appdynamics-php-agent-4.0.5.0-1.x86_64 on a C7.1 host. It's failing to communicate with it's controller on another host. And this is the interesting part. Whether or not I have SELinux enabled, I have apache reporting SELinux problems. [root at web1:~] #getenforce Permissive May 10 20:47:56 web1 python[25735]:

Dear R-dev, I would like to accelerate my R computation by using parallel OpenMP compilers (e.g from Pathscale) on a 2-processor AMD server and I would like to know whether R is a tread safe library. The main kernel of the OpenMP parallelization is a C SEXP function that performs the computational routine in parallel with: ******************* SEXP example(SEXP list, SEXP expr, SEXP rho) {

Hi, I have a glusterfs volume replicated on three nodes. I am planing to use the volume as storage for vMware ESXi machines using NFS. The reason for using tree nodes is to be able to configure Quorum and avoid split-brains. However, during my initial testing when intentionally and gracefully restart the node "ned", a split-brain/self-heal error occurred. The log on "todd"

Hello, I think there is an inconsistency in the handling of the compact form of the row.names attributes. When n is the number of rows of a data.frame, the compact form is c(NA_integer_,-n), as in: > d <- data.frame(x=1:10) > .Internal(inspect(d)) @104f174a8 19 VECSXP g0c1 [OBJ,NAM(2),ATT] (len=1, tl=0) @103a7dc60 13 INTSXP g0c4 [] (len=10, tl=0) 1,2,3,4,5,... ATTRIB: @104959380

I need help. For over a year I have been running SAMBA 2.05a under RedHat 6.1 (kernel 2.2.x) without problem. Then a couple days ago a power glitch crashed my system (UPS not powerful enough any more). Now SAMBA is not running. Here are the symptoms: As RedHat is starting up, both smbd and nmbd are listed as successful. /var/log/messages indicates: Dec 30 13:19:45 we-24-126-201-41 smb: smbd