parsing
Modules
bs4
fake_useragent
requests
Classes
builtins.object
Parser
class
Parser
(
builtins.object
)
Parser
for events on concert.ua
Methods defined here:
parse
(self, artist_name)
Parses concert.ua checking availability performance of this artist
:param artist_name:
:return: event_name, event_link: tuple


EatSchool by 5AINF and 5BINF in "I.I.S. Mattei Vasto" - 2020. The source code is licensed under MIT GitHub


The interface that all childs must implement
boolean checkIsEnabled( [ $data = false], [ $identifier = ''], [ $funcArgs = array()], [ $ttl = 60] )
Does the actual check whether the module can be enabled or not
For APC it can be used to check if APC is installed and loaded, file based cache can check whether the cache dir is writable, and so on


Netcraft Full-Stack Development April 2021
Evyatar Rosner
Full-Stack Architect, Consultant & Lecturer
David Meir-Levy
Full-Stack Javascript Developer, Platforms Builder
Let's stay in touch!
David Meir-Levy
Evyatar Rosner
Ophir Bucai
Student Name


Hi! I'm Shivani Soman, a Data Scientist based in New York City, NY.
Working in the finance field, I translate seemingly uninformative data into valuable and actionable insights. I build concise and insightful reporting dashboards and use machine learning solutions to improve clients' decision making power. My goal is to build innovative data-driven solutions that would help optimize everyday processes.
In my free time I enjoy impressing people with my ukulele skills, playing video games and trying to get my rubik's cube solve time under 30 secs.
Relevant Coursework : Big Data Analytics, Database Management and Statistical Computing, Bioinformatics, Large Scale Data Mining, Learning and Reasoning with Bayesian Networks, Health Analytics. GPA : 3.93
Relevant Coursework : Data Mining Techniques and Applications, Business Intelligence, Machine Learning, Data Structures and Algorithms, Database Systems , Operating Systems, Computer Networks. Final Percentage : 71% (First Class with Distinction)
Developed a two-fold method to classify music into 10 different genres using Convolutional Recurrent Neural Networks (CRNN) for spectrogram analysis and traditional machine learning classifiers for analysis of Mel-Frequency Spectral Coefficients (MFCCs) derived from the audio samples with an accuracy of 86%.
View ProjectPerformed predictive analysis on huge amounts of metagenomic data (> 3 TB) to correctly predict the origin of each metagenomic sample using neural networks and XGBoost.
Built a deep learning algorithm using Long Short-Term Memory Networks (LSTMs) by collecting data from various sensors like accelerometer and gyroscope obtained from a smart watch to accurately predict the activity the user was performing like standing, sitting, walking, etc.
View ProjectAnalyzed millions of tweets before and during Super Bowl XLIX (2015) to determine how and why public sentiments towards the New England Patriots and the Seattle Seahawks changed over the span of the championship match.
View ProjectDeveloped a Machine Learning model using NLP that classifies genetic mutations of cancer genes from an expert annotated knowledge base and text-based clinical literature into a set of predefined classes. Obtained a better score than the 1st rank on the leaderboard of this Kaggle competition using Word2Vec Embeddings and LightGBM.
View Project


Erin Eckerman
Erin Eckerman is a software developer with 10 years of experience in program management - working with organizations ranging from multinational corporations to small non-profits. She is passionate about developing technological solutions to address social challenges and creating immersive experiences that bring joy to their users.
Timothy Lee
Formerly a salesman working for the insurance industry, Tim was encouraged to learn programming by his brother-in-law. He developed a passion for coding and find found around with different logic strings to be amusing. Tim's goal is to continue to grow his passion for coding and eventually develop his own application so he can showcase his creativity.
Jessica Lovell
Born and raised deep in the heart of Texas, Jessica is a full-stack javascript software developer based in Seattle. Her background in mathematics and love for guiding tourists inspires her passion for justice and ice cream and is looking for opportunities to develop her skills in cyber security and cryptography.


Training Location: {{ @SESSION.training_info['location'] }}
Application Deadline: {{ @SESSION.training_info['deadline'] }}
Training Schedule:
{{ @SESSION.training_info['date'] }}
{{ @SESSION.training_info['date2'] }}
NAMI Ending the Silence is:
A 50-minute mental health presentation for middle and high school
aged youth available at no-cost to schools, youth clubs, and youth groups.
About This Training
- Presented by a trained 2-person team consisting of:
- A young adult (age 18-35) living with a mental health condition,
who will serve as the Young Adult Presenter.
- An adult (age 18 or older) living in recovery with a mental health
condition, or family member of an individual living with a mental health
condition, who will serve as the Lead Presenter.
-
This presentation educates audience members about mental health conditions and
their warning signs and provides audience members with resources and tools to
help themselves, friends, and family members who may be in need of support. The
program has three presentations designed for three audiences: students,
families and school staff.
-
Hearing a personal story from an individual living with a mental health
condition helps to dispel myths, instill a message of hope and recovery, and
encourage audience members to reduce the stigma associated with mental illness.
ETS reduces stigma through:
- Education — Provides accurate information about mental illness to
promote understanding and dispel myths.

Individuals who have lived experience with a mental health condition and are interested in
educating students, families, and school staff about mental health/illness. If an affiliate
is working to implement the program and wants to train their first Ending the Silence
presenters, we ask that they submit a 2-person team consisting of a Young Adult and Lead
Presenter, if possible.
-
A 2-person team consists of a Young Adult Presenter, a young adult (age 18-35)
living with a mental health condition who is willing to share their story, and a
Lead Presenter, an adult (age 18 or older) who is either a person living with a
mental health condition or is a family member or caregiver of an individual living
with a mental health condition.
-
A current NAMI Member.
-
Able to complete the online training three weeks after the application deadline.
- Able to attend the entire half-day intensive training.
-
Because NAMI Ending the Silence is taught in schools and youth settings, applicants
should have flexible schedules that allow them to present on weekdays during school
hours.
The Ending the Silence training is a blended training, with an online portion and in-person
portion. The 6-8 hour online training gives you resources and support as you prepare your
draft presentation script. The half-day in-person training gives you the opportunity to
practice your presentation in front of a friendly audience and our state trainers, who give
supportive and constructive feedback. You will leave the training feeling confident and
prepared to give Ending the Silence presentations.
The Lead Presenter will be trained to give the 25-minute educational PowerPoint
presentation, and will complete the NAMI ETS Lead Students online training. The Young Adult
Presenter will be trained to give both the 25-minute educational PowerPoint presentation as
well as trained to share their story of recovery, and will complete both the NAMI ETS Lead
Students and the NAMI ETS Young Adult online trainings.
After completing the in-person training, all Ending the Silence presenters will need to
complete two additional online trainings, NAMI ETS Lead Families and NAMI ETS Lead Staff.
NAMI Washington will cover the cost of all training materials, food, and lodging. Your NAMI
affiliate is asked to cover your travel expenses. Lodging for the training is double
occupancy, which means you will be sharing a room with another attendee. If you require
single occupancy, arrangements will need to be made prior to your attendance, and there
will be additional costs which will be the responsibility of the attendee.
Attending the training is by pre-registration only, and class size is limited. In order to
reserve a space, your affiliate must submit a $50 refundable registration deposit at the
time of registration. If there are more applications than spots for the training, a waiting
list will be created.
Completion of the online training is REQUIRED for in-person training attendance – if you do
not complete the online training within three weeks of the application deadline, you will
be unable to attend the in-person training.
If you find that you are unable to attend the training after being accepted, please notify
Jenny Gruenberg at the NAMI Washington state office by phone,<PHONE_NUMBER>, or email,
<EMAIL_ADDRESS>no later than the Friday
the week before the training, so we can fill your spot, otherwise your affiliate will lose
its $50 registration deposit. If you have any questions about the training or the
registration process, please feel free to contact Jenny Gruenberg by email or phone.
Ready to start the application?
Start


|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
| Interface Summary | |
|---|---|
| ActionsPublisher | This interface is used to mark resources that publish a list of actions that can be performed on them. |
| Handle | Interface for classes used to store the information about an open resource. |
| ResizableVisualResource | This interface denotes visual resources that can be resized. |
| Class Summary | |
|---|---|
| AccessRightsDialog | |
| AnnotationDiffGUI | Compare annotations in two annotation sets in one or two documents. |
| AppearanceDialog | Deprecated. |
| BooleanRenderer | A TableCellRenderer used for Booleans |
| BootStrapDialog | This class is used to handle BootStrap wizard with the Gate GUI interface. |
| CollectionSelectionDialog | This class visually selects some items from a collection and returns a collection with the items selected by the user. |
| ControllerMetadataViewer | This viewer displays metadata associated with a GATE Controller. |
| CorpusEditor | A simple viewer/editor for corpora. |
| CorpusFillerComponent | A simple component that allows the user to select a directory and a list of permitted extensions for populating a corpus |
| CorpusQualityAssurance | Quality assurance corpus view. |
| CorpusQualityAssurance.ExtendedListModel | |
| CorpusQualityAssurance.ToggleSelectionABModel | Add a suffix A and B for the first and second selected item. |
| CorpusQualityAssurance.ToggleSelectionModel | |
| CreateIndexDialog | |
| CreateIndexGUI | Provides a gui for creating a IR index on a corpus. |
| FeatureMapEditorDialog | A simple editor for List values. |
| FeaturesSchemaEditor | |
| GazetteerEditor | Editor for ANNIE Gazetteer . |
| HelpFrame | A frame used by Gate to display Help information. |
| ListEditorDialog | A simple editor for Collection values. |
| LogArea | This class is used to log all messages from GATE. |
| LogArea.UTF8PrintStream | A print writer that uses UTF-8 to convert from char[] to byte[] |
| LogArea.UTF8PrintWriter | A print writer that uses UTF-8 to convert from char[] to byte[] |
| LuceneDataStoreSearchGUI | GUI allowing to write a query with a JAPE derived syntax for querying a Lucene Datastore and display the results with a stacked view of the annotations and their values. |
| MainFrame | The main Gate GUI frame. |
| NameBearerHandle | Class used to store the GUI information about an open entity (resource, controller, datastore). |
| NewResourceDialog | |
| OkCancelDialog | A simple modal dialog that displays a component provided by the user along with two buttons ("OK" and "Cancel"). |
| OptionsDialog | The options dialog for Gate. |
| OptionsDialog.LNFData | |
| ParameterDisjunction | Represents a list of Parameters which are alternative to each other. |
| PRViewer | |
| ResourceParametersEditor | Allows the editing of a set of parameters for a resource. |
| ResourceRenderer | Renders a Resource for tables, trees and lists. |
| SearchPRViewer | Shows the results of a IR query. |
| SerialControllerEditor | |
| SerialDatastoreViewer | |
| SingleConcatenatedFileInputDialog | A simple component that allows the user to select a trec web file and encoding |
| Splash | A splash screen. |
| STreeNode | |
| SyntaxTreeViewer | The SyntaxTreeViewer is capable of showing and editing utterances (fancy name for sentences) and the attached syntax trees. |
| TabBlinker | |
| TabHighlighter | Highligts a tab in a JTabbedPane. |
| TextAttributesChooser | A dialog used to set the attributes for text display. |
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |


