search for: _immediately_

...c/pam.d/dovecot, and set session=yes in Dovecot's PAM configuration. Except that it didn't, quite: pam_mount worked just fine and mounted the encrypted disk using the IMAP password... and then immediately unmounted it, since for some reason session=yes means that Dovecot closes the session _immediately_ after opening it. This seems just silly. If a PAM session is to be used, then it seems obvious to me that its length should be exactly the length of the IMAP session. I can't see any reason for the current behavior, except maybe that it was a bit simpler to code and is sufficient for pam_mkhom...

...replacement for full-screen, all the time.) The first two are together below, because they seem caused by the same code. For the third I'll send another email. In all cases below, full-screen windows are NOT un-redirected. * Problem one Say the topmost window is non-full-screen and the window _immediately_ below it is a full-screen window (so the two are the topmost windows). In this case, if the user moves the normal, top-most window by dragging its title-bar, the window is immediately hidden below the full-screen one. (The move can be continued correctly, but without the benefit of actually seeing...

Hello, tl;dr: Is there a way to get dovecot's auth to log failed smtp authentications without having to switch on "auth_verbose"? postfix version 2.11.0 and dovecot version 2.2.12 I'm currently migrating my postfix+courier to postfix+dovecot and so far it's working as expected. Except for logging smtp login failures. Despite Postfix logging successful authentications (see

Hi, Short Version: Is there a function to re-bin a histogram to new, broader bins? Long version: I'm trying to create a histogram, however my input-data is itself in the form of a fine-grained histogram, i.e. numbers of counts in regular one-second bins. I want to produce a histogram of, say, 10-minute bins (though possibly irregular bins also). I suppose I could re-create a data set as

Hi, I am developing a call recording application on Asterisk 11.2 and have this configuration in my dialplan: [macro-ccdev2-rec] exten => s,1,MixMonitor(${ARG1},b) [outgoing-originate] exten => _X.,1,NoOp(Will send call to ${EXTEN}) exten => _X.,n,Dial(SIP/${EXTEN}@x.y.z) [outgoing-originate-rec] exten => h,1,Agi(agi://localhost/ajpbx.agi?path=uploadrec&callid=${CC_CALLID})

...pending messages to pam_msg, it sends errors and text_infos to the client as debug messages, and also log()'s error messages. I had a situation where a PAM module was trying to send an error to the user, but it was never being displayed. I also figured it'd be nice to see them _immediately_ (when connecting with '-v'), as well as having them logged so the sysadmin can go back to see any errors if a user reported a problem logging in. - in configure.in, added an option "--without-progress-meter" to have scp default to not showing the progress meter, similar...

The following series flushes my documentation queue and replaces previous postings of those patches. The main difference is that the xl cfg file is now formatted using POD instead of markdown and presented as a manpage. I have setup a cron job to build docs/html and publish it at http://xenbits.xen.org/docs/unstable/ (it''s a bit bare right now). The motivation for some of these patches