similar to: how to troubleshoot ssh multiplexing hanging issues?

> This means there was an error (some function returned -1), but the > error message was not set. Could you capture the backtrace when this > happens? It's hard to find the exact point, but going function and > checking what returns -1 should do. Assuming by "backtrace" you mean the strace output, I went to the end of the file, and then did a reverse search for -1; here

Commit-ID: 8b44cc180f664532821211e8261534b0c9e6c01c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=8b44cc180f664532821211e8261534b0c9e6c01c Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 14 Jan 2023 02:15:10 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 15 Jan 2023 21:28:18 +0100 [klibc] time: Use clock_* system

I''m continuing to investigate the usage of rdtsc in userspace and whether there are programs "out there" that use it "unsafely" that might randomly break under Xen if rdtsc is not emulated, e.g. across a migration. Some have argued that nobody should use rdtsc and any programs that use rdtsc directly are "fundamentally broken" so the default for rdtsc

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Estimada comunidad, tengo el siguiente problema: 1. tengo un data.frame con varias columnas, algunas numericas, otras son variables categoricas 2. necesito hacer un calculo simple sobre este data.frame (un promedio ponderado de los valores de la columna 7), pero solo para las filas que cumplan ciertos criterios 3. en ocasiones ninguna de las filas

Returning EMFILE (process has too many open files) is incorrect to indicate a port is already open by another process. Use EBUSY for that. This does change what we report to userspace, but I believe userspace can look at it this way: it gets EBUSY, a new error code, instead of EMFILE. It's still an error, and that's not changing. Reported-by: Mateusz Guzik <mguzik at redhat.com>

Returning EMFILE (process has too many open files) is incorrect to indicate a port is already open by another process. Use EBUSY for that. This does change what we report to userspace, but I believe userspace can look at it this way: it gets EBUSY, a new error code, instead of EMFILE. It's still an error, and that's not changing. Reported-by: Mateusz Guzik <mguzik at redhat.com>

Sadly, I'm back with another issue. I can do a "system list --all" just fine; however, if I attempt to start the machines, I get back: maas@Bill-MAAS-cc:~$ strace -s 1024 -f -o /tmp/asdfasdf.log virsh -c vbox+ssh://gbadmin@10.20.0.1/system start PXE-client-07 error: Failed to start domain PXE-client-07 error: An error occurred, but the cause is unknown Log files on both client

The latest version that Western Digital has shipped with the My cloud devices accesses the disk about twice a minute. The access to /dev/sda2 is causing the system to keep the disk from going into standby mode. I don't understand the call to quotactl every minute when no one is trying to access the share. An strace of one of the processes shows the following: poll([{fd=13,

On 2013-08-03 01:41, Darren Tucker wrote: > On Sat, Aug 3, 2013 at 5:58 PM, Damien Miller <djm at mindrot.org> wrote: >>> Looking at failure logs - this is what's killing it: >>> clock_gettime: Invalid argument > [...] >> Maybe these platforms lack CLOCK_MONOTONIC? Darren, perhaps we should >> wrap clock_gettime and have a fallback for

https://bugzilla.mindrot.org/show_bug.cgi?id=1557 Summary: ssh multiplexing does not fall back to new connection when server refuses muxd session Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh

I got more information ,after enable log_level to 10: ``` push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 3 push_conn_ctx(0) : conn_ctx_stack_ndx = 2 setting sec ctx (0, 0) - sec_ctx_stack_ndx = 3 Security token: (NULL) UNIX token of user 0 Primary group is 0 and contains 0 supplementary groups Adding cache entry with key=[ACCT_POL/password history] and timeout=[Thu Jan 1 03:00:00 AM 1970 MSK]

On 01/24/16 12:29 PM, Erik de Castro Lopo wrote:> Dave Yeo wrote: > >> After this the build dies with, >> util.c: In function 'benchmark_function': >> util.c:124:17: error: 'CLOCK_PROCESS_CPUTIME_ID' undeclared (first use >> in this function) >> clock_gettime (CLOCK_PROCESS_CPUTIME_ID, &start) ; >> >> Would using

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This reverts commit 8078db789a92b10ff6e2d713231b5367e014c53b. The reverted patch caused opening of ports to fail for rproc_serial. In probe guest_connected was set to true, but port_fops_open() fails with -EMFILE if guest_connected already is true. Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi

From: Sjur Br?ndeland <sjur.brandeland at stericsson.com> This reverts commit 8078db789a92b10ff6e2d713231b5367e014c53b. The reverted patch caused opening of ports to fail for rproc_serial. In probe guest_connected was set to true, but port_fops_open() fails with -EMFILE if guest_connected already is true. Signed-off-by: Sjur Br?ndeland <sjur.brandeland at stericsson.com> --- Hi

?Hello everybody, I'm working on the "Use difftime for time comparison" bug (#313634). Charles directed me to the other one "Use monotonic clock for monitoring" attended to by Baruch; I believe that's very good idea, however I'd use a bit more encapsulated & general approach: 1/ I'd create an opaque timer type and its get/set/cmp/inc/dec etc interface

configure uses clock_gettime to check whether -lrt is needed - and don''t check other functions. With glibc 2.17 clock_gettime is part of libc, so use timer_gettime instead, which is in -lrt in old and new versions of glibc. Signed-off-by: Olaf Hering <olaf@aepfle.de> --- configure | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure b/configure index

Sure. ``` [global] workgroup = EXAMPLE server string = dns proxy = no interfaces = eth0 bind interfaces only = yes log file = /var/log/samba/log.%m max log size = 1000 # new options log level = 5 netbios name = FILES #panic action = /usr/share/samba/panic-action %d server role = STANDALONE SERVER local master = no security = user encrypt passwords =

Free Nokia 3360, 3500 Night And Weekend Minutes, Free Nationwide Long Distance ------------------------------------------------- With Cingular's Home 400 Plan for Just $39.99 A Month You get: - 400 Minutes Minutes Per Month - Call Forwarding - Call Waiting - 3-Way Messaging And THe Nokia 3360 Features - 210 Minutes Of Talk Time - SMS 2-way Text Messaging - Predicitive Text

Hi, i just want to ask whether somebody else has this problem of mine and if it can be solved. Many of my ( 30+ ) puppet installation freeze up after some time. The process is waiting for some private futex, but it stays like that forever. This is what strace looks like when the problem occures: [pid 29173] futex(0x3d35ce7a84, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 43406739,

On Tue, 2015-11-24 at 17:48 +0300, Yuriy Tabolin wrote: > Thanks for answer. I am very sad to see that. > I had examined samba behavior with tracer and had seen too many poll, > fcntl and stat system calls by samba task[ldapsrv] process > > Elapsed Times for PID 1423, > > SYSCALL TIME (ns) > dup 2653 > flock