-
Print a count of the messages in the queue:
exim -bpc
-
How to resend frozen messages in exim4 queue
exim -bp | grep frozen | awk '{print $3}' | xargs exim -v -M
-
Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient):
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<cfif len(CGI.PATH_INFO)> | |
<!--- Mainly for ACF on windows server ---> | |
<cfset PathInfo = CGI.PATH_INFO /> | |
<cfelse> | |
<!--- for example, on Linux Railo running Apache, CGI.PATH_INFO = "" ---> | |
<cfset PathInfo = getPageContext().getRequest().getAttribute('requestedPath') /> | |
<cfif isNull(PathInfo)> | |
<cfset PathInfo = "" /> | |
<cfelseif PathInfo.startsWith(CGI.SCRIPT_NAME)> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, Rails 3.2 loads everything in app/javascripts and everything in app/stylesheets on | |
every page, despite controller-specific file naming. If you want to load controller-specific | |
files only on views from their respective controllers, you need to change the manifests and the | |
layout. The basic idea is to NOT require the entire trees, but only specific subfolders, in the | |
manifests, and then load the controller-specific files separately in the layout. | |
Any file you DO want loaded on every page should be placed in app/assets/javascripts/general or | |
app/assets/stylesheets/general. | |
For this to work in production, you also need to ensure that the individual files are precompiled by modifying your production.rb file, listing all of the controller-specific files. |
- launch your client as usual and wait for it to load the blockchain and start up
- click on 'help' in the menu bar (top right)
- click on 'debug window'
- select the 'console' tab
- type: walletpassphrase "your walletpassphrase here" 600
- type: dumpprivkey [your address here]
- this will return the private key, you can copy it now; ensure you clear your clipboard/history afterwards
- type: walletlock
- when dumpprivkey fails for no reason, restart your wallet and try again. this was tested :D