01-15-2008
Uhmm.. forgot another thing.. I will only need to take the start time if the status is 'send messages', and not 'submit messages'.
Here's another portion from the file:
<LogEvent ID="Timer Start">
<LogEventProperty Name="Event Type" ID="Event Type"><![CDATA[Timer Start]]></LogEventProperty>
<LogEventProperty Name="Start Date" ID="Start Date"><![CDATA[12/13/2007]]></LogEventProperty>
<LogEventProperty Name="Start Time" ID="Start Time"><![CDATA[19:04:46]]></LogEventProperty>
<LogEventProperty Name="End Date" ID="End Date"><![CDATA[12/13/2007]]></LogEventProperty>
<LogEventProperty Name="End Time" ID="End Time"><![CDATA[19:04:46]]></LogEventProperty>
<LogEventProperty Name="Result" ID="Result"><![CDATA[ ]]></LogEventProperty>
<LogEventProperty Name="Failure Reason" ID="Failure Reason"><![CDATA[ ]]></LogEventProperty>
<LogEventProperty Name="Failure Description" ID="Failure Description"></LogEventProperty>
<LogEventProperty Name="Virtual Tester Command ID" ID="Virtual Tester Command ID"><![CDATA[send messagesRCF/MH541/10JUL0700/FRA/T20]]></LogEventProperty>
<LogEventProperty Name="Virtual Tester First Time Stamp" ID="Virtual Tester First Time Stamp"><![CDATA[68798]]></LogEventProperty>
<LogEventProperty Name="Virtual Tester Line Number" ID="Virtual Tester Line Number"><![CDATA[1177]]></LogEventProperty>
<LogEventProperty Name="Operating System" ID="Operating System"><![CDATA[Windows]]></LogEventProperty>
<LogEventProperty Name="OS Version" ID="OS Version"><![CDATA[2003]]></LogEventProperty>
<LogEventProperty Name="Processor" ID="Processor"><![CDATA[Pentium]]></LogEventProperty>
<LogEventProperty Name="Display Resolution" ID="Display Resolution"><![CDATA[1024x768]]></LogEventProperty>
<LogEventProperty Name="Display Color Bits" ID="Display Color Bits"><![CDATA[32]]></LogEventProperty>
<LogEventProperty Name="OS Service Pack" ID="OS Service Pack"><![CDATA[Service Pack 1]]></LogEventProperty>
<LogEventProperty Name="Memory Size" ID="Memory Size"><![CDATA[2048]]></LogEventProperty>
<LogEventProperty Name="Processor Number" ID="Processor Number"><![CDATA[4]]></LogEventProperty>
</LogEvent>
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello Scripting Gurus,
I need help with extracting data from the XML file using shell script.
The data is in a large XML and I need to extract the id values of all completedworkflows. Here is a sample of it. Input and output data is also in the attached text files.
<wfregistry>... (5 Replies)
Discussion started by: yajaykumar
5 Replies
2. Shell Programming and Scripting
Hi, I want to get data from Xml file by using sed or awk command. I want to get the following result :
mon titre 1;Createur1;Dossier1
mon titre 1;Createur1;Dossier1
and save it in cvs file (fichier.cvs).
FROM this Xml file (test.xml):
<playlist version="1">
<trackList>
<track>... (1 Reply)
Discussion started by: yeclota
1 Replies
3. Shell Programming and Scripting
I have an xml file data as shown below:
<impl name="Nortel" is-enabled="true">
<package-mappings>
<const-mapping target-state="EndPoint"
target-param="cfCNDSubscribed" constant-value="true"/>
<const-mapping... (2 Replies)
Discussion started by: ravi_rn
2 Replies
4. UNIX for Dummies Questions & Answers
Hello People,
I have the following contents in an XML file
...........
...........
..........
...........
<Details = "Sample Details">
<Name>Bob</Name>
<Age>34</Age>
<Address>CA</Address>
<ContactNumber>1234</ContactNumber>
</Details>
...........
.............
.............. (4 Replies)
Discussion started by: sushant172
4 Replies
5. Shell Programming and Scripting
Please help me out to extract the Data from the XML Log files.
So here is the data
ERROR|2010-08-26 00:05:52,958|SERIAL_ID=128279996|ST=2010-08-2600:05:52|DEVICE=113.2.21.12:601|TYPE=TransactionLog... (9 Replies)
Discussion started by: raghunsi
9 Replies
6. Shell Programming and Scripting
Hi ,
I have input file as XML. following are input data
#complex.xml
<?xml version="1.0" encoding="UTF-8"?>
<TEST_doc xmlns="http://www.w3.org/2001/XMLSchema-instance">
<ENTRY uid="123456">
<protein>
<name>PROT001</name>
<organism>Human</organism>
... (1 Reply)
Discussion started by: mohan sharma
1 Replies
7. Shell Programming and Scripting
Hi evry1,
This is my 1st post in this forum.Pls help me
I want to extract some data froma xml file which has 2000 lines using shell scripting. Actually my xml file has some "audio and video codes" which i need to arrange in a column wise format after extracting it using shell scripting.I... (4 Replies)
Discussion started by: arun_kohan
4 Replies
8. Shell Programming and Scripting
Hi ,
I have input file as XML. following are input data
#complex.xml
Code:
<?xml version="1.0" encoding="UTF-8"?><TEST_doc xmlns="http://www.w3.org/2001/XMLSchema-instance"> <ENTRY uid="123456"> <protein> <name>PROT001</name> <organism>Human</organism> ... (1 Reply)
Discussion started by: arun_kohan
1 Replies
9. Shell Programming and Scripting
Hi Guys,
I am in a need to extract data from a xml file. The XML file format is as below.
<data jsxnamespace="propsbundle" locales="">
<locale>
<!--Error messages starts-->
<record jsxid="CHARPAIR001" jsxtext=" must be selected"></record>
<record... (1 Reply)
Discussion started by: Showdown
1 Replies
10. Shell Programming and Scripting
Hello Shell Gurus,
I have a requirement to get the specific tags from a XML file.
Here is my code snippet
<jdbc-system-resource>
<name>SDPData Source</name>
<target>AdminServer,osb_server1,soa_server1</target>
... (30 Replies)
Discussion started by: Siv51427882
30 Replies
LEARN ABOUT DEBIAN
sylpheed
SYLPHEED(1) General Commands Manual SYLPHEED(1)
NAME
sylpheed - Light weight e-mail client using GTK+
SYNOPSIS
sylpheed [OPTION]...
DESCRIPTION
Sylpheed is a light weight e-mail client for the X Window System using GTK+ aiming for
* Quick response
* Graceful, and sophisticated interface
* Easy configuration, intuitive operation
* Abundant features
The appearance and interface are similar to some popular e-mail clients for Windows, such as Outlook Express or so. The interface is also
designed to emulate the mailers on Emacsen and almost all commands are accessible with the keyboard.
--compose [address] open composition window
--attach file1 [...] open compose with attached files
--receive receive new messages
--receive-all receive new messages of all accounts
--send send all queued messages
--status [folder ...] show the total number of messages
--status-full [folder ...] show status status of each folder
--open folderid/msgnum open message msgnum in new window
--configdir dirname specify directory with configuration files
--exit exit sylpheed
--debug debug mode
--help display this help and exit
--version output version information and exit
There's a also a complete manual available in the sylpheed-doc package.
SEE ALSO
/usr/share/doc/sylpheed/ /usr/share/doc/sylpheed-doc/manual/
AUTHOR
This manual page was written by Takuo KITAME <kitame@northeye.org>, Guido Guenther <agx@debian.org> and Ricardo Mones <mones@debian.org>
for the Debian GNU/Linux system (but may be used by others).
August 31, 2010 SYLPHEED(1)