search for: sessios

Hi, I have installed mongrel on Vista and my app runs *really* slowly. Checking Net stats in firebug shows each html request for the assets taking ~1s. Running same app on XP is fine and running as webrick on vista is fine too. There is also a strange pattern : each of the http requests to mongrel take marginally more than 1s, e.g. 1.04, 1.05 on webrick each request takes ~ 4-40ms. Very odd

Hi!!! Samba greate Members I installed Samba version 2.2.5 on Redhatlinux.8 to make network with windows 2000. Telenet on port 139 is working ok beween the linux and windows machine. I can see workgroup Icon on windows machine. when I click on to access linux machine, it comes with a message stating that workgroup is not accessible. I try the following command on linux. #smbclient -L srver1

...create or include this machine in the smbpasswd ? 2: I don't want that the samba storaged the profiles for each user on the server. I want that when the user join the the domain the profile be storaged in that machine hard disk and no in the server. I try to do this, removing all profiles sessios from smb.conf but when i do this when the user logged in domain the machine display a message that the machine could not acess a profile on the server, so the profile will be storaged localy, but after this the machine display other message that it get not sucessful creating a local profile and...

Hello, When i have a "Hangup" in my dialplan (extensions.conf) the RFC says to terminate the session is to send a BYE request to UA. After tracing the traffic on port 5060 UDP i recognized that my asterisk is NOT sending a BYE request to it's peer, so the peer doen't know to end the session and continues to send RTP packages to me. Does anyone know how to fix this? Here's

I''m getting strange data back from my worker whenever I run our rails app with more than one dispatcher under lighttpd. just to give some info on what the app does: user submits data to rails app. rails app hands off data to worker, which goes and does it''s thing, storing results in an array of response objects (the array is an attribute of the worker). the response object

I'm having problems still with password authentication for 1.9.18p7. Samba only recognizes the root password only!!!! I thought password authentication was fixed in version 1.9.18p5. Anyway, here's output of the problems I'm facing: After starting smb and nmb using root's ID the following test was successful: 3 root@Sun-E3000:/usr/local/samba/private ==> smbclient -L

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

Hi all, With the help of Tomas, I was able to track the issue down: Prior to R v3.6.0 the parallel package passes an uninitialized variable as the file descriptor argument to the close system call. In my particular R session this uninitialized variable (reproducibly) was holding the value 7, which corresponded to the file descriptor of the write end of the pipe the second child would use to

Hi all, With the help of Tomas, I was able to track the issue down: Prior to R v3.6.0 the parallel package passes an uninitialized variable as the file descriptor argument to the close system call. In my particular R session this uninitialized variable (reproducibly) was holding the value 7, which corresponded to the file descriptor of the write end of the pipe the second child would use to

Hi Andreas, thank you very much, good job finding it was EBADF. Now the question is why the pipe has been closed prematurely; it could be accidentally by R (a race condition in the cleanup code in fork.c) or possibly by some other code running in the same process (maybe the R program itself or some other code it runs). Maybe we can take this off the list and come back when we know the cause