search for: writing

-----Original Message----- From: Clark Mr Philip Sent: Friday, August 01, 2003 11:15 AM To: 'Jeremy Allison' Subject: RE: [Samba] winbind on Solaris 2.5.1 not working. Sure but its rather large and the funny thing is that it runs when it is trussed ( not correctly mind you) but not without it. the truss switches I use are aefo and as I said its large. The IP's and Hostnames are in

I''m on Fedora''s 3.8.5-201.fc18.x86_64. I tried to do some not-very-heavy I/O on my system (i.e. save kernel/sys.c in emacs) and it took about a minute. Everything went downhill from there. My system was basically idle at the time. (I have very little in the way of diagnostics because I couldn''t do much but hit the reset button after a couple of minutes.) On

Hi, I'm trying to manually create a rhel7 image using the qemu-img and virt-install commands. I'm re-testing a procedure I previously wrote with the new grub commands that a customer suggested we add in. This procedure is available at: http://file.bne.redhat.com/dnavale/docs/review/RH-guides/AG-020715/#sect-create-images As in the procedure, I'm able to run all steps successfully

...Compressing objects: 82% (29/35) Compressing objects: 85% (30/35) Compressing objects: 88% (31/35) Compressing objects: 91% (32/35) Compressing objects: 94% (33/35) Compressing objects: 97% (34/35) Compressing objects: 100% (35/35) Compressing objects: 100% (35/35), done. Writing objects: 0% (1/203) Writing objects: 1% (3/203) Writing objects: 2% (5/203) Writing objects: 3% (7/203) Writing objects: 4% (9/203) Writing objects: 5% (11/203) Writing objects: 6% (13/203) Writing objects: 7% (15/203) Writing objects: 8% (17/203) Writin...

Hi Rich, I'm not sure how far this helps as it mostly says 'No space left on device', but here's the output of the command you asked me to run: ➜ tmp /usr/bin/supermin --build -v -v -v --copy-kernel -f ext2 --host-cpu x86_64 /usr/lib64/guestfs/supermin.d -o /tmp/appliance.d supermin: version: 5.1.9 supermin: rpm: detected RPM version 4.11 supermin: package handler: fedora/rpm

...Compressing objects: 88% (45/51) Compressing objects: 90% (46/51) Compressing objects: 92% (47/51) Compressing objects: 94% (48/51) Compressing objects: 96% (49/51) Compressing objects: 98% (50/51) Compressing objects: 100% (51/51) Compressing objects: 100% (51/51), done. Writing objects: 0% (1/296) Writing objects: 1% (3/296) Writing objects: 2% (6/296) Writing objects: 3% (9/296) Writing objects: 4% (12/296) Writing objects: 5% (15/296) Writing objects: 6% (18/296) Writing objects: 7% (21/296) Writing objects: 8% (24/296) Writi...

Hi, I have doubt in executing raw.write tests using lxc-execute. When I execute it without lxc-execute it works fine i.e it performs raw.write testing. command :: root at nishant:/home/nishant/Desktop/samba-4.0.0alpha15# bin/smbtorture //localhost/ubuntu -Ubase%base_system raw.write This command works fine. We can see the o/p of this also,

On Mon, Sep 3, 2018 at 8:12 PM, Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > We have seen one similar issue with LPSS devices when BIOS assigns > device BARs above 4G (which is not the case here) and it turned out to > be misconfigured MTRR register or something like that. It may not be > related at all but it could be worth a try to dump out MTRR registers of