Home
About
Albums
Blog
Contact
American Idiot
Time
Listen
Link
Information
Learn More
Maroom 5
Time
Listen
Link
Information
Learn More
The velvet underground and nico
Time
Listen
Link
Information
Read More
Bob Dylan
Time
Listen
Link
Information
Learn More
First page
Prev
1
2
3
Next
Last Page
Copyright © 2015.Pitt All rights reserved.


About me
Lower dollar body street exist fruit well blood lucky eventually pictured sale industrial driving milk held guess bow attention fly powerful price mostly obtain.
Block view organized stranger single happily leave made good rich seen contrast stick color lady excited higher balloon cave early spirit temperature park she. lady buried some diameter surprise using remain century desk loud here familiar oil setting recall wooden screen recently understanding push apple edge throw are. recall wooden screen recently understanding push apple edge throw are.
Block view organized stranger single happily leave made good rich seen contrast stick color lady excited higher balloon cave early spirit temperature park she. lady buried some diameter surprise using remain century desk loud here familiar oil setting recall wooden screen recently understanding push apple edge throw are. Block view organized stranger single happily leave made good rich seen contrast stick color lady excited higher balloon cave early spirit temperature park she. lady buried some diameter surprise using remain century desk loud here familiar oil setting recall wooden screen recently understanding push apple edge throw are.


Are you sure you want to close your account?You won't be able to undo this.


CRUEL INTENTIONS (Columbia) Starring: Ryan Phillippe, Sarah Michelle Gellar, Reese Witherspoon, Selma Blair, Joshua Jackson, Sean Patrick Thomas, Christine Baranski. Screenplay: Roger Kumble, suggested by "Les Liaisons Dangereuses" by Choderlos De Laclos. Producer: Neal H. Moritz. Director: Roger Kumble.  Reviewed by Scott Renshaw.
Hollywood has always been obsessed with youth, but that obsession finally appears to be spinning out of control. In these halcyon days of 'N Sync, "Dawson's Creek" and the like, it now seems that you can sell any pitch in Hollywood by naming a piece of source material and tagging on the phrase "...but with teenagers." The most recent wave may have started with CLUELESS ("Jane Austen's _Emma_, but with teenagers"), and has since generated such classics as THE FACULTY ("THE THING, but with teenagers") and SHE'S ALL THAT ("PYGMALION, but with teenagers"). So why not CRUEL INTENTIONS? Why not "DANGEROUS LIAISONS, but with teenagers?"
Because it's a really lousy idea, that's why, made even worse by appalling execution. The principle players are Sebastian Valmont (Ryan Phillippe) and Kathryn Merteuil (Sarah Michelle Gellar), Manhattan step-siblings who are birds of a poisonous feather. Sebastian delights in deflowering innocents and building his reputation as a cad; Kathryn seeks vengeance on a sweet young thing named Cecile (Selma Blair) who unwittingly stole away her boyfriend. United in their disdain for all other feeling human beings, Sebastian and Kathryn strike a wager. It involves Annette Hargrove (Reese Witherspoon), a teen who has published a national magazine article trumpeting her virginity. Sebastian's mission is to seize that virtue or risk losing his classic car. If he wins, his next conquest will be his own step-sister.
If that all sounds considerably sleazier than the original DANGEROUS LIAISONS, that's only because it is. Writer/director Roger Kumble plays most of the film as though it's soft-core porn for teenyboppers, teasing with pseudo-incestuous fondling and money-shot close-ups of Gellar and Blair tongue kissing. To make matters even more unpleasant, Kumble even plays an interracial relationship for titillation value, and goes for cheap laughs by introducing a pointless subplot in which a stud athlete (Eric Mabius) is a closet homosexual, complete with gratuitous slurs. In a depressing case of lowest common denominator film-making, Kumble has appealed to his teen audience by reducing the themes of "Les Liaisons Dangereuses" to "everyone has sex with everyone else."
In an even more depressing development, Kumble may actually have the _best_ grasp of the source material. Ryan Phillippe, in a valiant but grossly misguided effort to do some acting, spends virtually the entire film aping John Malkovich's performance in Stephen Frears' 1988 DANGEROUS LIAISONS. Every inflectionless line reading, every arched eybrow, every lascivious double-entendre is familiar, with no apparent adjustment for the fact that Sebastian is a contemporary teenager instead of an 18th century nobleman. Gellar is only a bit better in the lip-curling Glenn Close role, while Selma Blair plays Cecile not as simple and innocent, but with a fumbling idiocy that makes her every moment on screen unbearable. Only Reese Witherspoon brings a shred of dignity to the proceedings, continuing to show a wonderful presence for a young actress and an interest in finding something human in her character.
Unfortunately, that's an interest her director doesn't share. I suppose it shouldn't be surprising that CRUEL INTENTIONS is just another in a long line of glossy high school audience flicks, another film with a mind-numbingly incessant underscore of shuffle-beats and pop songs, another vehicle for pretty girls and even prettier boys to pose for their fans. It is sad, however, that these filmmakers have to keep picking promising source material for their libretti, then demonstrating no concern for that material whatsoever. DANGEROUS LIAISONS was a tale of corruption beneath a courtly veneer; CRUEL INTENTIONS makes the shocking suggestion that adolescents can be petty, manipulative and obsessed with sex.
On the Renshaw scale of 0 to 10 dubious liaisons: 2.
Visit Scott Renshaw's Screening Room http://www.inconnect.com/~renshaw/ *** Subscribe to receive new reviews directly by email! See the Screening Room for details, or reply to this message with subject "Subscribe".
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


You may experience something wrong with your vim color scheme after you installed TMUX, something like:
TMUX really wants the terminal set to screen, not xterm.
to fix this, simply add this line to your ~/.bashrc file:
export TERM="screen-256color"
to make sure you’re doing it properly, login to TMUX and type the command below:
echo $TERM
if terminal show you “screen-256color” then everything should be fine. you can start your vim now.


New Star Trek: Picard Images Feature New and Returning Characters
by Jake AbbateJean-Luc Picard is the focus of CBS All Access’ upcoming Star Trek series, but he won’t be alone on his travels. After a two decade hiatus, the former Starfleet captain will forge new alliances and also reunite with some recognizable faces. Recent trailers have given fans an early look at who these characters are. But now, CBS All Access has debuted some new photos that highlight Star Trek: Picard’s supporting cast.
In these pics, Picard once again cross paths with Jonathan Frakes’ William Riker. Frakes’ behind-the-scenes involvement with the series has been known for some time. In addition to reprising his famous role, Frakes will also direct the second “block” of episodes for the first season.
RELATED: Brent Spiner Admits He Was Surprised To Be Back For Picard
We also see a new shot of Dahj, the young woman who comes to Picard for help. In one new photo, she’s sharing a tender moment with Narek, played by Harry Treadaway. Narek is a Romulan who becomes part of Picard’s new team. But Narek won’t be the only one of his species showing up. Evan Evagora will star as Elnor, another Romulan dedicated to Picard’s cause who is also a skilled hand-to-hand combatant. Other new stills include Michelle Hurd’s Raffi Musiker and Santiago Cabrera’s Cristobal “Chris” Rios, both of whom are ex-Starfleet officers.
Star Trek: Picard will premiere on January 23 on CBS All Access.
You can check out the new photos from the series in the gallery below. Which supporting character are you most excited to see? Let us know in the comment section!
Recommended Reading – Star Trek: The Next Generation: Through The Mirror
We are a participant in the Amazon Services LLC Associates Program. This affiliate advertising program also provides a means to earn fees by linking to Amazon.com and affiliated sites.


Looks like the snapshot you are looking for does not exist. Either the snaphot collector has yet to run or the snapshot id in the URL is invalid.
{{snapshot.repository.description}}
No description found
{{repository.project.html_url}}
No README file found during repository scan.


Cocktail Lounge
Cocktail Lounge
Carina Coelestin | Nikolaus Hribernig | Patrick Plank
Fill List
Add a new Cocktail
ID
Name
Type
Alcohol in %
Ingredients
Delete
Show
Edit
Average Rating
Delete
Show
Edit


Drive more deeper and deeper in PWA concepts.
Resize this responsive page to see the effect!
A service worker is a script that your browser runs in the background, separate from a web page, opening the door to features that don't need a web page or user interaction. Today, they already include features like push notifications and background sync. In the future, service workers might support other things like periodic sync or geofencing. The core feature discussed in this tutorial is the ability to intercept and handle network requests, including programmatically managing a cache of responses.
The web app manifest is a simple JSON file that tells the browser about your web application and how it should behave when 'installed' on the user's mobile device or desktop. Having a manifest is required by Chrome to show the Add to Home Screen prompt.
Footer


Blocktrace
Dashboard
Logout
Dashboard
×
Delete User
Something went wrong. Please try again.
TestCompany, Inc.
You are logged in as
It is your responsibility to protect user data.
Do not leave your computer unattended and log out when you are finished.
Refresh Database
NRIC
Name
D.O.B.
Postcode


Before Change
question_id = article["QuestionId"]
question_source = article["QuestionSource"].strip()
yield "%s_%s" % (os.path.basename(filepath), question_id), {
"entity_pages": entity_pages,
"search_results": search_results,
"question": question,
"question_id": question_id,
"question_source": question_source,
"answer": answer_dict,
}
After Change
for line in f:
if line == " {\n":
current_record = line
elif line.startswith(" }"): // Handles final record as well.
article = json.loads(current_record + "}")
current_record = ""
example = parse_example(article)
yield "%s_%s" % (fname, example["question_id"]), example
else:
current_record += line


