similar to: sessions with new threads

Hi, My persistent variables (_XXX or __XXX) don't persist when I dial a Local extension. I'm doing a forked dial where the other channel is SIP and the other Local. Is this a known problem? Using Asterisk 1.0.9. My purpose is to fork the original call to two destinations: One going to an "internal" SIP phone and the other going to an external PSTN gateway (also using SIP). So

Hello, We are developing in Rails 2.1.0 and serving the files with mongrels behind Apache. We are using SqlSessionStore. Recently I noticed that when logging into our site using IE7 the session doesn''t persist in some situations, and persists when it shouldn''t. For instance when I log in my info is maintained when visiting certain pages, but disappears on others. The info never

Okay, I know this is going to sound like a terrible idea to many of you, but please bear with me for just a moment. I want to be able to have a few of my models optionally persist to my session instead of to my database under certain circumstances. Basically I want to be able to provide a limited demo version of my site to potential new users without polluting my db with all their fooling around.

Hi, There doesn''t seem to be any previous posts about this problem, I must be setting things up wrongly at very basics... Firstly, the problem... I can''t get session[] to persist with active_record_store. I enabled (config.action_controller.session_store = :active_record_store) in environment.rb and created the sessions table at my MySQL database. When I do a session[:blah] =

Kevin P. Fleming wrote: > Falck Kenneth wrote: > > My persistent variables (_XXX or __XXX) don't persist when I dial a > > Local extension. I'm doing a forked dial where the other channel is > > SIP and the other Local. Is this a known problem? Using Asterisk 1.0.9. > > Variable inheritance is a CVS HEAD feature, it is not > supported in 1.0.x. Thanks, I

I''m trying to get the configuration done for sessions but I can''t seem to find any documentation on how to do it beyond the merest of basics. I would rather have something that would NOT persist a marshalled object to the database since that''s just not something I want to do. I want to be able to read the data for one. But there''s really nothing to

http://bugzilla.mindrot.org/show_bug.cgi?id=1330 Summary: RFE: 'ControlPersist' support -- automatically fork and leave ControlMaster behind as a d?mon Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component:

If you have a plugin which either creates background threads itself or uses a library that creates background threads, it turns out you cannot create these in .get_ready (or earlier). The reason is that nbdkit forks when either daemonizing itself or using the --run option, and fork cancels all the background threads in the child process (the daemonized or captive nbdkit). The only good solution

I just finished rebuilding my server after a penetration last week which left my filesystem in shambles. I've gotten most everything running again better than before with one exception. sshd doesn't work as well as it used to and I'm not sure why, I'm including a sanitized log snippet, hopefully someone can point out my stupidity for me... If I open a putty session from another

Hello all, I am trying to create a corosync/pacemaker cluster using CentOS 6.0. However, I'm having a great deal of difficulty doing so. Corosync has a valid configuration file and an authkey has been generated. When I run /etc/init.d/corosync I see that only corosync is started. >From experience working with corosync/pacemaker before, I know that this is not enough to have a functioning

All, I see this item on the merb-0.0.8 release notes Added rails session parasite mode. I am assuming merbs can piggy back off the rails current session. How does one achieve that ? Thanks Fernand -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/merb-devel/attachments/20070112/0803f46e/attachment.html

Hello all, I''ve got the problem about the following simple application using autostart and repeat_every. A thread(?) is forked for processing task at first, but at sencond time two threads seem to be forked. My simple application code is... - In worker class class FooWorker < BackgrounDRb:Rails repeat_every 2.minutes first_run Time.now def do_work puts Time.now.to_s +

On 6/22/20 10:49 AM, Richard W.M. Jones wrote: > If you have a plugin which either creates background threads itself or > uses a library that creates background threads, it turns out you > cannot create these in .get_ready (or earlier). The reason is that > nbdkit forks when either daemonizing itself or using the --run option, > and fork cancels all the background threads in the

I would like to persist the user authentication between user sessions (basically a "remind me" by default). Sessions expire while cookies persist: why should I use a session for authentication and then another different cookie for the "remind me"? Can''t I simply store a cookie whith a token and use it for both authentication and persistence? -- Posted via

Hello, I''m a total newbie, so please forgive my ignorance. I am trying to port an application from java to ruby. In order to do that, I need to put the object containing all the business logic into something like application scope. The nicest solution would be just to have an application wide hash, where I can put all kinds in of objects. Where and how would I instantiate such an

Hi Campers, from the discussions gathered around, the current Camping sessions don''t seem to be satisfying. ActiveRecord doesn''t seem to handle hashid as an identifier, plus it doesn''t seem to be fully consistent across the various RDBMS. On the other hand, the scope of the project does not permit to implement all kind of client persistence. Secure sessions with

On 05/23, Eric W. Biederman wrote: > > I want to point out that we need to consider not just SIGKILL, but > SIGABRT that causes a coredump, as well as the process peforming > an ordinary exit(2). All of which will cause get_signal to return > SIGKILL in this context. Yes, but probably SIGABRT/exit doesn't really differ from SIGKILL wrt vhost_worker(). > It is probably not

https://bugzilla.mindrot.org/show_bug.cgi?id=3589 Bug ID: 3589 Summary: ControlMaster auto, persist and -f fail. Product: Portable OpenSSH Version: 9.3p1 Hardware: amd64 OS: Linux Status: NEW Severity: minor Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org

> On Jul 29, 2016, at 2:19 AM, David Chisnall <david.chisnall at cl.cam.ac.uk> wrote: > > On 29 Jul 2016, at 05:11, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> What I meant by “different problem" is that “downstream users” for instance don’t need to commit, that makes their problem/workflow quite different from an upstream developer

> -----Original Message----- > From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Mehdi > Amini via llvm-dev > Sent: Friday, July 29, 2016 10:02 AM > To: David Chisnall > Cc: llvm-dev at lists.llvm.org; Bruce Hoult > Subject: Re: [llvm-dev] [RFC] One or many git repositories? > > > > On Jul 29, 2016, at 2:19 AM, David Chisnall >