Displaying 11 results from an estimated 11 matches for "prcesses".
Did you mean:
processes
2006 Aug 07
3
RC6 startup failure: "Login prcess died too early"
Greetings.
I have been running Dovecot-1.0rc2 on a test server for the last couple
of weeks. No problems. However, when I installed RC6 this morning,
Dovecot refused to launch completely. Here's the relevant snippet from
/var/log/maillog:
Aug 7 10:08:36 mercury dovecot: Dovecot v1.0.rc6 starting up
Aug 7 10:08:37 mercury dovecot: Login process died too early - shutting
down
Aug 7
2006 Sep 01
2
makeSOCKcluster
Hi,
I am a newbie to R and trying to implement parallelism in R. I am currently using R-2.3.1, and Cygwin to run R on Windows xp.
ssh and all are working fine,
When I try to create a socket connection as
makeSOCKcluster(c("localhost","localhost")),
it just waits for the other prcess on localhost to get created and respond. But this other process is
2007 Jun 04
2
backgroundrb scheduler
...cheduled actions aren''t ran at all and if
they do, the process stays around forever. I''m using the backgroundrb as a
nightly cron to run some accounting operations.
questions:
1. How can I have the process destroyed after the worker completes?
2. Any idea on what would keep the prcesses from being started. The
backgroundrb.log is empty. I''ll post the backgroundrb_server.log
3. Is backgroundrb even the right choice for nightly rails crons?
Thanks for any help, and of course for backgroundrb!
Charlie
This is the backgroundrb_server.log for last night. It called and r...
2005 Jun 06
2
PHP mcrypt
Hi,
Could someone tell me how I'd go about compiling php with mcrypt support
from src.rpm?
ie. configure -with-mcrypt[=DIR]
Is it just a matter of calling
rpmbuild --rebuild src.rpm --with=mcrypt
?
Cheers,
MaZe.
2007 Aug 14
1
makeSOCKcluster
Hi,
I am attempting to implement a mixed (windows/linux) snow sockets
parallelism in R, but am running into difficulties similar to a post made
Aug 31, 2006 under the same subject heading. I feel like I may be one or
two non-obvious steps away from getting it all working, but I'm stuck. If
anyone can shed some light on this (I believe Prof. Tierney stated that he
has successfully run a
2019 Apr 30
2
[External] Re: Background R session on Unix and SIGINT
Unfortunately --interactive also makes the session interactive(),
which is bad for me, as it is a background session.
In general, I don't want the interactive behavior, but was wondering
if I could send as SIGINT to try to interrupt the computation of the
background process, and if that does not work, then I would send a
SIGKILL and start up another process. It all works nicely, except for
2013 Jul 25
0
[PATCH v3 4/9] virtio: console: fix raising SIGIO after port unplug
SIGIO should be sent when a port gets unplugged. It should only be sent
to prcesses that have the port opened, and have asked for SIGIO to be
delivered. We were clearing out guest_connected before calling
send_sigio_to_port(), resulting in a sigio not getting sent to
processes.
Fix by setting guest_connected to false after invoking the sigio
function.
CC: <stable at vger.ker...
2007 Nov 20
1
How to receive manager events from commands made by an AGI script?
Hi all,
I'm new on this list, my name is Noel. :D
I developed a system using AGI and now I'm trying to develop a system
that listen events fired by Manager API. I have realized that I don't
receive events from commands made by an AGI script like "play a file"
or "record a file".
Is there a way to receive such events?
Sorry about the poor English.
Thanks in
2019 May 01
0
[External] Re: Background R session on Unix and SIGINT
Gabor,
I think you're talking about two independent things. You can interrupt the computation, no question about that. It's just that if you send an interrupt while you're *not* doing any computations, it will be signaled but not raised until the interrupts are checked since there is no one to check it. This goes back to my original response - the interactive REPL calls
2013 Jul 25
18
[PATCH v3 0/9] virtio: console: fixes for bugs and races with unplug
Hello,
This series fixes a few bugs and races with port unplug and the
various file operations: read(), write() and close().
I started coding up an alternative locking mechanism based on the
discussion earlier in this series, but some of what we already have
has to remain, and the new code is sufficiently different, so I'd
rather it bakes for a while, and I ensure there are no regressions
2013 Jul 25
18
[PATCH v3 0/9] virtio: console: fixes for bugs and races with unplug
Hello,
This series fixes a few bugs and races with port unplug and the
various file operations: read(), write() and close().
I started coding up an alternative locking mechanism based on the
discussion earlier in this series, but some of what we already have
has to remain, and the new code is sufficiently different, so I'd
rather it bakes for a while, and I ensure there are no regressions