search for: prcess

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

...o 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 not created. To debug, I put print statements in the "snow " file in library\snow\r of R after every statement that comes under Socket Implementation. I realized that it does the execution till system(a<-pas...

...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...

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.

...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 not created. To debug, I put print statements in the "snow " file in library\snow\r of R after every statement that comes under Socket Implementation. I realized that it does the execution till system(a<-p...

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

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.k...

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

...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 R_CheckUserInterrupt(), but the straight stdin-prcessing doesn't (since it's expected to be a script, not interactive prompt). If you just want to clear interrupts before next processing you can either just run R_CheckUserInterrupt() explicitly, or on R side do anything that does that, e.g. to take your example "tryCatch(Sys.sleep(0), int...

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

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