Here are the parameters to apply to play movies in HTC wildfire.

ffmpeg -i input.avi -s 240x320 -vcodec mpeg4 -acodec libfaac -ac 1 -ar 16000 -r 13 -ab 32000 -aspect 3:2 output.mp4

or (if you don’t have FFMPEG compiled with –enable-libfaac)

ffmpeg -i input.avi -s 240×320 -vcodec mpeg4 -ac 1 -ar 16000 -r 13 -ab 32000 -aspect 3:2 output.mp4

Here, the value after “-i” switch indicates the path to the input file and output.mp4 is the output file.  Explanation of other parameters is beyond the scope of this post and can understood from the documentation of FFMPEG.

Incoming mail server settings
Protocol : IMAP
Server     : android.imap.mail.yahoo.com
Port         : 993
Security : SSL

Outgoing mail server settings
Protocol : SMTP
Server     : android.smtp.mail.yahoo.com
Port         : 465
Security : SSL

Welcome home, buddy.

java -classpath ${TOMCAT_HOME}/server/lib/catalina.jar org.apache.catalina.util.ServerInfo

$HOME/.local/share/Trash is the folder that represents the Trash.  This directory has a couple of sub-directories, namely info and files.  Later is the directory that has the actual files that were deleted while the directory name “info” is a metadata of the deleted files.

If deleting files from Trash fails because of permission, just change the permission of the files in $HOME/.local/share/Trash/files directory.

Happy trashing !

Most of this week at work I had to analyze issues based on the messages in log files of server. In addition to the messages that were logged to a file, there were also useful messages that were printed on the console. Now, messages scattered in two different stores made my work difficult right from the first step. Moreover, the other problem to me was that at a granular logging level I was hit with a sprinting screen of log messages. I wanted to have all the log messages in a single store but with no change to the application.

Java instrumentation saved me !

Steps
>> Write a class (say, MyAgent.java) with a method following the signature mentioned below

public static void premain(String args, Instrumentation inst) {}

>> In the premain() method, set the PrintStream to wrap a FileOutputStream(). In my usecase, I had to make the FileOutputStream refer the log file.

public class MyAgent {
	public static void premain(String args, Instrumentation inst) {
		java.io.PrintStream savedStream = System.out;
		try {
			System.setOut(new java.io.PrintStream(new java.io.FileOutputStream(
					new java.io.File("System.out.txt"), true)));
		} catch (FileNotFoundException e) {
			System.setOut(savedStream);
			System.err.println("Error while setting System.out"
					+ e.getLocalizedMessage());
		}
	}
}

>> Compile the class with premain() method and pack it to any java archive.
>> Update the java archive with “Premain-Class: MyAgent” entry in the manifest file.
>> Hook the agent to the JVM using the -javaagent switch.

    java -javaagent:myagent.jar -cp ./classes HelloWorld

The real idea behind the instrumentation is completely different. The above can be taken as the first step towards instrumentation. I am sure I am not the last one to face the problem due to scattered log messages in J2EE applications.

Command to install debian package
$sudo dpkg -i <debian_package_name>

Command to remove debian package
$sudo dpkg -r <debian_package_name>

• Connect to the JMS provider using JNDI.
• Get the destination resource, a JBoss queue in our example.
• Post a message to the queue.
• Consume the message from the queue.

Here is the java client to Jboss as jms provider. I also had an opportunity to test the client against BEA’s WebLogic server as JMS provider.  So, you would also see a few lines commented in context of weblogic server.  The code is pretty straight forward in the manner the above listed objectives are implemented. You can post any question/comment if you have in this regard and I shall update the code accordingly.

import java.util.Properties;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageConsumer;
import javax.jms.MessageListener;
import javax.jms.MessageProducer;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueReceiver;
import javax.jms.QueueSession;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
import javax.naming.NamingException;

/**
 * @author Dexter
 *
 */
public class JMSClient {

 QueueConnection conn;
 QueueSession session;
 Queue que;

 /**
 * @param args
 */
 public static void main(String[] args) {
 JMSClient jms = new JMSClient();
 try {
 jms.init();
 jms.send();
 jms.receive();
 jms.cleanUp();
 } catch (NamingException e) {
 e.printStackTrace();
 } catch (JMSException e) {
 e.printStackTrace();
 }

 }

 public static void log(String message, int level) {
 System.out.println(message);
 }