JDE Tutorial
This tutorial will walk you though the process of creating and running
a program using emacs and the Java Development Environment (JDE). The first
thing to do is run emacs. If you are at a work station open a teminal and
type:
emacs &
If you are working elsewhere using telnet type the following:
TERM=vt100
emacs -nw
Each action you can take in emacs can be done by typing at the keyboard
or often by use of menus. Both options will be discussed in the tutorial.
Keyboard commands will often have special notation:
| C-x |
Indicates that you should hold down the Control (Ctrl) key while pressing
the x. |
| M-x |
Indicates that you should press the Meta key with the x. This can be
done in two ways. Either press and hold the diamond key (on either side
of the space bar on a sun) while pressing the x or press the Escape (Esc)
key release it and then press the x. |
A sequence of commands starting with a control or meta key will appear
in the last line of the emacs window which is called the minibuffer.
Important:
anytime you find yourself typing in the minibuffer when you would rather
not be, type C-g (control g) to "quit" the minibuffer. You may need to
do this more than once.
Text listed with a blue background
indicates text you should type in emacs. These will indicate the keyboard
method for executing commands. A description of the mouse/menu method will
appear nearby.
The big window in emacs is called the buffer. It is where you edit your
files. Each file you have open will have its own buffer.
Creating and Opening a file
The first step to writing a program is creating a file. You can create
an empty file or open an existing file using the command sequence
C-x
C-f (remember that is a Control x followed by a Control f). There
will be a line in the minibuffer asking you to type a name for this file.
If the file name exists the file will be opened. Otherwise, a new blank
buffer will be opened with that filename. The file will not be created
until you save (see below).
Creating a file with JDE
For the purposes of this tutorial we will use a slightly different command.
We want JDE to build an outline of our program for use. So we will use
the following command:
M-x jde-gen-console-buffer
Before continuing let's break this command down into its component parts:
-
M-x
-
Either the diamond with the x key or escape followed by the x key. This
will put your cursor into the minibuffer. This tells emacs you are about
to give it a command.
-
jde-gen-console-buffer
-
You will type this command directly into the minibuffer and press the return
key. A bit wordy. Read on.
If you are fortunate enough to be using emacs directly on a workstation
i.e. you did not telnet from off site, then you can use your mouse instead.
Just go to the Files menu select the JDE-New sub-menu and choose Console...
We will indicate this action with the notation Files-> JDE New-> Console...Once you have executed the command you will type the name of your new
program in the minibuffer. Type Hello.java
in the minibuffer and hit return. You
should have in your emacs window something that looks like this: (your
colors may be different or non-existent depending on how you started emacs)
authorversion
public class Hello{
public Hello (){
}
public static void main(String[] args){
}
}
Let's make some changes to the file. Above the minibuffer
is an inverse video status line which includes the name of the file you
are editing and some various other information. One piece of information
is the current line number--the line in your file where the cursor is currently
located. You can either use the arrow keys or the mouse to move this cursor.
Put the cursor on line 18 of Hello.java. That should be the blank line directly
below public static void main(String[] args){. Type the following:
System.out.println("Hello World") //a line with an error
Line the 'S' in System up with the 'i' in public of the previous line--this
is not a requirement, but it is considered good programming style. You can do
this by pressing Tab anywhere on
the line. Notice
that there is no semi-colon at the end of the line. This will cause a problem
with the Java compiler. We want it to.
Saving
Look again at the status bar at the bottom of emacs. Notice the left end
looks like --\**. The stars indicate that this file is in need
of saving. To save the contents of this buffer to the current filename
type C-x C-s. If you wanted to change the file name (Save As...)
you would type C-x C-w and type in a new name. You could perform
these tasks similarly with a mouse by using the menus Files-> Save Buffer
and Files-> Save Buffer As...
Recalling or Reopening a Previously Created File
Suppose you are working on Hello.java and you want to take a break (see Quitting
below). So you leave emacs and log out of your work station and leave.
When you come back and restart emacs, you only need to open the file you
were working on. If you are simply working on a file that already exists
you can type C-x C-f or use the menus Files-> Open File... This
will prompt you for a file name in the minibuffer. Try it:
-
Quit emacs by typing C-x C-c.
-
Take a break. Don't forget to come back.
-
Run emacs again (see above).
-
Type C-x C-f.
-
Type Hello.java in the minibuffer, and press the return
key.
Emacs now has Hello.java in an open buffer, ready for you to continue.
Compiling and Fixing Errors
Now we want to compile the file Hello.java. So we will tell emacs to run the
java compiler. We can do this by typing
C-c C-v C-c or by selecting
the menu JDE-> Compile. This action will split our window into two separate
buffers. In the top you will see Hello.java. In the bottom you will see the
results of the compilation which should look something like this:
cd c:/My Documents/java/
javac -g Hello.java
Hello.java:18: ';' expected
System.out.println("Hello World") //a line with an error
^
1 error
Compilation exited abnormally with code 1 at Wed Jan 10 14:13:08
This shows us one error message. Each error message tells us the file name
where the error is, what line number it occurs in, a description of the
error and the line itself. A ^ symbol beneath the line indicates where
the compiler thinks the error occurred.
Now we have two buffers showing us information. To switch between them
we can either click with the mouse or type C-x o to move the cursor
to the other buffer. We'll try this out later.
With JDE you can use the error messages to go directly to the line where
the error occurred. Use one of the following options to do this.
-
Type C-x ` while the cursor is in the buffer containing Hello.java.
This will advance the cursor to the next error. Doing this multiple times
will go through multiple errors if they exist.
-
OR Click on the filename:line part of the error message using the
middle mouse button.
-
OR Move the cursor to the buffer containing the error messages.
Put the cursor at the beginning of the error message and press the return
key.
Fix the error in Hello.java by adding a semicolon ;
after the ) of line 18.
It should now read:
System.out.println("Hello World"); //a line with an error
Recompile Hello.java with C-c C-v C-c. There will be a question in the
minibuffer asking if you want to save your changes to the file. Type
y.
Working with multiple buffers
Before going any further let's look at using multiple buffers. The area
containing a buffer is called a window. Currently you should have two visible
windows in emacs. We already saw how C-x o switches the cursor
between windows. There are a number of other useful commands for multiple
windows. Below are descriptions of each and how to perform them using either
the keyboard or the mouse.
| Description |
Keyboard |
Mouse |
| Move the cursor to a different window. |
C-x o |
Click in the window where you want the cursor |
| Go back to a single window. |
C-x 1 |
Select from the menus Files-> One Window |
| Split one window into two. |
C-x 2 |
Menu: Files-> Split Window |
You can also have multiple buffers open at once and they don't all have
to be displayed in emacs. Below are some actions for looking at other buffers.
| Description |
Keyboard |
Mouse |
| Show all open buffers. |
C-x C-b |
Buffers-> List All Buffers. The Buffers menu has list list of the buffers
you have used most recently. |
| Switch to a buffer from the list of all buffers. |
Move the cursor to the buffer name. Hit return. |
Click with the middle button on the name of the buffer. |
| Switch to a buffer without looking at the list. |
C-x b The name shown in the minibuffer is the default. To
switch to it press return, otherwise type the name of the buffer you wish
to switch to. |
Select the name of a buffer from those in the Buffers menu |
Try it: Manipulating Buffers
-
Move the cursor to the window containing the compilation messages. C-x
o.
-
Show only this buffer. C-x 1
-
Switch to the scratch buffer. C-x b type *scratch* and
hit return.
-
Split the window. C-x 2
-
Move the cursor to the bottom window. C-x o
-
Show the Hello.java buffer. C-x b type
Hello.java and hit return.
-
Show only the Hello.java window. C-x 1.
Running your program
Now that we've compiled a working version of Hello.java, it's time to run
our program. Either type C-c C-v C-r or select the menu JDE->
Run App. As a result emacs split your window and wrote "Hello World" to
the screen, along with some other status messages which are NOT
part of your program itself.
Quitting
You can now exit emacs by typing C-x C-c or selecting Files->
Exit Emacs.
Last modified: 01/21/03


{% trans %} We've partnered with some great brands to bring you a number of free assets that you can use to help your flick stand out. {% endtrans %}
{{ _('Read the blog post') }} * {{ _('English only') }}


Daily-Do develops strong interval identification abilities! Click on the 'easy' or 'hard' button to begin. Click the 'easy' or 'hard' button again to reset the game.
ready!


Package javax.accessibility
Defines a contract between user-interface components and an assistive technology
that provides access to those components.
See:
Description
|
Interface Summary |
| Accessible |
Interface Accessible is the main interface for the accessibility package. |
| AccessibleAction |
The AccessibleAction interface should be supported by any object
that can perform one or more actions. |
| AccessibleComponent |
The AccessibleComponent interface should be supported by any object
that is rendered on the screen. |
| AccessibleEditableText |
The AccessibleEditableText interface should be implemented by all
classes that present editable textual information on the display. |
| AccessibleExtendedComponent |
The AccessibleExtendedComponent interface should be supported by any object
that is rendered on the screen. |
| AccessibleExtendedTable |
Class AccessibleExtendedTable provides extended information about
a user-interface component that presents data in a two-dimensional
table format. |
| AccessibleExtendedText |
The AccessibleExtendedText interface contains additional methods
not provided by the AccessibleText interface
Applications can determine if an object supports the AccessibleExtendedText
interface by first obtaining its AccessibleContext (see Accessible )
and then calling the AccessibleContext.getAccessibleText() method of
AccessibleContext. |
| AccessibleHypertext |
The AccessibleHypertext class is the base class for all
classes that present hypertext information on the display. |
| AccessibleIcon |
The AccessibleIcon interface should be supported by any object
that has an associated icon (e.g., buttons). |
| AccessibleKeyBinding |
The AccessibleKeyBinding interface should be supported by any object
that has a keyboard bindings such as a keyboard mnemonic and/or keyboard
shortcut which can be used to select the object. |
| AccessibleSelection |
This AccessibleSelection interface
provides the standard mechanism for an assistive technology to determine
what the current selected children are, as well as modify the selection set. |
| AccessibleStreamable |
|
| AccessibleTable |
Class AccessibleTable describes a user-interface component that
presents data in a two-dimensional table format. |
| AccessibleTableModelChange |
The AccessibleTableModelChange interface describes a change to
the table model. |
| AccessibleText |
The AccessibleText interface should be implemented by all
classes that present textual information on the display. |
| AccessibleValue |
The AccessibleValue interface should be supported by any object
that supports a numerical value (e.g., a scroll bar). |
Package javax.accessibility Description
Defines a contract between user-interface components and an assistive technology
that provides access to those components. If a Java application fully supports
the Java Accessibility API, then it should be compatible with, and friendly
toward, assistive technologies such as screen readers, screen magnifiers,
etc. With a Java application that fully supports the Java Accessibility
API, no screen reader off screen model would be necessary because the API
provides all of the information normally contained in an off screen model.
The Java Accessibility API package consists of 8 Java programming language
interfaces, and 6 Java programming language classes. These are described
below.
Interface Accessible is the main interface
of the Java Accessibility API. All components that support the Java Accessibility
API must implement this interface. It contains a single method, getAccessibleContext,
that returns an instance of the class AccessibleContext.
Sun thinks that implementing this interface is the absolute minimum requirement
of every object that is part of the user interface of a Java application,
if that program is to be compatible with assistive technologies.
AccessibleContext represents the minimum
information all accessible objects return and is obtained by calling the
getAccessibleContext method on an object that implements the Accessible
interface. This information includes the accessible name, description,
role, and state
of the object, as well as information about the parent and children of
the object. In addition, JavaBeans TM
property change support is also included to allow assisitive technologies
learn when the values of the accessible properties change. AccessibleContext
also contains methods for obtaining more specific accessibility information
about a component. If the component supports it, these methods will return
an object that implements one or more of the following interfaces:
-
AccessibleAction - the object can
perform one or more actions. This interface provides the standard mechanism
for an assistive technology to determine what those actions are and tell
the object to perform those actions. Any object that can be manipulated
should return an object that implements this interface when the getAccessibleAction
method is called on an AccessibleContext.
-
AccessibleComponent - the object
has a graphical representation. This interface provides the standard mechanism
for an assistive technology to determine and set the graphical representation
of the object. Any object that is rendered on the screen should return
an object that implements this interface when the getAccessibleComponent
method is called on an AccessibleContext.
-
AccessibleSelection - the object
allows its children to be selected. This interface provides the standard
mechanism for an assistive technology to determine the currently selected
children as well as modify the selection set. Any object that has children
that can be selected should return an object that implements this interface
when the getAccessibleSelection method is called on an AccessibleContext.
-
AccessibleText - the object presents
editable textual information on the display. This interface provides the
standard mechanism for an assistive technology to access that text via
its content, attributes, and spatial location. Any object that contains
editable text should return an object that implements this interface when
the getAccessibleText method is called on an AccessibleContext.
-
AccessibleHypertext - the object
presents hypertext information on the display. This interface provides
the standard mechanism for an assistive technology to access that hypertext
via its content, attributes, and spatial location. Any object that contains
hypertext should return an object that implements this interface when the
getAccessibleText method is called on an AccessibleContext.
-
AccessibleValue - the object supports
a numerical value. This interface provides the standard mechanism for an
assistive technology to determine and set the current value of the object,
as well as the minimum and maximum values. Any object that supports a numerical
value should return an object that implements this interface when the getAccessibleValue
method is called on an AccessibleContext.
This class encapsulates the Accessible object's role in the user interface
and is obtained by calling the getAccessibleRole method on an
AccessibleContext. Accessible roles include
"Check box", "Menu Item", "Panel", etc. These roles are identified by the
constants in this class such as AccessibleRole.CHECK_BOX, AccessibleRole.MENU_ITEM,
and AccessibleRole.PANEL. The constants in this class present
a strongly typed enumeration of common object roles. A public constructor
for this class has been purposely omitted and applications should use one
of the constants from this class. Although this class pre-defines a large
list of standard roles, it is extensible so additional programmer-defined
roles can be added in the future without needing to modify the base class.
This class encapsulates a particular state of the Accessible object. Accessible
states include things like "Armed", "Busy", "Checked", "Focused", etc.
These roles are identified by the constants in this class such as AccessibleState.ARMED,
AccessibleState.BUSY, AccessibleState.CHECKED, and AccessibleState.FOCUSED.
The sum of all the states of an Accessible object is called the AccessibleStateSet,
and can be obtained by calling the getAccessibleStateSet method
on an AccessibleContext.
The constants in this class present a strongly typed enumeration of
common object roles. A public constructor for this class has been purposely
omitted and applications should use one of the constants from this class.
Although this class pre-defines a large list of standard roles, it is extensible
so additional, programmer-defined roles can be added in the future without
needing to modify the base class.
This class encapsulates a collection of states of the Accessible object
and is obtained by calling the getAccessibleStateSet method on
an AccessibleContext. Since an object
might have multiple states (e.g. it might be both "Checked" and "Focused"),
this class is needed to encapsulate a collection of these states. Methods
in the class provide for retrieving the individual AccessibleStates
on the state set.
This class is used to maintain a strongly typed enumeration. It is the
super class of both the AccessibleRole and
AccessibleState classes. Programmers normally
do not interact with this class directly, but will instead use the AccessibleRole
and AccessibleState classes.
The AccessibleAction interface should
be supported by any object that can perform one or more actions. This interface
provides the standard mechanism for an assistive technology to determine
what those actions are as well as tell the object to perform those actions.
Any object that can be manipulated should support this interface.
Applications can determine if an object supports the AccessibleAction
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the getAccessibleAction
method of AccessibleContext. If the return
value is not null, the object supports this interface.
The AccessibleComponent interface
should be supported by any object that is rendered on the screen. This
interface provides the standard mechanism for an assistive technology to
determine and set the graphical representation of an object.
Applications can determine if an object supports the AccessibleComponent
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the getAccessibleComponent
method of AccessibleContext. If the return
value is not null, the object supports this interface.
The AccessibleSelection interface
provides the standard mechanism for an assistive technology to determine
what the current selected children are, as well as modify the selection
set. Any object that has children that can be selected should support this
the AccessibleSelection interface.
Applications can determine if an object supports the AccessibleSelection
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the getAccessibleSelection
method of AccessibleContext. If the return
value is not null, the object supports this interface.
Interface AccessibleText is the contract
for making rich, editable text Accessible. Not all text displayed on the
screen is rich and editable (e.g. text contained in buttons, labels, menus,
etc., which users aren't expected to manipulate). However, objects containing
editable text must implement interface AccessibleText if they are to interoperate
with assistive technologies.
This interface provides support for going between pixel coordinates
and the text at a given pixel coordinate, for retrieving the letter, word,
and sentence at, before, or after a given position in the text. This interface
provides support for retrieving the attributes of the character at a given
position in the text (font, font size, style, etc.), as well as getting
the selected text (if any), the length of the text, and the location of
the text caret.
Applications can determine if an object supports the AccessibleText
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the getAccessibleText
method of AccessibleContext. If the return
value is not null, the object supports this interface.
The AccessibleHypertext interface
should be supported by any object that presents hypertext information on
the display. This interface provides the standard mechanism for an assistive
technology to access that text via its content, attributes, and spatial
location. It also provides standard mechanisms for manipulating hyperlinks.
Applications can determine if an object supports the AccessibleHypertext
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the AccessibleContext.getAccessibleText()
method of AccessibleContext. If the return
value is a class which extends AccessibleHypertext, then that object supports
AccessibleHypertext.
An object that is a hyperlink should support the AccessibleHyperlink
interface. An object that implements this interface will be returned
by calling the getLink method on an AccessibleHypertext
object.
The AccessibleValue interface should
be supported by any object that supports a numerical value (e.g., a scroll
bar). This interface provides the standard mechanism for an assistive technology
to determine and set the numerical value as well as get the minimum and
maximum values.
Applications can determine if an object supports the AccessibleValue
interface by first obtaining its AccessibleContext
(see Accessible) and then calling the getAccessibleValue
method of AccessibleContext. If the return
value is not null, the object supports this interface.
- Since:
- JDK1.2
Submit a bug or feature
For further API reference and developer documentation, see Java 2 SDK SE Developer Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples. Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.


Controls: Arrow Keys/WASD: Move; Shift: Run;
Note: Touch screen supported Upper area: Jump; Lower-right area: Run right; Lower-left area: Run left;


Neighborhood:
Room Type:
Total Number of Listings of the owner:
Number of Reviews on the listing:
Minimum Nights
Number of days per year available:
Last Review Time (TODO)


Class: AutomationObject::BluePrint::Composite::Hook
- Defined in:
- lib/automation_object/blue_print/composite/hook.rb
Overview
Hook composite class
Instance Attribute Summary
Attributes inherited from Base
Instance Method Summary collapse
- #after ⇒ AutomationObject::BluePrint::Composite::HookAction
- #before ⇒ AutomationObject::BluePrint::Composite::HookAction
-
#changes ⇒ Array<Symbol>
Get possible changes.
- #changes_to_container?(name) ⇒ Boolean
-
#live? ⇒ Array<AutomationObject::BluePrint::Composite::HookElementRequirements>
Array of element requirements.
Methods inherited from Base
Constructor Details
This class inherits a constructor from AutomationObject::BluePrint::Composite::Base
Instance Method Details
#after ⇒ AutomationObject::BluePrint::Composite::HookAction
17 18 19 |
# File 'lib/automation_object/blue_print/composite/hook.rb', line 17 def after adapter.after end |
#before ⇒ AutomationObject::BluePrint::Composite::HookAction
12 13 14 |
# File 'lib/automation_object/blue_print/composite/hook.rb', line 12 def before adapter.before end |
#changes ⇒ Array<Symbol>
Get possible changes
28 29 30 31 |
# File 'lib/automation_object/blue_print/composite/hook.rb', line 28 def changes [before.change_screen, before.new_screen, after.change_screen, after.new_screen, before.show_modal, after.show_modal].uniq.compact end |
#changes_to_container?(name) ⇒ Boolean
35 36 37 |
# File 'lib/automation_object/blue_print/composite/hook.rb', line 35 def changes_to_container?(name) changes.include?(name) end |
#live? ⇒ Array<AutomationObject::BluePrint::Composite::HookElementRequirements>
Returns array of element requirements
22 23 24 |
# File 'lib/automation_object/blue_print/composite/hook.rb', line 22 def live? adapter.live? end |


Traffic Control¶
The vast majority of today’s Internet traffic is media files being sent from a single source to many thousands or even millions of destinations. Content Delivery Networks make that one-to-many distribution possible in an economical way.
Traffic Control is an Open Source implementation of a Content Delivery Network.
The following documentation sections are available:
CDN Basics¶
A review of the basic functionality of a Content Delivery Network.
Traffic Control Overview¶
An introduction to the Traffic Control architecture, components, and their integration.
Administrator’s Guide¶
How to deploy and manage a Traffic Control CDN.
- Administrator’s Guide
- Traffic Ops - Installing
- Traffic Ops - Default Profiles
- Traffic Ops - Migrating from 1.x to 2.x
- Traffic Ops - Migrating from 2.0 to 2.2
- Traffic Ops - Configuring
- Traffic Ops - Using
- Managing Traffic Ops Extensions
- Traffic Portal Administration
- Traffic Portal - Using
- Traffic Monitor Administration (Legacy)
- Traffic Monitor Administration
- Traffic Router Administration
- Traffic Stats Administration
- Traffic Server Administration
- Traffic Vault Administration
- Quick How To Guides
Developer’s Guide¶
A guide to the various internal and external APIs, and an introduction for the Traffic Control developer.
APIs¶
A guide to external RESTful APIs for Traffic Ops
- APIs
- API Overview
- API Routes
- API 1.1 Reference
- API 1.2 Reference
- API-Capabilities
- ASN
- Cache
- Cache Group
- Cache Group parameters
- Cache Group Fallback
- Cache Statistics
- Capabilities
- CDN
- Change Logs
- Config Files and Config File Metadata
- Delivery Service
- Delivery Service Regexes
- Delivery Service Statistics
- Divisions
- Federation
- Federation Delivery Service
- Federation Federation Resolver
- Federation Resolver
- Federation User
- Hardware Info
- ISO
- Jobs
- Parameter
- Physical Location
- Profiles
- Profile parameters
- InfluxDB
- Regions
- Roles
- Server
- Static DNS Entries
- Status
- Steering Targets
- System
- Tenants
- TO Extensions
- Types
- Users
- Snapshot CRConfig
- API 1.3 Reference


The Full Tankard
Home
Beer
Brewers
Articles
Contact
Home
Beer
Brewers
Articles
Contact
menu
search
Search by keyword
Number of Articles
Year Range
Find Articles
Please fill some keyword in the search engine:)
OK


Welcome to the website of the Paradixm project. This site aims to provide a no-holds-barred catalog of user interface elements, designs, and behaviors across platforms and across time.
The long-term goal of the Paradixm project is to serve as the basis for a broad-based, best-of-breed user interface vision that can accommodate users of all levels of proficiency as well as devices with varying display and interaction technologies. The very feasibility of this goal remains to be seen, but we have to start somewhere, right?


Delta Electronics.
aka >> Farhadi.biz
🡲 CCTV, Solar sys
urban sign and tv, etc.
🡲 Let's trade :)
International sell and delivery


TCPDUMP
Section: Maintenance Commands (8)Updated: 05 March 2009
Index Return to Main Contents
NAME
tcpdump - dump traffic on a networkSYNOPSIS
tcpdump [ -AdDefIKlLnNOpqRStuUvxX ] [ -B buffer_size ] [ -c count ][ -C file_size ] [ -G rotate_seconds ] [ -F file ]
[ -i interface ] [ -m module ] [ -M secret ]
[ -r file ] [ -s snaplen ] [ -T type ] [ -w file ]
[ -W filecount ]
[ -E spi@ipaddr algo:secret,... ]
[ -y datalinktype ] [ -z postrotate-command ] [ -Z user ]
[ expression ]
DESCRIPTION
Tcpdump prints out a description of the contents of packets on a network interface that match the boolean expression. It can also be run with the -w flag, which causes it to save the packet data to a file for later analysis, and/or with the -r flag, which causes it to read from a saved packet file rather than to read packets from a network interface. In all cases, only packets that match expression will be processed by tcpdump.
Tcpdump will, if not run with the -c flag, continue capturing packets until it is interrupted by a SIGINT signal (generated, for example, by typing your interrupt character, typically control-C) or a SIGTERM signal (typically generated with the kill(1) command); if run with the -c flag, it will capture packets until it is interrupted by a SIGINT or SIGTERM signal or the specified number of packets have been processed.
When tcpdump finishes capturing packets, it will report counts of:
- packets ``captured'' (this is the number of packets that tcpdump has received and processed);
- packets ``received by filter'' (the meaning of this depends on the OS on which you're running tcpdump, and possibly on the way the OS was configured - if a filter was specified on the command line, on some OSes it counts packets regardless of whether they were matched by the filter expression and, even if they were matched by the filter expression, regardless of whether tcpdump has read and processed them yet, on other OSes it counts only packets that were matched by the filter expression regardless of whether tcpdump has read and processed them yet, and on other OSes it counts only packets that were matched by the filter expression and were processed by tcpdump);
- packets ``dropped by kernel'' (this is the number of packets that were dropped, due to a lack of buffer space, by the packet capture mechanism in the OS on which tcpdump is running, if the OS reports that information to applications; if not, it will be reported as 0).
On platforms that support the SIGINFO signal, such as most BSDs (including Mac OS X) and Digital/Tru64 UNIX, it will report those counts when it receives a SIGINFO signal (generated, for example, by typing your ``status'' character, typically control-T, although on some platforms, such as Mac OS X, the ``status'' character is not set by default, so you must set it with stty(1) in order to use it) and will continue capturing packets.
Reading packets from a network interface may require that you have special privileges; see the pcap (3PCAP) man page for details. Reading a saved packet file doesn't require special privileges.
OPTIONS
- -A
- Print each packet (minus its link level header) in ASCII. Handy for capturing web pages.
- -B
- Set the operating system capture buffer size to buffer_size.
- -c
- Exit after receiving count packets.
- -C
-
Before writing a raw packet to a savefile, check whether the file is
currently larger than file_size and, if so, close the current
savefile and open a new one. Savefiles after the first savefile will
have the name specified with the
-w
flag, with a number after it, starting at 1 and continuing upward.
The units of file_size are millions of bytes (1,000,000 bytes,
not 1,048,576 bytes).
Note that when used with -Z option (enabled by default), privileges are dropped before opening first savefile.
- -d
- Dump the compiled packet-matching code in a human readable form to standard output and stop.
- -dd
- Dump packet-matching code as a C program fragment.
- -ddd
- Dump packet-matching code as decimal numbers (preceded with a count).
- -D
- Print the list of the network interfaces available on the system and on which tcpdump can capture packets. For each network interface, a number and an interface name, possibly followed by a text description of the interface, is printed. The interface name or the number can be supplied to the -i flag to specify an interface on which to capture.
- This can be useful on systems that don't have a command to list them (e.g., Windows systems, or UNIX systems lacking ifconfig -a); the number can be useful on Windows 2000 and later systems, where the interface name is a somewhat complex string.
- The -D flag will not be supported if tcpdump was built with an older version of libpcap that lacks the pcap_findalldevs() function.
- -e
- Print the link-level header on each dump line.
- -E
- Use spi@ipaddr algo:secret for decrypting IPsec ESP packets that are addressed to addr and contain Security Parameter Index value spi. This combination may be repeated with comma or newline seperation.
- Note that setting the secret for IPv4 ESP packets is supported at this time.
- Algorithms may be des-cbc, 3des-cbc, blowfish-cbc, rc3-cbc, cast128-cbc, or none. The default is des-cbc. The ability to decrypt packets is only present if tcpdump was compiled with cryptography enabled.
- secret is the ASCII text for ESP secret key. If preceeded by 0x, then a hex value will be read.
- The option assumes RFC2406 ESP, not RFC1827 ESP. The option is only for debugging purposes, and the use of this option with a true `secret' key is discouraged. By presenting IPsec secret key onto command line you make it visible to others, via ps(1) and other occasions.
- In addition to the above syntax, the syntax file name may be used to have tcpdump read the provided file in. The file is opened upon receiving the first ESP packet, so any special permissions that tcpdump may have been given should already have been given up.
- -f
- Print `foreign' IPv4 addresses numerically rather than symbolically (this option is intended to get around serious brain damage in Sun's NIS server --- usually it hangs forever translating non-local internet numbers).
- The test for `foreign' IPv4 addresses is done using the IPv4 address and netmask of the interface on which capture is being done. If that address or netmask are not available, available, either because the interface on which capture is being done has no address or netmask or because the capture is being done on the Linux "any" interface, which can capture on more than one interface, this option will not work correctly.
- -F
- Use file as input for the filter expression. An additional expression given on the command line is ignored.
- -G
- If specified, rotates the dump file specified with the -w option every rotate_seconds seconds. Savefiles will have the name specified by -w which should include a time format as defined by strftime(3). If no time format is specified, each new file will overwrite the previous.
- If used in conjunction with the -C option, filenames will take the form of `file<count>'.
- -i
- Listen on interface. If unspecified, tcpdump searches the system interface list for the lowest numbered, configured up interface (excluding loopback). Ties are broken by choosing the earliest match.
- On Linux systems with 2.2 or later kernels, an interface argument of ``any'' can be used to capture packets from all interfaces. Note that captures on the ``any'' device will not be done in promiscuous mode.
- If the -D flag is supported, an interface number as printed by that flag can be used as the interface argument.
- -I
- Put the interface in "monitor mode"; this is supported only on IEEE 802.11 Wi-Fi interfaces, and supported only on some operating systems.
- Note that in monitor mode the adapter might disassociate from the network with which it's associated, so that you will not be able to use any wireless networks with that adapter. This could prevent accessing files on a network server, or resolving host names or network addresses, if you are capturing in monitor mode and are not connected to another network with another adapter.
- This flag will affect the output of the -L flag. If -I isn't specified, only those link-layer types available when not in monitor mode will be shown; if -I is specified, only those link-layer types available when in monitor mode will be shown.
- -K
- Don't attempt to verify IP, TCP, or UDP checksums. This is useful for interfaces that perform some or all of those checksum calculation in hardware; otherwise, all outgoing TCP checksums will be flagged as bad.
- -l
-
Make stdout line buffered.
Useful if you want to see the data
while capturing it.
E.g.,
``tcpdump -l | tee dat'' or ``tcpdump -l > dat & tail -f dat''. - -L
- List the known data link types for the interface, in the specified mode, and exit. The list of known data link types may be dependent on the specified mode; for example, on some platforms, a Wi-Fi interface might support one set of data link types when not in monitor mode (for example, it might support only fake Ethernet headers, or might support 802.11 headers but not support 802.11 headers with radio information) and another set of data link types when in monitor mode (for example, it might support 802.11 headers, or 802.11 headers with radio information, only in monitor mode).
- -m
- Load SMI MIB module definitions from file module. This option can be used several times to load several MIB modules into tcpdump.
- -M
- Use secret as a shared secret for validating the digests found in TCP segments with the TCP-MD5 option (RFC 2385), if present.
- -n
- Don't convert host addresses to names. This can be used to avoid DNS lookups.
- -nn
- Don't convert protocol and port numbers etc. to names either.
- -N
- Don't print domain name qualification of host names. E.g., if you give this flag then tcpdump will print ``nic'' instead of ``nic.ddn.mil''.
- -O
- Do not run the packet-matching code optimizer. This is useful only if you suspect a bug in the optimizer.
- -p
- Don't put the interface into promiscuous mode. Note that the interface might be in promiscuous mode for some other reason; hence, `-p' cannot be used as an abbreviation for `ether host {local-hw-addr} or ether broadcast'.
- -q
- Quick (quiet?) output. Print less protocol information so output lines are shorter.
- -R
- Assume ESP/AH packets to be based on old specification (RFC1825 to RFC1829). If specified, tcpdump will not print replay prevention field. Since there is no protocol version field in ESP/AH specification, tcpdump cannot deduce the version of ESP/AH protocol.
- -r
- Read packets from file (which was created with the -w option). Standard input is used if file is ``-''.
- -S
- Print absolute, rather than relative, TCP sequence numbers.
- -s
- Snarf snaplen bytes of data from each packet rather than the default of 65535 bytes. Packets truncated because of a limited snapshot are indicated in the output with ``[|proto]'', where proto is the name of the protocol level at which the truncation has occurred. Note that taking larger snapshots both increases the amount of time it takes to process packets and, effectively, decreases the amount of packet buffering. This may cause packets to be lost. You should limit snaplen to the smallest number that will capture the protocol information you're interested in. Setting snaplen to 0 sets it to the default of 65535, for backwards compatibility with recent older versions of tcpdump.
- -T
- Force packets selected by "expression" to be interpreted the specified type. Currently known types are aodv (Ad-hoc On-demand Distance Vector protocol), cnfp (Cisco NetFlow protocol), rpc (Remote Procedure Call), rtp (Real-Time Applications protocol), rtcp (Real-Time Applications control protocol), snmp (Simple Network Management Protocol), tftp (Trivial File Transfer Protocol), vat (Visual Audio Tool), and wb (distributed White Board).
- -t
- Don't print a timestamp on each dump line.
- -tt
- Print an unformatted timestamp on each dump line.
- -ttt
- Print a delta (micro-second resolution) between current and previous line on each dump line.
- -tttt
- Print a timestamp in default format proceeded by date on each dump line.
- -ttttt
- Print a delta (micro-second resolution) between current and first line on each dump line.
- -u
- Print undecoded NFS handles.
- -U
- Make output saved via the -w option ``packet-buffered''; i.e., as each packet is saved, it will be written to the output file, rather than being written only when the output buffer fills.
- The -U flag will not be supported if tcpdump was built with an older version of libpcap that lacks the pcap_dump_flush() function.
- -v
- When parsing and printing, produce (slightly more) verbose output. For example, the time to live, identification, total length and options in an IP packet are printed. Also enables additional packet integrity checks such as verifying the IP and ICMP header checksum.
- When writing to a file with the -w option, report, every 10 seconds, the number of packets captured.
- -vv
- Even more verbose output. For example, additional fields are printed from NFS reply packets, and SMB packets are fully decoded.
- -vvv
- Even more verbose output. For example, telnet SB ... SE options are printed in full. With -X Telnet options are printed in hex as well.
- -w
- Write the raw packets to file rather than parsing and printing them out. They can later be printed with the -r option. Standard output is used if file is ``-''. See pcap-savefile(5) for a description of the file format.
- -W
- Used in conjunction with the -C option, this will limit the number of files created to the specified number, and begin overwriting files from the beginning, thus creating a 'rotating' buffer. In addition, it will name the files with enough leading 0s to support the maximum number of files, allowing them to sort correctly.
- Used in conjunction with the -G option, this will limit the number of rotated dump files that get created, exiting with status 0 when reaching the limit. If used with -C as well, the behavior will result in cyclical files per timeslice.
- -x
- When parsing and printing, in addition to printing the headers of each packet, print the data of each packet (minus its link level header) in hex. The smaller of the entire packet or snaplen bytes will be printed. Note that this is the entire link-layer packet, so for link layers that pad (e.g. Ethernet), the padding bytes will also be printed when the higher layer packet is shorter than the required padding.
- -xx
- When parsing and printing, in addition to printing the headers of each packet, print the data of each packet, including its link level header, in hex.
- -X
- When parsing and printing, in addition to printing the headers of each packet, print the data of each packet (minus its link level header) in hex and ASCII. This is very handy for analysing new protocols.
- -XX
- When parsing and printing, in addition to printing the headers of each packet, print the data of each packet, including its link level header, in hex and ASCII.
- -y
- Set the data link type to use while capturing packets to datalinktype.
- -z
- Used in conjunction with the -C or -G options, this will make tcpdump run " command file " where file is the savefile being closed after each rotation. For example, specifying -z gzip or -z bzip2 will compress each savefile using gzip or bzip2.
- Note that tcpdump will run the command in parallel to the capture, using the lowest priority so that this doesn't disturb the capture process.
- And in case you would like to use a command that itself takes flags or different arguments, you can always write a shell script that will take the savefile name as the only argument, make the flags & arguments arrangements and execute the command that you want.
- -Z
- Drops privileges (if root) and changes user ID to user and the group ID to the primary group of user.
-
This behavior is enabled by default (-Z tcpdump), and can
be disabled by -Z root.
- expression
-
-
selects which packets will be dumped.
If no expression
is given, all packets on the net will be dumped.
Otherwise,
only packets for which expression is `true' will be dumped.
For the expression syntax, see pcap-filter(7).
Expression arguments can be passed to tcpdump as either a single argument or as multiple arguments, whichever is more convenient. Generally, if the expression contains Shell metacharacters, it is easier to pass it as a single, quoted argument. Multiple arguments are concatenated with spaces before being parsed.
-
selects which packets will be dumped.
If no expression
is given, all packets on the net will be dumped.
Otherwise,
only packets for which expression is `true' will be dumped.
EXAMPLES
To print all packets arriving at or departing from sundown:
-
tcpdump host sundown
To print traffic between helios and either hot or ace:
-
tcpdump host helios and \( hot or ace \)
To print all IP packets between ace and any host except helios:
-
tcpdump ip host ace and not helios
To print all traffic between local hosts and hosts at Berkeley:
-
tcpdump net ucb-ether
To print all ftp traffic through internet gateway snup: (note that the expression is quoted to prevent the shell from (mis-)interpreting the parentheses):
-
tcpdump 'gateway snup and (port ftp or ftp-data)'
To print traffic neither sourced from nor destined for local hosts (if you gateway to one other net, this stuff should never make it onto your local net).
-
tcpdump ip and not net localnet
To print the start and end packets (the SYN and FIN packets) of each TCP conversation that involves a non-local host.
-
tcpdump 'tcp[tcpflags] & (tcp-syn|tcp-fin) != 0 and not src and dst net localnet'
To print all IPv4 HTTP packets to and from port 80, i.e. print only packets that contain data, not, for example, SYN and FIN packets and ACK-only packets. (IPv6 is left as an exercise for the reader.)
-
tcpdump 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)'
To print IP packets longer than 576 bytes sent through gateway snup:
-
tcpdump 'gateway snup and ip[2:2] > 576'
To print IP broadcast or multicast packets that were not sent via Ethernet broadcast or multicast:
-
tcpdump 'ether[0] & 1 = 0 and ip[16] >= 224'
To print all ICMP packets that are not echo requests/replies (i.e., not ping packets):
-
tcpdump 'icmp[icmptype] != icmp-echo and icmp[icmptype] != icmp-echoreply'
OUTPUT FORMAT
The output of tcpdump is protocol dependent. The following gives a brief description and examples of most of the formats.
Link Level Headers
If the '-e' option is given, the link level header is printed out. On Ethernets, the source and destination addresses, protocol, and packet length are printed.
On FDDI networks, the '-e' option causes tcpdump to print the `frame control' field, the source and destination addresses, and the packet length. (The `frame control' field governs the interpretation of the rest of the packet. Normal packets (such as those containing IP datagrams) are `async' packets, with a priority value between 0 and 7; for example, `async4'. Such packets are assumed to contain an 802.2 Logical Link Control (LLC) packet; the LLC header is printed if it is not an ISO datagram or a so-called SNAP packet.
On Token Ring networks, the '-e' option causes tcpdump to print the `access control' and `frame control' fields, the source and destination addresses, and the packet length. As on FDDI networks, packets are assumed to contain an LLC packet. Regardless of whether the '-e' option is specified or not, the source routing information is printed for source-routed packets.
On 802.11 networks, the '-e' option causes tcpdump to print the `frame control' fields, all of the addresses in the 802.11 header, and the packet length. As on FDDI networks, packets are assumed to contain an LLC packet.
(N.B.: The following description assumes familiarity with the SLIP compression algorithm described in RFC-1144.)
On SLIP links, a direction indicator (``I'' for inbound, ``O'' for outbound), packet type, and compression information are printed out. The packet type is printed first. The three types are ip, utcp, and ctcp. No further link information is printed for ip packets. For TCP packets, the connection identifier is printed following the type. If the packet is compressed, its encoded header is printed out. The special cases are printed out as *S+n and *SA+n, where n is the amount by which the sequence number (or sequence number and ack) has changed. If it is not a special case, zero or more changes are printed. A change is indicated by U (urgent pointer), W (window), A (ack), S (sequence number), and I (packet ID), followed by a delta (+n or -n), or a new value (=n). Finally, the amount of data in the packet and compressed header length are printed.
For example, the following line shows an outbound compressed TCP packet, with an implicit connection identifier; the ack has changed by 6, the sequence number by 49, and the packet ID by 6; there are 3 bytes of data and 6 bytes of compressed header:
-
O ctcp * A+6 S+49 I+6 3 (6)
ARP/RARP Packets
Arp/rarp output shows the type of request and its arguments. The format is intended to be self explanatory. Here is a short sample taken from the start of an `rlogin' from host rtsg to host csam:
-
arp who-has csam tell rtsg arp reply csam is-at CSAM
This would look less redundant if we had done tcpdump -n:
-
arp who-has <IP_ADDRESS> tell <IP_ADDRESS> arp reply <IP_ADDRESS> is-at 02:07:01:00:01:c4
If we had done tcpdump -e, the fact that the first packet is broadcast and the second is point-to-point would be visible:
-
RTSG Broadcast 0806 64: arp who-has csam tell rtsg CSAM RTSG 0806 64: arp reply csam is-at CSAM
TCP Packets
(N.B.:The following description assumes familiarity with the TCP protocol described in RFC-793. If you are not familiar with the protocol, neither this description nor tcpdump will be of much use to you.)
The general format of a tcp protocol line is:
-
src > dst: flags data-seqno ack window urgent options
Src, dst and flags are always present. The other fields depend on the contents of the packet's tcp protocol header and are output only if appropriate.
Here is the opening portion of an rlogin from host rtsg to host csam.
-
rtsg.1023 > csam.login: S 768512:768512(0) win 4096 <mss 1024> csam.login > rtsg.1023: S 947648:947648(0) ack 768513 win 4096 <mss 1024> rtsg.1023 > csam.login: . ack 1 win 4096 rtsg.1023 > csam.login: P 1:2(1) ack 1 win 4096 csam.login > rtsg.1023: . ack 2 win 4096 rtsg.1023 > csam.login: P 2:21(19) ack 1 win 4096 csam.login > rtsg.1023: P 1:2(1) ack 21 win 4077 csam.login > rtsg.1023: P 2:3(1) ack 21 win 4077 urg 1 csam.login > rtsg.1023: P 3:4(1) ack 21 win 4077 urg 1
Csam replies with a similar packet except it includes a piggy-backed ack for rtsg's SYN. Rtsg then acks csam's SYN. The `.' means no flags were set. The packet contained no data so there is no data sequence number. Note that the ack sequence number is a small integer (1). The first time tcpdump sees a tcp `conversation', it prints the sequence number from the packet. On subsequent packets of the conversation, the difference between the current packet's sequence number and this initial sequence number is printed. This means that sequence numbers after the first can be interpreted as relative byte positions in the conversation's data stream (with the first data byte each direction being `1'). `-S' will override this feature, causing the original sequence numbers to be output.
On the 6th line, rtsg sends csam 19 bytes of data (bytes 2 through 20 in the rtsg -> csam side of the conversation). The PUSH flag is set in the packet. On the 7th line, csam says it's received data sent by rtsg up to but not including byte 21. Most of this data is apparently sitting in the socket buffer since csam's receive window has gotten 19 bytes smaller. Csam also sends one byte of data to rtsg in this packet. On the 8th and 9th lines, csam sends two bytes of urgent, pushed data to rtsg.
If the snapshot was small enough that tcpdump didn't capture the full TCP header, it interprets as much of the header as it can and then reports ``[|tcp]'' to indicate the remainder could not be interpreted. If the header contains a bogus option (one with a length that's either too small or beyond the end of the header), tcpdump reports it as ``[bad opt]'' and does not interpret any further options (since it's impossible to tell where they start). If the header length indicates options are present but the IP datagram length is not long enough for the options to actually be there, tcpdump reports it as ``[bad hdr length]''.
Capturing TCP packets with particular flag combinations (SYN-ACK, URG-ACK, etc.)
There are 8 bits in the control bits section of the TCP header:
- CWR | ECE | URG | ACK | PSH | RST | SYN | FIN
Let's assume that we want to watch packets used in establishing a TCP connection. Recall that TCP uses a 3-way handshake protocol when it initializes a new connection; the connection sequence with regard to the TCP control bits is
- 1) Caller sends SYN
- 2) Recipient responds with SYN, ACK
- 3) Caller sends ACK
Now we're interested in capturing packets that have only the SYN bit set (Step 1). Note that we don't want packets from step 2 (SYN-ACK), just a plain initial SYN. What we need is a correct filter expression for tcpdump.
Recall the structure of a TCP header without options:
0 15 31 ----------------------------------------------------------------- | source port | destination port | ----------------------------------------------------------------- | sequence number | ----------------------------------------------------------------- | acknowledgment number | ----------------------------------------------------------------- | HL | rsvd |C|E|U|A|P|R|S|F| window size | ----------------------------------------------------------------- | TCP checksum | urgent pointer | -----------------------------------------------------------------
A TCP header usually holds 20 octets of data, unless options are present. The first line of the graph contains octets 0 - 3, the second line shows octets 4 - 7 etc.
Starting to count with 0, the relevant TCP control bits are contained in octet 13:
0 7| 15| 23| 31 ----------------|---------------|---------------|---------------- | HL | rsvd |C|E|U|A|P|R|S|F| window size | ----------------|---------------|---------------|---------------- | | 13th octet | | |
Let's have a closer look at octet no. 13:
| | |---------------| |C|E|U|A|P|R|S|F| |---------------| |7 5 3 0|
These are the TCP control bits we are interested in. We have numbered the bits in this octet from 0 to 7, right to left, so the PSH bit is bit number 3, while the URG bit is number 5.
Recall that we want to capture packets with only SYN set. Let's see what happens to octet 13 if a TCP datagram arrives with the SYN bit set in its header:
|C|E|U|A|P|R|S|F| |---------------| |0 0 0 0 0 0 1 0| |---------------| |7 6 5 4 3 2 1 0|
Looking at the control bits section we see that only bit number 1 (SYN) is set.
Assuming that octet number 13 is an 8-bit unsigned integer in network byte order, the binary value of this octet is
- 00000010
and its decimal representation is
7 6 5 4 3 2 1 0 0*2 + 0*2 + 0*2 + 0*2 + 0*2 + 0*2 + 1*2 + 0*2 = 2
We're almost done, because now we know that if only SYN is set, the value of the 13th octet in the TCP header, when interpreted as a 8-bit unsigned integer in network byte order, must be exactly 2.
This relationship can be expressed as
- tcp[13] == 2
We can use this expression as the filter for tcpdump in order to watch packets which have only SYN set:
- tcpdump -i xl0 tcp[13] == 2
The expression says "let the 13th octet of a TCP datagram have the decimal value 2", which is exactly what we want.
Now, let's assume that we need to capture SYN packets, but we don't care if ACK or any other TCP control bit is set at the same time. Let's see what happens to octet 13 when a TCP datagram with SYN-ACK set arrives:
|C|E|U|A|P|R|S|F| |---------------| |0 0 0 1 0 0 1 0| |---------------| |7 6 5 4 3 2 1 0|
Now bits 1 and 4 are set in the 13th octet. The binary value of octet 13 is
-
00010010
which translates to decimal
7 6 5 4 3 2 1 0 0*2 + 0*2 + 0*2 + 1*2 + 0*2 + 0*2 + 1*2 + 0*2 = 18
Now we can't just use 'tcp[13] == 18' in the tcpdump filter expression, because that would select only those packets that have SYN-ACK set, but not those with only SYN set. Remember that we don't care if ACK or any other control bit is set as long as SYN is set.
In order to achieve our goal, we need to logically AND the binary value of octet 13 with some other value to preserve the SYN bit. We know that we want SYN to be set in any case, so we'll logically AND the value in the 13th octet with the binary value of a SYN:
00010010 SYN-ACK 00000010 SYN AND 00000010 (we want SYN) AND 00000010 (we want SYN) -------- -------- = 00000010 = 00000010
We see that this AND operation delivers the same result regardless whether ACK or another TCP control bit is set. The decimal representation of the AND value as well as the result of this operation is 2 (binary 00000010), so we know that for packets with SYN set the following relation must hold true:
- ( ( value of octet 13 ) AND ( 2 ) ) == ( 2 )
This points us to the tcpdump filter expression
-
tcpdump -i xl0 'tcp[13] & 2 == 2'
Note that you should use single quotes or a backslash in the expression to hide the AND ('&') special character from the shell.
UDP Packets
UDP format is illustrated by this rwho packet:
-
actinide.who > broadcast.who: udp 84
Some UDP services are recognized (from the source or destination port number) and the higher level protocol information printed. In particular, Domain Name service requests (RFC-1034/1035) and Sun RPC calls (RFC-1050) to NFS.
UDP Name Server Requests
(N.B.:The following description assumes familiarity with the Domain Service protocol described in RFC-1035. If you are not familiar with the protocol, the following description will appear to be written in greek.)
Name server requests are formatted as
-
src > dst: id op? flags qtype qclass name (len) h2opolo.1538 > helios.domain: 3+ A? ucbvax.berkeley.edu. (37)
A few anomalies are checked and may result in extra fields enclosed in square brackets: If a query contains an answer, authority records or additional records section, ancount, nscount, or arcount are printed as `[na]', `[nn]' or `[nau]' where n is the appropriate count. If any of the response bits are set (AA, RA or rcode) or any of the `must be zero' bits are set in bytes two and three, `[b2&3=x]' is printed, where x is the hex value of header bytes two and three.
UDP Name Server Responses
Name server responses are formatted as
-
src > dst: id op rcode flags a/n/au type class data (len) helios.domain > h2opolo.1538: 3 3/3/7 A <IP_ADDRESS> (273) helios.domain > h2opolo.1537: 2 NXDomain* 0/1/0 (97)
In the second example, helios responds to query 2 with a response code of non-existent domain (NXDomain) with no answers, one name server and no authority records. The `*' indicates that the authoritative answer bit was set. Since there were no answers, no type, class or data were printed.
Other flag characters that might appear are `-' (recursion available, RA, not set) and `|' (truncated message, TC, set). If the `question' section doesn't contain exactly one entry, `[nq]' is printed.
SMB/CIFS decoding
tcpdump now includes fairly extensive SMB/CIFS/NBT decoding for data on UDP/137, UDP/138 and TCP/139. Some primitive decoding of IPX and NetBEUI SMB data is also done.
By default a fairly minimal decode is done, with a much more detailed decode done if -v is used. Be warned that with -v a single SMB packet may take up a page or more, so only use -v if you really want all the gory details.
For information on SMB packet formats and what all te fields mean see www.cifs.org or the pub/samba/specs/ directory on your favorite samba.org mirror site. The SMB patches were written by Andrew Tridgell (tridge@samba.org).
NFS Requests and Replies
Sun NFS (Network File System) requests and replies are printed as:
-
src.xid > dst.nfs: len op args src.nfs > dst.xid: reply stat len op results sushi.6709 > wrl.nfs: 112 readlink fh 21,24/10.73165 wrl.nfs > sushi.6709: reply ok 40 readlink "../var" sushi.201b > wrl.nfs: 144 lookup fh 9,74/4096.6878 "xcolors" wrl.nfs > sushi.201b: reply ok 128 lookup fh 9,74/4134.3150
In the third line, sushi asks wrl to lookup the name `xcolors' in directory file 9,74/4096.6878. Note that the data printed depends on the operation type. The format is intended to be self explanatory if read in conjunction with an NFS protocol spec.
If the -v (verbose) flag is given, additional information is printed. For example:
-
sushi.1372a > wrl.nfs: 148 read fh 21,11/12.195 8192 bytes @ 24576 wrl.nfs > sushi.1372a: reply ok 1472 read REG 100664 ids 417/0 sz 29388
If the -v flag is given more than once, even more details are printed.
Note that NFS requests are very large and much of the detail won't be printed unless snaplen is increased. Try using `-s 192' to watch NFS traffic.
NFS reply packets do not explicitly identify the RPC operation. Instead, tcpdump keeps track of ``recent'' requests, and matches them to the replies using the transaction ID. If a reply does not closely follow the corresponding request, it might not be parsable.
AFS Requests and Replies
Transarc AFS (Andrew File System) requests and replies are printed as:
-
src.sport > dst.dport: rx packet-type src.sport > dst.dport: rx packet-type service call call-name args src.sport > dst.dport: rx packet-type service reply call-name args elvis.7001 > pike.afsfs: rx data fs call rename old fid 536876964/1/1 ".newsrc.new" new fid 536876964/1/1 ".newsrc" pike.afsfs > elvis.7001: rx data fs reply rename
In general, all AFS RPCs are decoded at least by RPC call name. Most AFS RPCs have at least some of the arguments decoded (generally only the `interesting' arguments, for some definition of interesting).
The format is intended to be self-describing, but it will probably not be useful to people who are not familiar with the workings of AFS and RX.
If the -v (verbose) flag is given twice, acknowledgement packets and additional header information is printed, such as the the RX call ID, call number, sequence number, serial number, and the RX packet flags.
If the -v flag is given twice, additional information is printed, such as the the RX call ID, serial number, and the RX packet flags. The MTU negotiation information is also printed from RX ack packets.
If the -v flag is given three times, the security index and service id are printed.
Error codes are printed for abort packets, with the exception of Ubik beacon packets (because abort packets are used to signify a yes vote for the Ubik protocol).
Note that AFS requests are very large and many of the arguments won't be printed unless snaplen is increased. Try using `-s 256' to watch AFS traffic.
AFS reply packets do not explicitly identify the RPC operation. Instead, tcpdump keeps track of ``recent'' requests, and matches them to the replies using the call number and service ID. If a reply does not closely follow the corresponding request, it might not be parsable.
KIP AppleTalk (DDP in UDP)
AppleTalk DDP packets encapsulated in UDP datagrams are de-encapsulated and dumped as DDP packets (i.e., all the UDP header information is discarded). The file /etc/atalk.names is used to translate AppleTalk net and node numbers to names. Lines in this file have the form
-
number name 1.254 ether 16.1 icsd-net 1.254.110 ace
AppleTalk addresses are printed in the form
-
net.host.port <IP_ADDRESS> > icsd-net.112.220 office.2 > icsd-net.112.220 jssmag.149.235 > icsd-net.2
NBP (name binding protocol) and ATP (AppleTalk transaction protocol) packets have their contents interpreted. Other protocols just dump the protocol name (or number if no name is registered for the protocol) and packet size.
NBP packets are formatted like the following examples:
-
icsd-net.112.220 > jssmag.2: nbp-lkup 190: "=:LaserWriter@*" jssmag.209.2 > icsd-net.112.220: nbp-reply 190: "RM1140:LaserWriter@*" 250 techpit.2 > icsd-net.112.220: nbp-reply 190: "techpit:LaserWriter@*" 186
ATP packet formatting is demonstrated by the following example:
-
jssmag.209.165 > helios.132: atp-req 12266<0-7> 0xae030001 helios.132 > jssmag.209.165: atp-resp 12266:0 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:1 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:2 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:3 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:4 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:5 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:6 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp*12266:7 (512) 0xae040000 jssmag.209.165 > helios.132: atp-req 12266<3,5> 0xae030001 helios.132 > jssmag.209.165: atp-resp 12266:3 (512) 0xae040000 helios.132 > jssmag.209.165: atp-resp 12266:5 (512) 0xae040000 jssmag.209.165 > helios.132: atp-rel 12266<0-7> 0xae030001 jssmag.209.133 > helios.132: atp-req* 12267<0-7> 0xae030002
Helios responds with 8 512-byte packets. The `:digit' following the transaction id gives the packet sequence number in the transaction and the number in parens is the amount of data in the packet, excluding the atp header. The `*' on packet 7 indicates that the EOM bit was set.
Jssmag.209 then requests that packets 3 & 5 be retransmitted. Helios resends them then jssmag.209 releases the transaction. Finally, jssmag.209 initiates the next request. The `*' on the request indicates that XO (`exactly once') was not set.
IP Fragmentation
Fragmented Internet datagrams are printed as
-
(frag id:size@offset+) (frag id:size@offset)
Id is the fragment id. Size is the fragment size (in bytes) excluding the IP header. Offset is this fragment's offset (in bytes) in the original datagram.
The fragment information is output for each fragment. The first fragment contains the higher level protocol header and the frag info is printed after the protocol info. Fragments after the first contain no higher level protocol header and the frag info is printed after the source and destination addresses. For example, here is part of an ftp from arizona.edu to lbl-rtsg.arpa over a CSNET connection that doesn't appear to handle 576 byte datagrams:
-
arizona.ftp-data > rtsg.1170: . 1024:1332(308) ack 1 win 4096 (frag 595a:328@0+) arizona > rtsg: (frag 595a:204@328) rtsg.1170 > arizona.ftp-data: . ack 1536 win 2560
A packet with the IP don't fragment flag is marked with a trailing (DF).
Timestamps
By default, all output lines are preceded by a timestamp. The timestamp is the current clock time in the form
-
hh:mm:ss.frac
SEE ALSO
stty(1), pcap(3PCAP), bpf(4), nit(4P), pcap-savefile(5), pcap-filter(7)AUTHORS
The original authors are:Van Jacobson, Craig Leres and Steven McCanne, all of the Lawrence Berkeley National Laboratory, University of California, Berkeley, CA.
It is currently being maintained by tcpdump.org.
The current version is available via http:
The original distribution is available via anonymous ftp:
IPv6/IPsec support is added by WIDE/KAME project. This program uses Eric Young's SSLeay library, under specific configurations.
BUGS
Please send problems, bugs, questions, desirable enhancements, patches etc. to:
NIT doesn't let you watch your own outbound traffic, BPF will. We recommend that you use the latter.
On Linux systems with 2.0[.x] kernels:
- packets on the loopback device will be seen twice;
- packet filtering cannot be done in the kernel, so that all packets must be copied from the kernel in order to be filtered in user mode;
- all of a packet, not just the part that's within the snapshot length, will be copied from the kernel (the 2.0[.x] packet capture mechanism, if asked to copy only part of a packet to userland, will not report the true length of the packet; this would cause most IP packets to get an error from tcpdump);
- capturing on some PPP devices won't work correctly.
We recommend that you upgrade to a 2.2 or later kernel.
Some attempt should be made to reassemble IP fragments or, at least to compute the right length for the higher level protocol.
Name server inverse queries are not dumped correctly: the (empty) question section is printed rather than real query in the answer section. Some believe that inverse queries are themselves a bug and prefer to fix the program generating them rather than tcpdump.
A packet trace that crosses a daylight savings time change will give skewed time stamps (the time change is ignored).
Filter expressions on fields other than those in Token Ring headers will not correctly handle source-routed Token Ring packets.
Filter expressions on fields other than those in 802.11 headers will not correctly handle 802.11 data packets with both To DS and From DS set.
ip6 proto should chase header chain, but at this moment it does not. ip6 protochain is supplied for this behavior.
Arithmetic expression against transport layer headers, like tcp[0], does not work against IPv6 packets. It only looks at IPv4 packets.
Index
This document was created by man2html, using the manual pages.
Time: 05:34:30 GMT, December 24, 2015


Mailthem
Home
Add Templete
Logout
Welcome Home {{username}} !
{{template.title}}
{{template.description}}
{{tempalte.email}}
Send
Edit
Delete
Edit Template Details
Title
Description
Content
Are you suer you want to delete the template?


In and Out (1997) Written by Paul Rudnick Directed by Frank Oz Starring: Kevin Kline, Joan Cusack, Tom Selleck, and Debbie Reynolds... okay...and Matt Dillon.
A Review by Jeremiah "Spassvogel" Rickert
I've always been a Kevin Kline fan, Silverado, Fish Called Wanda, Pirates of Penzance, and even his Hamlet on PBS' Great Performances. The minute I saw the trailer for this film, I resolved to see it. Besides the fact that Kline starred, it looked like a hilarious film. I got sucker punched by the trailer to an extent, however, as I also thought, "wow, if there's this much funny stuff in the trailer, there must be a ton of laughs in the rest of the film." (Oops) I packed up the wife and headed to Les Cinemas Del Diablo (my name for our local Multi-multi-plex.) The film began.... The film concerns an English/Drama teacher at a suburban high school, named Howard Brackett. He loves poetry and great literary works, but his class is more interested in his famous former student, played by Matt Dillon. (I'd put in his name, but my wife won't let me take notes during a movie and I've forgotten it.) They continually interrupt his long poetic expositions with fawning questions about him. Brackett has been engaged to another teacher (played by Joan Cusack) for three years, and has finally gotten up the gumption to marry her. The wedding, however, becomes the big question mark of the film as this famous student of his says during the Live Oscar broadcast that Brackett is a homosexual. Kline spends most of the first two-thirds of the film frantically trying to convince everyone that he isn't. The whole town begins to examine every detail of his life and begins to identifying all those things that confirm his sexual preference. His closest friends don't help matters, bringing nothing but Barbara Streisand laserdiscs to his stag party. There are some genuinely hilarous moments, one involving a tape geared towards helping men assert their masculinity. Kline is hounded by a gay reporter played by Tom Selleck, who waxes poetic on the benefits of coming out, while at the same time doing his best to exploit the situation for his own sleazy tabloid machinations. The movie moves along fine and slowly builds to the climax of the wedding. Kline stands at the Altar and is asked to take his vows... If you want to be surprised, don't read, I am going to reveal the ending. ...instead of saying "I do" in front of his parents and most of the town, and even some cameras, he says "I'm Gay." This is where the movie, in my opinion falls apart. Most of the humor in the film had come from Kline's insistence that he was straight, while at the same time, loving poetry and being a senstivie guy, dressing well, and occaisionally acting prissy. It reminded me of the "Effeminate Heterosexual" sketch from Saturday Night Live. It was funny, it was sustainably funny, and Kline's performance made it doubly so. However, after the wedding, the film drags on. They should have attempted to come to a quick conclusion, but it then gets into the serious side of what he's done. He reconciles with his parents and his friends, some of which had turned on him. There are several scenes which seemed like a waste of time, the scene with his Mother and her friends, which was hilarious, seemed pointless, and the scene with Tom Selleck in the Bar with Joan seemed pointless. Finally, even though I am not Catholic, I found the scene with the Priest to be condescending. The preist cannot believe that a man was engaged for three years and had not consumated the relationship, proclaiming to Brackett in the third person, "He's Gay." It got a chuckle from the audience, but I was distracted by it, and began to tire of the film. By the time the wedding had come and gone, I found myself hoping it would be over soon. (much like this review you are saying)
Overall, if I have to quantify it, I say, Rising Action gets **** and Climax and falling action gets *1/2 out of *****. See it in economy time.
jr --
Jeremiah "Spassvogel" Rickert 6'7" 320 lbs of Dr. Pepper and Pez Candy.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Avengers: Infinity War
Coming out on April 27th
Avengers: Infinity War
Coming out on April 27th
13 Reasons Why
Season 2 Release date
Suits
Season 7 Episode 11
Power
Season 5 Premiere Date
13 Reasons Why
Season 2 Release date
Suits
Season 7 Episode 11
Power
Season 5 Premiere Date