search for: 13s

...o and OpenLinux eBuilder linux-2.2.14-12S OpenLinux eDesktop 2.4 All packages previous to linux-2.2.14-8 OpenLinux Server 3.1 All packages previous to linux-2.4.2-13S OpenLinux Workstation 3.1 All packages previous to linux-2.4.2-13D 3. Solution Workaround none The proper solution is to upgrade to the latest packages. 4. OpenLinux 2.3 4.1 Location of Fixed Packages The upgrade...

...Package ----------------------------------------------------------- OpenLinux 2.3 All packages previous to linux-2.2.10-14 OpenLinux eServer 2.3.1 All packages previous to and OpenLinux eBuilder linux-2.2.14-13S OpenLinux eDesktop 2.4 All packages previous to linux-2.2.14-9 OpenLinux Server 3.1 All packages previous to linux-2.4.2-14S OpenLinux Workstation 3.1 All packages pre...

...Takes about 6 seconds to run if llvm-symbolizer isn't present 13 seconds with debug info 1m30s with split DWARF/Fission So, couple of things: 1) llvm-symbolizer is /really slow/ on split-dwarf files... 2) Why are stack traces even attempted when using bugpoint? Even if it's just the 6->13s slowdown, that's still halving the speed of bugpoint in the presence of llvm-symbolizer+debug info (I didn't test in the presence of llvm-symbolizer but no debug info)? It doesn't look like the LLVM tools have any way to disable symbolization/stack trace/crash handling. Is that correct...

...e size of the debug IR is 162M vs 39M no-debug. Both profiles look relatively similar with the exception of bit code writer and verifier taking a larger share in the -g case. Looking at InstCombine, it’s 23% slower. One notable thing is that CallInst takes significantly larger share with -g: 5s vs 13s, which translates to about half of the InstCombine slowdown. Need to understand why. ComputeKnownBits takes about the same time and other visitors have elevated times I would guess due to the need to propagate debug info. > >> I wanted to see what transformations InstCombine actually pe...

...ug IR is 162M vs 39M no-debug. Both profiles look relatively similar with the exception of bit code writer and verifier taking a larger share in the -g case. >> >> Looking at InstCombine, it’s 23% slower. One notable thing is that CallInst takes significantly larger share with -g: 5s vs 13s, which translates to about half of the InstCombine slowdown. Need to understand why. > > Ah, it’s all those calls to @llvm.dbg.* functions. I’ll explore if they can be safely ignored by InstCombine. > > I took a look and saw no immediate problems, also discussed with David Majnemer on...

...systemctl start vncserver@:3.service # systemctl -l status vncserver@:3 ? vncserver@:3.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncserver at .service; enabled; vendor preset: disabled) Active: failed (Result: resources) since Thu 2017-05-25 12:31:13 EDT; 13s ago Process: 5173 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i (code=exited, status=0/SUCCESS) Process: 5170 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) May 25 12:31:10 homebase.home.htt systemd[1]: Sta...

