search for: keyboardinterrupt

...and then at RPy. It is not yet a Debian package as it had the odd problem here or there -- initially an Atlas interaction, currently something with long_jump() which cannot be found when R's dynamic library is loaded. [1] It is called R_eval.c: /* Abort the current R computation and signal a KeyboardInterrupt exception */ void interrupt_R(int signum) { interrupted = 1; jump_now(); } By commenting it out, the package builds and is usable (modulo the absence of interrupt handling, I suppose). Could someone give me a pointer or suggestion as to what the replacement for jump_now() would be?...

...t call last): File "/usr/sbin/xend", line 110, in ? sys.exit(main()) File "/usr/sbin/xend", line 102, in main return daemon.stop() or daemon.start() File "usr/lib64/python2.4/site-packages/xen/xend/server/SrvDaemon.py", line 181, in start s = r.read() KeyboardInterrupt Can some help with the xend hang problem. Thanks a lot! -- View this message in context: http://xen.1045712.n5.nabble.com/Xend-hangs-on-starting-time-tp4340029p4340029.html Sent from the Xen - User mailing list archive at Nabble.com. _______________________________________________ Xen-users mai...

...n be skipped on errors, but we must log a detailed error message before we fallback to https. Also bare except should be used only in one case, when you do: try: ... except: cleanup raise If you don't raise, you should use Exception. Otherwise you will swallow KeyboardInterrupt, SystemExit, and GeneratorExit and any other user defined exceptions inheriting from BaseException. Also it will be easier to maintain this if this will be in a separate function like: def find_host(): read hardware id or return None... get hosts from engine or return None... return t...

...oubleshootd object_path=/org/fedoraproject/Setroubleshootd interface=org.fedoraproject.SetroubleshootdIface 2011-11-01 15:11:55,119 [server.DEBUG] dbus __init__ /org/fedoraproject/Setroubleshootd called 2011-11-01 15:12:05,119 [server.DEBUG] received signal=14 2011-11-01 15:12:05,119 [server.DEBUG] KeyboardInterrupt in RunFaultServer 2011-11-01 15:12:05,119 [database.DEBUG] writing database (/var/lib/setroubleshoot/audit_listener_database.xml) modified_count=0 ------------------------ I've found this resource, http://docs.fedoraproject.org/en-US/Fedora/13/html/SELinux_FAQ/index.html#id4621954, but have no...

...;, "credits" or "license" for more information. >>> import gi Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named 'gi' >>> quit Use quit() or Ctrl-D (i.e. EOF) to exit >>> KeyboardInterrupt >>> >>> exit Use exit() or Ctrl-D (i.e. EOF) to exit >>> Sincerely AndyBe

On 03/04/2015 09:45 PM, Dave McGuire wrote: > On 03/04/2015 03:37 PM, Oliver Welter wrote: >> Am 04.03.2015 um 21:03 schrieb Dave McGuire: >>> Am 04.03.2015 um 20:12 schrieb Michael Orlitzky: >>>> Please add [DNSBL] support to iptables instead of Dovecot. It's a waste of >>>> effort to code it into every application that listens on the network.

...curses.halfdelay(int(sleeptime * 10)) + sleeptime = 3 + try: + c = screen.getkey() + if c == 'x': + drilldown = not drilldown + update_drilldown() + if c == 'q': + break + except KeyboardInterrupt: + break + except curses.error: + continue + +def batch(stats): + s = stats.get() + time.sleep(1) + s = stats.get() + for key in sorted(s.keys()): + values = s[key] + print '%-22s%10d%10d' % (key, values[0], values[1]) + +def log(stats)...

To help in vhost analyzing, the following series adding basic tracepoints to vhost. Operations of both virtqueues and vhost works were traced in current implementation, net code were untouched. A top-like satistics displaying script were introduced to help the troubleshooting. TODO: - net specific tracepoints? --- Jason Wang (2): vhost: basic tracepoints tools: virtio: add a

To help in vhost analyzing, the following series adding basic tracepoints to vhost. Operations of both virtqueues and vhost works were traced in current implementation, net code were untouched. A top-like satistics displaying script were introduced to help the troubleshooting. TODO: - net specific tracepoints? --- Jason Wang (2): vhost: basic tracepoints tools: virtio: add a

v1 was here: https://www.redhat.com/archives/libguestfs/2018-June/msg00099.html v2: - Just fixes the two problems noted in the review of the previous version. Rich.

Recent debugging on vhost net zerocopy shows the need of tracepoints. So to help in vhost{net} debugging and performance analyzing, the following series adding basic tracepoints to vhost. Operations of both vhost and vhost_net were traced in current implementation. A top-like satistics displaying script were introduced to help the troubleshooting: vhost statistics vhost_virtio_update_used_idx

Recent debugging on vhost net zerocopy shows the need of tracepoints. So to help in vhost{net} debugging and performance analyzing, the following series adding basic tracepoints to vhost. Operations of both vhost and vhost_net were traced in current implementation. A top-like satistics displaying script were introduced to help the troubleshooting: vhost statistics vhost_virtio_update_used_idx

...exception occurred: Traceback (most recent call last): File "/usr/sbin/samba_dnsupdate", line 883, in <module> creds = get_credentials(lp) ^^^^^^^^^^^^^^^^^^^ File "/usr/sbin/samba_dnsupdate", line 188, in get_credentials os.unlink(ccachename) KeyboardInterrupt root at dc:~# [/output] As "kinit for DC$@AUGUSTA.domain.tld failed" I run: root at dc:~# kinit administrator kinit: KDC f?r Realm ?AUGUSTA.DOMAIN.TLD? kann nicht gefunden werden bei Anf?ngliche Anmeldedaten werden geholt. root at dc:~# Cheers, Torsten

Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently in lit you can set a global timeout for all of the tests but

Am 04.01.2024 um 13:28 schrieb lists--- via samba: > Am 04.01.2024 um 12:36 schrieb Rowland Penny via samba: >> On Thu, 4 Jan 2024 12:12:57 +0100 >> lists--- via samba <samba at lists.samba.org> wrote: >> >>> Am 04.01.2024 um 11:55 schrieb Rowland Penny via samba: >>>> On Thu, 4 Jan 2024 11:19:17 +0100 >>>> lists--- via samba <samba at