 public static void log(String message) {
 JMSClient.log(message, 4);
 }

 public void init() throws NamingException, JMSException {
 Properties prop = new Properties();
 String connFactory = null;
 String queueName = null;

 // JBoss config
 // Notes : Added jbossall-client.jar to classpath from JBoss v4.1
 prop.put(Context.INITIAL_CONTEXT_FACTORY,
 "org.jnp.interfaces.NamingContextFactory");
 prop.put(Context.PROVIDER_URL, "jnp://localhost:1099");
 prop.put("java.naming.factory.url.pkgs",
 "org.jboss.naming:org.jnp.interfaces");
 connFactory = "ConnectionFactory";
 queueName = "queue/A";

 // WebLogic config
 // Notes : Added weblogic.jar to classpath from weblogic server v9.
 /*
 * prop.put(Context.INITIAL_CONTEXT_FACTORY,
 * "weblogic.jndi.WLInitialContextFactory");
 * prop.put(Context.PROVIDER_URL, "t3://localhost:7001"); connFactory =
 * "weblogic.examples.jms.QueueConnectionFactory"; queueName =
 * "exampleQueue";
 */
 // prop.put("java.naming.factory.url.pkgs",
 // "org.jboss.naming:org.jnp.interfaces");

 Context iniCtx = new InitialContext(prop);
 Object tmp = iniCtx.lookup(connFactory);
 JMSClient.log("Connectionfactory lookup successful ..", 5);
 QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;
 conn = qcf.createQueueConnection();
 que = (Queue) iniCtx.lookup(queueName);
 JMSClient.log("Queue lookup successful ..", 5);
 session = conn.createQueueSession(false, QueueSession.AUTO_ACKNOWLEDGE);
 JMSClient.log("Create session successful ..", 5);

 conn.start();
 JMSClient.log("Connection started successfully ..", 5);

 JMSClient.log("JMS Initialization completed successfully.. ", 3);
 }

 public void send() throws NamingException, JMSException {

 MessageProducer producer = session.createProducer(que);
 JMSClient.log("MessageProducer created successfully ..", 5);
 TextMessage message = session.createTextMessage();
 message.setText("My first JMS message");
 JMSClient.log("Message created successfully ..", 5);
 producer.send(message);
 JMSClient.log("Message sent successfully ..", 5);

 }

 public void receive() throws JMSException {
 QueueReceiver qRcvr = session.createReceiver(que);
 qRcvr.setMessageListener(new MyQueueListener());
 JMSClient.log("Message listener associated ..", 5);
 // Notes : Blocking call - Synchronous. Hence I switched to Asynchronous
 // (non-blocking) approach by implementing MessageListener
 /*
 * MessageConsumer consumer = this.session.createConsumer(que);
 * JMSClient.log("Consumer created successfully..", 5); TextMessage
 * message = null; while ((message = (TextMessage) consumer.receive())
 * != null) { JMSClient.log(message.getText()); }
 */
 long waitTime = 5000;
 JMSClient.log("Receiver waiting " + waitTime + " ms to give MessageListener a chance to run.", 3);
 try {
 Thread.sleep(waitTime);
 } catch (InterruptedException e) {
 e.printStackTrace();
 }
 }

 public void cleanUp() throws JMSException {

 if (session != null) {
 session.close();
 log("Session closed successfully ..", 5);
 }
 if (conn != null) {
 conn.close();
 JMSClient.log("Connection closed successfully ..", 5);
 }

 }
}

class MyQueueListener implements MessageListener {

 public void onMessage(Message message) {
 try {
 JMSClient.log(((TextMessage) message).getText());
 } catch (JMSException e) {
 e.printStackTrace();
 }
 }
}

The command to lauch the scanner for Avast 4.8 is ashQuick.exe.  This command takes the path to scan.  To scan the whole computer, pass all the local drives as argument to the command and this should be set as the command to run for auto-scanner to start.

"{AVAST_HOME}\ashQuick.exe" "C:\" "D:\"

There is no self-help switch on this command for a better understanding of the command.  With the above option, all we do just to start the scanner for the listed path as argument. It is unknown whether an archived file will be scanned along with the depth of scanning for infection. Just set this scheduler up and have automated scans.

Much appreciated if you could comment/suggest in this context.

I have tried this with Windows XP many times and everytime this solution worked.  So, I guess this solution should work in most cases when disconnecting USB drive from Windows PC fails.