...sent >> 13 seconds with debug info >> 1m30s with split DWARF/Fission >> >> So, couple of things: >> 1) llvm-symbolizer is /really slow/ on split-dwarf files... >> 2) Why are stack traces even attempted when using bugpoint? Even if it's >> just the 6->13s slowdown, that's still halving the speed of bugpoint in the >> presence of llvm-symbolizer+debug info (I didn't test in the presence of >> llvm-symbolizer but no debug info)? >> >> It doesn't look like the LLVM tools have any way to disable >> symbolization...

On Thu, Apr 7, 2016 at 1:26 PM, Subscriber <ml-lists at agoris.net.ua> wrote: > Hello FrancisM, > > Thursday, April 7, 2016, 8:03:38 AM, you wrote: > > > > I tried last night and it seems like the vlans that I created is failing > to > > bring-up. So this is what Im doing > > > in my DATA trunk port at my HomeLab Im doing this > > > 2 port

...bit machine is there not a 10% chance of *each* random 32-bit int "pointing" into your heap, i.e. a false positive? I just did a simple test here (create an array with 1M random 32-bit ints and then allocate blocks n=1..2^16 of size n bytes) and Boehm's conservative GC sometimes takes 13s and other times runs out of memory after several minutes. It even complains about the "Repeated allocation of very large block (appr. size 65536)". Is 64kb really "very large" today? I think not. Performance is certainly an important reason to implement an accurate collector...

...Debian 8 Jessie with software RAID of a similar fashion as well. That would unexpectably prevent the system from booting past something like (I copied it from the working setup), I ran it over night, so it was actually about 16 hours: "A start job is running for dev-mapper-vg0\x2droot.device (13s / 1min 30s)" Can it be just some kind of a scan, which takes so long? The current throughput based on time (16 h) and capacity (3 TB) would be about 50 MBps. (Those drives can be pretty slow when writing, dd showed about 30 MBps, the write cache is off.) This is actually repeatable. If I u...

...he second. root at dtdc03:~# systemctl restart apparmor.service root at dtdc03:~# systemctl status apparmor.service ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: active (exited) since Sun 2016-10-16 12:14:58 CDT; 13s ago Docs: man:systemd-sysv-generator(8) Process: 2197 ExecStop=/etc/init.d/apparmor stop (code=exited, status=0/SUCCESS) Process: 1547 ExecReload=/etc/init.d/apparmor reload (code=exited, status=123) Process: 2211 ExecStart=/etc/init.d/apparmor start (code=exited, status=0/SUCCESS) Oct...

----- Message d'origine ---- > De : vitamin <wineforum-user at winehq.org> > ? : wine-users at winehq.org > Envoy? le : Samedi, 3 Mai 2008, 5h01mn 13s > Objet : [Wine] Re: Supreme Commander Forged Alliance > > > Harkainos wrote: > > this is the first time i have heard of it actually 'breaking' wine. > > Said deaf person about birds singing outside his window... > Where are you "listening" to such...

I never figured out how I should tread error 13 from rsync, "Problem with diagnostics". My question is, is this a transient or permanent error? Or how seriously did something go wrong when rsync returns 13? I don't get much smarter reading the rsync source either. For reference this is for Lsyncd, which watches files with inotify and uses rsync to transmit changes to a slave. It

...its the same configuration as what I have done earlier. [root at server network-scripts]# systemctl status network.service -l ? network.service - LSB: Bring up/down networking Loaded: loaded (/etc/rc.d/init.d/network) Active: failed (Result: exit-code) since Tue 2015-04-07 17:19:00 SGT; 1min 13s ago Docs: man:systemd-sysv-generator(8) Process: 48732 ExecStop=/etc/rc.d/init.d/network stop (code=exited, status=0/SUCCESS) Process: 49302 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE) Apr 07 17:17:28 server network[49302]: [ OK ] Apr 07 17:17:29 server netw...

...vice > > # systemctl -l status vncserver@:3 > ? vncserver@:3.service - Remote desktop service (VNC) > Loaded: loaded (/etc/systemd/system/vncserver at .service; enabled; > vendor preset: disabled) > Active: failed (Result: resources) since Thu 2017-05-25 12:31:13 > EDT; 13s ago > Process: 5173 ExecStart=/usr/sbin/runuser -l root -c > /usr/bin/vncserver %i (code=exited, status=0/SUCCESS) > Process: 5170 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i > > /dev/null 2>&1 || : (code=exited, status=0/SUCCESS) > > May 25 12:31:10 homeba...

...systemctl restart apparmor.service >> root at dtdc03:~# systemctl status apparmor.service >> ● apparmor.service - LSB: AppArmor initialization >> Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) >> Active: active (exited) since Sun 2016-10-16 12:14:58 CDT; 13s ago >> Docs: man:systemd-sysv-generator(8) >> Process: 2197 ExecStop=/etc/init.d/apparmor stop (code=exited, >> status=0/SUCCESS) >> Process: 1547 ExecReload=/etc/init.d/apparmor reload (code=exited, >> status=123) >> Process: 2211 ExecStart=/etc/init.d/apparmor...

...I have done > earlier. > > [root at server network-scripts]# systemctl status network.service -l > ? network.service - LSB: Bring up/down networking > Loaded: loaded (/etc/rc.d/init.d/network) > Active: failed (Result: exit-code) since Tue 2015-04-07 17:19:00 SGT; > 1min 13s ago > Docs: man:systemd-sysv-generator(8) > Process: 48732 ExecStop=/etc/rc.d/init.d/network stop (code=exited, > status=0/SUCCESS) > Process: 49302 ExecStart=/etc/rc.d/init.d/network start (code=exited, > status=1/FAILURE) > > Apr 07 17:17:28 server network[49302]: [...

Hello, When I define *unix charset = ISO-8859-1* in *smb.conf*, it does not work. When I comment it, the share works fine. However, we need to define the charset... When unix charset is Here is the global section of smb.conf [global] workgroup = COMPANY realm = COMPANY.COM security = ADS winbind use default domain = true winbind offline logon = true idmap config * :

...s is on Centos 7.4 I see this when I start smbd : [root at zinc samba]# systemctl status smb.service * smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2019-01-14 15:19:01 EST; 13s ago Docs: man:smbd(8) man:samba(7) man:smb.conf(5) Process: 9214 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE) Main PID: 9214 (code=exited, status=1/FAILURE) Status: "daemon failed to start: Samba cannot s...

Hi there, I'm running rsync on an nslu2 (using nslu2-linux) and it keeps failing with return code 13. The man page doesn't give a good description of what this means ("Errors with program diagnostics") so could someone give me a clue. as to what diagnostics rsync is running and reasons why they might be failing? The only magic to note is the machine only has 32MB of ram so low