...cts: 94% (177/188) Compressing objects: 95% (179/188) Compressing objects: 96% (181/188) Compressing objects: 97% (183/188) Compressing objects: 98% (185/188) Compressing objects: 99% (187/188) Compressing objects: 100% (188/188) Compressing objects: 100% (188/188), done. Writing objects: 0% (1/1085) Writing objects: 1% (11/1085) Writing objects: 2% (22/1085) Writing objects: 3% (33/1085) Writing objects: 4% (44/1085) Writing objects: 5% (55/1085) Writing objects: 6% (66/1085) Writing objects: 7% (76/1085) Writing objects: 8% (87/10...

...Compressing objects: 62% (10/16) Compressing objects: 68% (11/16) Compressing objects: 75% (12/16) Compressing objects: 81% (13/16) Compressing objects: 87% (14/16) Compressing objects: 93% (15/16) Compressing objects: 100% (16/16) Compressing objects: 100% (16/16), done. Writing objects: 1% (1/93) Writing objects: 2% (2/93) Writing objects: 3% (3/93) Writing objects: 4% (4/93) Writing objects: 5% (5/93) Writing objects: 6% (6/93) Writing objects: 7% (7/93) Writing objects: 8% (8/93) Writing objects: 9% (9/93) Writing objects: 1...

...Compressing objects: 93% (92/98) Compressing objects: 94% (93/98) Compressing objects: 95% (94/98) Compressing objects: 96% (95/98) Compressing objects: 97% (96/98) Compressing objects: 98% (97/98) Compressing objects: 100% (98/98) Compressing objects: 100% (98/98), done. Writing objects: 0% (1/288) Writing objects: 1% (3/288) Writing objects: 2% (6/288) Writing objects: 3% (9/288) Writing objects: 4% (13/288) Writing objects: 5% (15/288) Writing objects: 6% (18/288) Writing objects: 7% (21/288) Writing objects: 8% (24/288) Writi...

Hello, I'm compiling samba 4.2.2 from source on a Linux From Scratch (LFS) system. Packages I have installed on the system are mixed from various versions of LFS (7.6 through 7.9). This is a 64-bit CPU running 32-bit OS: # uname -a Linux pjnas 4.4.4-asrockN3150-001-1_pj #1 SMP Fri Mar 4 22:40:03 CET 2016 i686 GNU/Linux Samba compiles fine, but a few selftests fail. The ones I'm worried

Hi, Has anyone any ideas what is causing my smbd processes to crash? The files being accessed via samba are on an NFS mounted directory. In the samba log file I am getting the following errors: [2004/12/03 16:31:33, 0] smbd/oplock.c:request_oplock_break(1026) request_oplock_break: no response received to oplock break request to pid 2181 9 on port 53336 for dev = 2c00002, inode = 297939333

Full_Name: Kenneth Cater Version: 2.9.1 OS: Linux x86_64 Submission from: (NULL) (171.159.192.10) It appears that R closes my connection to the Netezza device before the Netezza has completed its return of data, below are two files clean_test.log which tracks the systems call made when running the test.r file, and clean_test.out which is the output generated when test.r is executed. Notice how

...oking for. Any ideas in debugging this? I do have ACLs enabled but this was happening before I enabled them too. My understanding was that the network profile just gets checked against the local one, and any changes are written to the server upon logout. It almost looks like, for him, it is writing his entire profile back to the network every time he logs out. It certainly feels like it! geteuid32() = 1011 write(30, " change_to_user: Skipping user "..., 54) = 54 time(NULL) = 1100038555 geteuid32()...

On Tue, Sep 04, 2018 at 09:52:02AM +0800, Daniel Drake wrote: > # cat /proc/mtrr > reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable > reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable > reg02: base=0x090000000 ( 2304MB), size= 256MB, count=1: uncachable > reg03: base=0x08c000000 ( 2240MB), size= 64MB, count=1: uncachable > reg04:

My smbpasswd command to join the WIN2k domain fails with a session set up 21 error then 'NT_STATUS_LOGON_FAILURE ) = 54'. I included the last few lines of the strace output below. Maybe it is enough for someone to tell me what the problem between the PDC and my REDHAT 8.0 2.4.19 with SAMBA 2.2.7a-2 is. Thanks in advance. rite(1, "smb_bcc=38\n", 11smb_bcc=38 ) = 11

We have several DELL R900 server with PERC 6/E adapter in it. O.S. is CENTOS 5.5. recently one of server continue pop-up messages on /var/log/message for switch status between "write back" and "write through". ============================== Dec 6 08:09:31 host01 Server Administrator: Storage Service EventID: 2189 The controller write policy has been changed to Write Back.:

Hey guys, I''m having a little trouble working out partials. I have successfully made a partial work in my list.rhtml, but as I see it on the 15min introductry video. They guy uses one partial on multipul pages. At the moment I am trying this in my show.rhtml, I write <%= render :partial => "journal" %> and I get this. NoMethodError in Write#show > > Showing

Hi. I have a RHEL server that has some errors in dmesg , what do they mean, how do I fix them ? mtrr: type mismatch for f9000000,800000 old: write-back new: write-combining mtrr: type mismatch for f9000000,1000000 old: write-back new: write-combining mtrr: type mismatch for f9fe0000,10000 old: write-back new: write-combining mtrr: type mismatch for f9fc0000,20000 old: write-back new: