Section: Maintenance Commands (8)
lsof [ ?abChKlnNOPRtUvVX ] [ -A A ] [ -c c ] [ +c c ] [ +|-d d ] [ +|-D D ] [ +|-e s ] [ +|-f [cfgGn] ] [ -F [f] ] [ -g [s] ] [ -i [i] ] [ -k k ] [ +|-L [l] ] [ +|-m m ] [ +|-M ] [ -o [o] ] [ -p s ] [ +|-r [t[m<fmt>]] ] [ -s [p:s] ] [ -S [t] ] [ -T [t] ] [ -u s ] [ +|-w ] [ -x [fl] ] [ -z [z] ] [ -Z [Z] ] [ - ] [names]
Lsof revision 4.86 lists on its standard output file information about files opened by processes for the following UNIX dialects:
Apple Darwin 9 and Mac OS X 10. FreeBSD 4.9 and 6.4 for x86-based systems FreeBSD 8.2, 9.0 and 10.0 for AMD64-based systems Linux 2.1.72 and above for x86-based systems Solaris 9, 10 and 11
(See the DISTRIBUTION section of this manual page for information on how to obtain the latest lsof revision.)
An open file may be a regular file, a directory, a block special file, a character special file, an executing text reference, a library, a stream or a network file (Internet socket, NFS file or UNIX domain socket.) A specific file or all the files in a file system may be selected by path.
Instead of a formatted display, lsof will produce output that can be parsed by other programs. See the -F, option description, and the OUTPUT FOR OTHER PROGRAMS section for more information.
In addition to producing a single output list, lsof will run in repeat mode. In repeat mode it will produce output, delay, then repeat the output operation until stopped with an interrupt or quit signal. See the +|-r [t[m<fmt>]] option description for more information.
In the absence of any options, lsof lists all open files belonging to all active processes.
If any list request option is specified, other list requests must be specifically requested - e.g., if -U is specified for the listing of UNIX socket files, NFS files won't be listed unless -N is also specified; or if a user list is specified with the -u option, UNIX domain socket files, belonging to users not in the list, won't be listed unless the -U option is also specified.
Normally list options that are specifically stated are ORed - i.e., specifying the -i option without an address and the -ufoo option produces a listing of all network files OR files belonging to processes owned by user ``foo''. The exceptions are:
Since they represent exclusions, they are applied without ORing or ANDing and take effect before any other selection criteria are applied.
The -a option may be used to AND the selections. For example, specifying -a, -U, and -ufoo produces a listing of only UNIX socket files that belong to processes owned by user ``foo''.
Caution: the -a option causes all list selection options to be ANDed; it can't be used to cause ANDing of selected pairs of selection options by placing it between them, even though its placement there is acceptable. Wherever -a is placed, it causes the ANDing of all selection options.
Items of the same selection set - command names, file descriptors, network addresses, process identifiers, user identifiers, zone names, security contexts - are joined in a single ORed set and applied before the result participates in ANDing. Thus, for example, specifying -email@example.com, -firstname.lastname@example.org, -a, and -ufff,ggg will select the listing of files that belong to either login ``fff OR ``ggg AND have network connections to either host aaa.bbb OR ccc.ddd.
Options may be grouped together following a single prefix -- e.g., the option set ``a -b -C may be stated as -abC. However, since values are optional following +|-f, -F, -g, -i, +|-L, -o, +|-r, -s, -S, -T, -x and -z. when you have no values for them be careful that the following character isn't ambiguous. For example, -Fn might represent the -F and -n options, or it might represent the n field identifier character following the -F option. When ambiguity is possible, start a new option with a ` character - e.g., ``F -n. If the next option is a file name, follow the possibly ambiguous option with ``-' - e.g., ``F - name''.
Either the `+' or the `-' prefix may be applied to a group of options. Options that don't take on separate meanings for each prefix - e.g., -i - may be grouped under either prefix. Thus, for example, ``+M -i may be stated as ``+Mi and the group means the same as the separate options. Be careful of prefix grouping when one or more options in the group does take on separate meanings under different prefixes - e.g., +|-M; ``-iM is not the same request as ``-i +M. When in doubt, use separate options with appropriate prefixes.
b the regular expression is a basic one.
i ignore the case of letters.
x the regular expression is an extended one
@] See the lsof FAQ (The FAQ section gives its location.) for more information on basic and extended regular expressions.The simple command specification is tested first. If that test fails, the command regular expression is applied. If the simple command test succeeds, the command regular expression test isn't made. This may result in ``no command found for regex:'' messages when lsof's -V option is specified.:
? - report device cache file paths b - build the device cache file i - ignore the device cache file r - read the device cache file u - read and update the device cache file
@] The b, r, and u functions, accompanied by a path name, are sometimes restricted. When these functions are restricted, they will not appear in the description of the -D option that accompanies -h or -? option output. See the DEVICE CACHE FILE section and the sections that follow it for more information on these functions and when they're restricted.The ? function reports the read-only and write paths that lsof can use for the device cache file, the names of any environment variables whose values lsof will examine when forming the device cache file path, and the format for the personal device cache file path. (Escape the `?' character as your shell requires.)When available, the b, r, and u functions may be followed by the device cache file's path. The standard default is .lsof_hostname in the home directory of the real user ID that executes lsof, but this could have been changed when lsof was configured and compiled. (The output of the -h and -? options show the current default prefix - e.g., ``.lsof.) The suffix, hostname, is the first component of the host's name returned by gethostname?(2).When available, the b function directs lsof to build a new device cache file at the default or specified path.The i function directs lsof to ignore the default device cache file and obtain its information about devices via direct calls to the kernel.The r function directs lsof to read the device cache at the default or specified path, but prevents it from creating a new device cache file when none exists or the existing one is improperly structured. The r function, when specified without a path name, prevents lsof from updating an incorrect or outdated device cache file, or creating a new one in its place. The r function is always available when it is specified without a path name argument; it may be restricted by the permissions of the lsof process.When available, the u function directs lsof'' to read the device cache file at the default or specified path, if possible, and to rebuild it, if necessary. This is the default device cache file function when no -D option has been specified.:
$ lsof +f -- /file/system/name $ lsof -f -- /file/nameThe listing of information from kernel file structures, requested with the +f [cfgGn] option form, is normally inhibited, and is not available in whole or part for some dialects - e.g., /proc-based Linux kernels below 2.6.22. When the prefix to f is a plus sign (`), these characters request file structure information:
c file structure use count (not Linux) f file structure address (not Linux) g file flag abbreviations (Linux 2.6.22 and up) G file flags in hexadecimal (Linux 2.6.22 and up) n file structure node address (not Linux)
@] When the prefix is minus (`-') the same characters disable the listing of the indicated values.File structure addresses, use counts, flags, and node addresses may be used to detect more readily identical files inherited by child processes and identical files in use by different processes. Lsof column output can be sorted by output columns holding the values and listed to identify identical file use, or lsof field output can be parsed by an AWK or Perl post-filter script, or by a C program.:
''hostname''|''hostaddr''][:''service''|''port'']where: (:nl:) ''46'' specifies the IP version, IPv4 or IPv6 (:nl:) that applies to the following address. (:nl:) '6' may be be specified only if the UNIX (:nl:) dialect supports IPv6. If neither '4' nor (:nl:) '6' is specified, the following address (:nl:) applies to all IP versions. (:nl:) ''protocol'' is a protocol name - '''TCP''', '''UDP''' (:nl:) (:nl:) ''hostname'' is an Internet host name. Unless a (:nl:) specific IP version is specified, open (:nl:) network files associated with host names (:nl:) of all versions will be selected. (:nl:) ''hostaddr'' is a numeric Internet IPv4 address in (:nl:) dot form; or an IPv6 numeric address in (:nl:) colon form, enclosed in brackets, if the (:nl:) UNIX dialect supports IPv6. When an IP (:nl:) version is selected, only its numeric (:nl:) addresses may be specified. (:nl:) ''service'' is an ''/etc/services'' name - e.g., '''smtp''' - or a list of them. (:nl:) ''port'' is a port number, or a list of them.IPv6 options may be used only if the UNIX dialect supports IPv6. To see if the dialect supports IPv6, run lsof and specify the -h or -? (help) option. If the displayed description of the -i option contains `` and `IPv, IPv6 is supported.IPv4 host names and addresses may not be specified if network file selection is limited to IPv6 with -i 6. IPv6 host names and addresses may not be specified if network file selection is limited to IPv4 with -i 4. When an open IPv4 network file's address is mapped in an IPv6 address, the open file's type will be IPv6, not IPv4, and its display will be selected by '6', not '4'.At least one address component - 4, 6, protocol, hostname, hostaddr, or service - must be supplied. The `@' character, leading the host specification, is always required; as is the `:', leading the port specification. Specify either hostname or hostaddr. Specify either service name list or port number list. If a service name list is specified, the protocol may also need to be specified if the TCP, UDP and UDPLITE port numbers for the service name are different. Use any case - lower or upper - for protocol.Service names and port numbers may be combined in a list whose entries are separated by commas and whose numeric range entries are separated by minus signs. There may be no embedded spaces, and all service names must belong to the specified protocol. Since service names may contain embedded minus signs, the starting entry of a range can't be a service name; it can be a port number, however.Here are some sample addresses:
-i6 - IPv6 only
TCP:25 - TCP and port 25
@22.214.171.124 - Internet IPv4 host address 126.96.36.199
@[3ffe:1ebc::1]:1234 - Internet IPv6 host address 3ffe:1ebc::1, port 1234
UDP:who - UDP who service port
TCP@lsof.itap:513 - TCP, port 513 and host name lsof.itap
tcp@foo:1-10,smtp,99 - TCP, ports 1 through 10, service name smtp, port 99, host name foo
tcp@bar:1-smtp - TCP, ports 1 through smtp, host bar
:time - either TCP, UDP or UDPLITE time service port
/ 0x801Lsof can use the mount supplement file to get device numbers for file systems when it can't get them via stat?(2) or lstat?(2).The option form +m m identifies m as a mount supplement file.Note: the +m and +m m options are not available for all supported dialects. Check the output of lsof's -h or -? options to see if the +m and +m m options are available.:
-o -o 10 or -oo10The default number of digits allowed after ``0t is normally 8, but may have been changed by the lsof builder. Consult the description of the -o o'' option in the output of the -h or -? option to determine the default that is in effect.:
-iTCP -sTCP:LISTENOr, for example, to list network files with all UDP states except Idle, use:
-iUDP -sUDP:IdleState names vary with UNIX dialects, so it's not possible to provide a complete list. Some common TCP state names are: CLOSED, IDLE, BOUND, LISTEN, ESTABLISHED, SYN_SENT, SYN_RCDV, ESTABLISHED, CLOSE_WAIT, FIN_WAIT1, CLOSING, LAST_ACK, FIN_WAIT_2, and TIME_WAIT. Two common UDP state names are Unbound and Idle.See the lsof FAQ (The FAQ section gives its location.) for more information on how to use protocol state exclusion and inclusion, including examples.The -o (without a following decimal digit count) and -s option (without a following protocol and state name list) are mutually exclusive; they can't both be specified. When neither is specified, lsof displays whatever value - size or offset - is appropriate and available for the type of file.Since some types of files don't have true sizes - sockets, FIFOs, pipes, etc. - lsof displays for their sizes the content amounts in their associated kernel buffers, if possible.:
<TCP or TPI state name> QR=<read queue length> QS=<send queue length> SO=<socket options and values> SS=<socket states> TF=<TCP flags and values> WR=<window read length> WW=<window write length>Not all values are reported for all UNIX dialects. Items values (when available) are reported after the item name and '='.When the field output mode is in effect (See OUTPUT FOR OTHER PROGRAMS.) each item appears as a field with a `T' leading character.-T with no following key characters disables TCP/TPI information reporting.-T with following characters selects the reporting of specific TCP/TPI information:
f selects reporting of socket options, states and values, and TCP flags and values. q selects queue length reporting. s selects connection state reporting. w selects window size reporting.@] Not all selections are enabled for some UNIX dialects. State may be selected for all dialects and is reported by default. The -h or -? help output for the -T option will show what selections may be used with the UNIX dialect.When -T is used to select information - i.e., it is followed by one or more selection characters - the displaying of state is disabled by default, and it must be explicitly selected again in the characters following -T. (In effect, then, the default is equivalent to -Ts.) For example, if queue lengths and state are desired, use -Tqs.Socket options, socket states, some socket values, TCP flags and one TCP value may be reported (when available in the UNIX dialect) in the form of the names that commonly appear after SO_, so_, SS_, TCP_ and TF_ in the dialect's header files - most often <sys/socket.h>, <sys/socketvar.h> and <netinet/tcp_var.h>. Consult those header files for the meaning of the flags, options, states and values.``SO= precedes socket options and values; ``SS=, socket states; and ``TF=, TCP flags and values.If a flag or option has a value, the value will follow an '=' and the name -- e.g., ``SO=LINGER=5, ``SO=QLIM=5, ``TF=MSS=512. The following seven values may be reported:
Name Reported Description (Common Symbol) KEEPALIVE keep alive time (SO_KEEPALIVE) LINGER linger time (SO_LINGER) MSS maximum segment size (TCP_MAXSEG) PQLEN partial listen queue connections QLEN established listen queue connections QLIM established listen queue limit RCVBUF receive buffer length (SO_RCVBUF) SNDBUF send buffer length (SO_SNDBUF)Details on what socket options and values, socket states, and TCP flags and values may be displayed for particular UNIX dialects may be found in the answer to the ``Why doesn't lsof report socket options, socket states, and TCP flags and values for my dialect? and ``Why doesn't lsof report the partial listen queue connection count for my dialect? questions in the lsof FAQ (The FAQ section gives its location.):
Lsof supports the recognition of AFS files for these dialects (and AFS versions):
AIX 4.1.4 (AFS 3.4a) HP-UX 9.0.5 (AFS 3.4a) Linux 1.2.13 (AFS 3.3) Solaris 2. (AFS 3.4a)
It may recognize AFS files on other versions of these dialects, but has not been tested there. Depending on how AFS is implemented, lsof may recognize AFS files in other dialects, or may have difficulties recognizing AFS files in the supported dialects.
Lsof may have trouble identifying all aspects of AFS files in supported dialects when AFS kernel support is implemented via dynamic modules whose addresses do not appear in the kernel's variable name list. In that case, lsof may have to guess at the identity of AFS files, and might not be able to obtain volume information from the kernel that is needed for calculating AFS volume node numbers. When lsof can't compute volume node numbers, it reports blank in the NODE column.
The -A A option is available in some dialect implementations of lsof for specifying the name list file where dynamic module kernel addresses may be found. When this option is available, it will be listed in the lsof help output, presented in response to the -h or -?
See the lsof FAQ (The FAQ section gives its location.) for more information about dynamic modules, their symbols, and how they affect lsof options.
Lsof has three features that may cause security concerns. First, its default compilation mode allows anyone to list all open files with it. Second, by default it creates a user-readable and user-writable device cache file in the home directory of the real user ID that executes lsof. (The list-all-open-files and device cache features may be disabled when lsof is compiled.) Third, its -k and -m options name alternate kernel name list or memory files.
Restricting the listing of all open files is controlled by the compile-time HASSECURITY and HASNOSOCKSECURITY options. When HASSECURITY is defined, lsof will allow only the root user to list all open files. The non-root user may list only open files of processes with the same user IDentification number as the real user ID number of the lsof process (the one that its user logged on with).
However, if HASSECURITY and HASNOSOCKSECURITY are both defined, anyone may list open socket files, provided they are selected with the -i option.
When HASSECURITY is not defined, anyone may list all open files.
Help output, presented in response to the -h or -? option, gives the status of the HASSECURITY and HASNOSOCKSECURITY definitions.
See the Security section of the 00README file of the lsof distribution for information on building lsof with the HASSECURITY and HASNOSOCKSECURITY options enabled.
Creation and use of a user-readable and user-writable device cache file is controlled by the compile-time HASDCACHE option. See the DEVICE CACHE FILE section and the sections that follow it for details on how its path is formed. For security considerations it is important to note that in the default lsof distribution, if the real user ID under which lsof is executed is root, the device cache file will be written in root's home directory - e.g., / or /root. When HASDCACHE is not defined, lsof does not write or attempt to read a device cache file.
When HASDCACHE is defined, the lsof help output, presented in response to the -h, -D?, or -? options, will provide device cache file handling information. When HASDCACHE is not defined, the -h or -? output will have no -D option description.
Before you decide to disable the device cache file feature - enabling it improves the performance of lsof by reducing the startup overhead of examining all the nodes in /dev (or /devices) - read the discussion of it in the 00DCACHE file of the lsof distribution and the lsof FAQ (The FAQ section gives its location.)
WHEN IN DOUBT, YOU CAN TEMPORARILY DISABLE THE USE OF THE DEVICE CACHE FILE WITH THE -Di OPTION.
When lsof user declares alternate kernel name list or memory files with the -k and -m options, lsof checks the user's authority to read them with access?(2). This is intended to prevent whatever special power lsof's modes might confer on it from letting it read files not normally accessible via the authority of the real user ID.
This section describes the information lsof lists for each open file. See the OUTPUT FOR OTHER PROGRAMS section for additional information on output that can be processed by another program.
Lsof only outputs printable (declared so by isprint?(3)) 8 bit characters. Non-printable characters are printed in one of three forms: the C ``\[bfrnt] form; the control character `^' form (e.g., ``^@); or hexadecimal leading ``\x form (e.g., ``\xab). Space is non-printable in the COMMAND column (``\x20'') and printable elsewhere.
For some dialects - if HASSETLOCALE is defined in the dialect's machine.h header file - lsof will print the extended 8 bit characters of a language locale. The lsof process must be supplied a language locale environment variable (e.g., LANG) whose value represents a known language locale in which the extended characters are considered printable by isprint?(3). Otherwise lsof considers the extended characters non-printable and prints them according to its rules for non-printable characters, stated above. Consult your dialect's setlocale?(3) man page for the names of other environment variables that may be used in place of LANG - e.g., LC_ALL, LC_CTYPE, etc.
Lsof's language locale support for a dialect also covers wide characters - e.g., UTF-8 - when HASSETLOCALE and HASWIDECHAR are defined in the dialect's machine.h header file, and when a suitable language locale has been defined in the appropriate environment variable for the lsof process. Wide characters are printable under those conditions if iswprint?(3) reports them to be. If HASSETLOCALE, HASWIDECHAR and a suitable language locale aren't defined, or if iswprint?(3) reports wide characters that aren't printable, lsof considers the wide characters non-printable and prints each of their 8 bits according to its rules for non-printable characters, stated above.
Consult the answers to the "Language locale support" questions in the lsof FAQ (The FAQ section gives its location.) for more information.
Lsof dynamically sizes the output columns each time it runs, guaranteeing that each column is a minimum size. It also guarantees that each column is separated from its predecessor by at least one space.
cwd current working directory;
Lnn library references (AIX);
err FD information error (see NAME column);
jld jail directory (FreeBSD);
ltx shared library text (code and data);
Mxx hex memory-mapped type number xx.
m86 DOS Merge mapped file;
mem memory-mapped file;
mmap memory-mapped device;
pd parent directory;
rtd root directory;
tr kernel trace file (OpenBSD);
txt program text (code and data);
v86 VP/ix mapped file;@] FD is followed by one of these characters, describing the mode under which the file is open:
r for read access;
w for write access;
u for read and write access;
space if mode unknown and no lock
`-' if mode unknown and lock
character follows. The mode character is followed by one of these lock characters, describing the type of lock applied to the file:
N for a Solaris NFS lock of unknown type;
r for read lock on part of the file;
R for a read lock on the entire file;
w for a write lock on part of the file;
W for a write lock on the entire file;
u for a read and write lock of any length;
U for a lock of unknown type;
x for an SCO OpenServer Xenix lock on part
of the file;
X for an SCO OpenServer Xenix lock on the
space if there is no lock.
See the LOCKS section for more information on the lock information character.The FD column contents constitutes a single field for parsing in post-processing scripts.:
AIO asynchronous I/O (e.g., FAIO) AP append ASYN asynchronous I/O (e.g., FASYNC) BAS block, test, and set in use BKIU block if in use BL use block offsets BSK block seek CA copy avoid CIO concurrent I/O CLON clone CLRD CL read CR create DF defer DFI defer IND DFLU data flush DIR direct DLY delay DOCL do clone DSYN data-only integrity DTY must be a directory EVO event only EX open for exec EXCL exclusive open FSYN synchronous writes GCDF defer during unp_gc() (AIX) GCMK mark during unp_gc() (AIX) GTTY accessed via /dev/tty HUP HUP in progress KERN kernel KIOC kernel-issued ioctl LCK has lock LG large file MBLK stream message block MK mark MNT mount MSYN multiplex synchronization NATM don't update atime NB non-blocking I/O NBDR no BDRM check NBIO SYSV non-blocking I/O NBF n-buffering in effect NC no cache ND no delay NDSY no data synchronization NET network NFLK don't follow links NMFS NM file system NOTO disable background stop NSH no share NTTY no controlling TTY OLRM OLR mirror PAIO POSIX asynchronous I/O PP POSIX pipe R read RC file and record locking cache REV revoked RSH shared read RSYN read synchronization RW read and write access SL shared lock SNAP cooked snapshot SOCK socket SQSH Sequent shared set on open SQSV Sequent SVM set on open SQR Sequent set repair on open SQS1 Sequent full shared open SQS2 Sequent partial shared open STPI stop I/O SWR synchronous read SYN file integrity while writing TCPM avoid TCP collision TR truncate W write WKUP parallel I/O synchronization WTG parallel I/O synchronization VH vhangup pending VTXT virtual text XL exclusive lockthis list of names was derived from F* #define's in dialect header files <fcntl.h>, <linux</fs.h>, <sys/fcntl.c>, <sys/fcntlcom.h>, and <sys/file.h>; see the lsof.h header file for a list showing the correspondence between the above short-hand names and the header file definitions;the second list (after the semicolon) may contain short-hand names for kernel per-process open file flags from this table:
ALLC allocated BR the file has been read BHUP activity stopped by SIGHUP BW the file has been written CLSG closing CX close-on-exec (see fcntl(F_SETFD)) LCK lock was applied MP memory-mapped OPIP open pending - in progress RSVW reserved wait SHMT UF_FSHMAT set (AIX) USE in use (multi-threaded):
For dialects that support a ``namefs file system, allowing one file to be attached to another with (3C), lsof will add ``(FA:<address1><direction><address2>) to the NAME column. <address1> and <address2> are hexadecimal vnode addresses. <direction> will be ``<- if <address2> has been fattach'ed to this vnode whose address is <address1>; and ``-> if <address1>, the vnode address of this vnode, has been fattach'ed to <address2>. <address1> may be omitted if it already appears in the DEVICE column.
Lsof may add two parenthetical notes to the NAME column for open Solaris 10 files: ``(?) if lsof considers the path name of questionable accuracy; and ``(deleted) if the -X option has been specified and lsof detects the open file's path name has been deleted. Consult the lsof FAQ (The FAQ section gives its location.) for more information on these NAME column additions.
Lsof can't adequately report the wide variety of UNIX dialect file locks in a single character. What it reports in a single character is a compromise between the information it finds in the kernel and the limitations of the reporting format.
Moreover, when a process holds several byte level locks on a file, lsof only reports the status of the first lock it encounters. If it is a byte level lock, then the lock character will be reported in lower case - i.e., `r', `w', or `x' - rather than the upper case equivalent reported for a full file lock.
Generally lsof can only report on locks held by local processes on local files. When a local process sets a lock on a remotely mounted (e.g., NFS) file, the remote server host usually records the lock state. One exception is Solaris - at some patch levels of 2.3, and in all versions above 2.4, the Solaris kernel records information on remote locks in local structures.
When the -F option is specified, lsof produces output that is suitable for processing by another program - e.g, an awk or Perl script, or a C program.
Each unit of information is output in a field that is identified with a leading character and terminated by a NL (012) (or a NUL (000) if the 0 (zero) field identifier character is specified.) The data of the field follows immediately after the field identification character and extends to the field terminator.
It is possible to think of field output as process and file sets. A process set begins with a field whose identifier is `p' (for process IDentifier (PID)). It extends to the beginning of the next PID field or the beginning of the first file set of the process, whichever comes first. Included in the process set are fields that identify the command, the process group IDentification (PGID) number, the task number and the user ID (UID) number or login name.
A file set begins with a field whose identifier is `f' (for file descriptor). It is followed by lines that describe the file's access mode, lock state, type, device, size, offset, inode, protocol, name and stream module names. It extends to the beginning of the next file or process set, whichever comes first.
When the NUL (000) field terminator has been selected with the 0 (zero) field identifier character, lsof ends each process and file set with a NL (012) character.
Lsof always produces one field, the PID (`p') field. All other fields may be declared optionally in the field identifier character list that follows the -F option. When a field selection character identifies an item lsof does not normally list - e.g., PPID, selected with -R - specification of the field character - e.g., ``-FR'' - also selects the listing of the item.
It is entirely possible to select a set of fields that cannot easily be parsed - e.g., if the field descriptor field is not selected, it may be difficult to identify file sets. To help you avoid this difficulty, lsof supports the -F option; it selects the output of all fields with NL terminators (the -F0 option pair selects the output of all fields with NUL terminators). For compatibility reasons neither -F nor -F0 select the raw device field.
These are the fields that lsof will produce. The single character listed first is the field identifier.
a file access mode c process command name (all characters from proc or user structure) C file structure share count d file's device character code D file's major/minor device number (0x<hexadecimal>) f file descriptor F file structure address (0x<hexadecimal>) G file flaGs (0x<hexadecimal>; names if +fg follows) g process group ID i file's inode number K tasK ID k link count l file's lock status L process login name m marker between repeated output n file name, comment, Internet address N node identifier (ox<hexadecimal> o file's offset (decimal) p process ID (always selected) P protocol name r raw device number (0x<hexadecimal>) R parent process ID s file's size (decimal) S file's stream identification t file's type T TCP/TPI information, identified by prefixes (the `=' is part of the prefix): QR=<read queue size> QS=<send queue size> SO=<socket options and values> (not all dialects) SS=<socket states> (not all dialects) ST=<connection state> TF=<TCP flags and values> (not all dialects) WR=<window read size> (not all dialects) WW=<window write size> (not all dialects) (TCP/TPI information isn't reported for all supported UNIX dialects. The -h or -? help output for the -T option will show what TCP/TPI reporting can be requested.) u process user ID z Solaris 10 and higher zone name Z SELinux security context (inhibited when SELinux is disabled) 0 use NUL field terminator character in place of NL 1-9 dialect-specific field identifiers (The output of -F? identifies the information to be found in dialect-specific fields.)
You can get on-line help information on these characters and their descriptions by specifying the -F? option pair. (Escape the `?' character as your shell requires.) Additional information on field content can be found in the OUTPUT section.
As an example, ``-F pcfn will select the process ID (`p'), command name (`c'), file descriptor (`f') and file name (`n') fields with an NL field terminator character; ``-F pcfn0 selects the same output with a NUL (000) field terminator character.
Lsof doesn't produce all fields for every process or file set, only those that are available. Some fields are mutually exclusive: file device characters and file major/minor device numbers; file inode number and protocol name; file name and stream identification; file size and offset. One or the other member of these mutually exclusive sets will appear in field output, but not both.
Normally lsof ends each field with a NL (012) character. The 0 (zero) field identifier character may be specified to change the field terminator character to a NUL (000). A NUL terminator may be easier to process with xargs (1), for example, or with programs whose quoting mechanisms may not easily cope with the range of characters in the field output. When the NUL field terminator is in use, lsof ends each process and file set with a NL (012).
Three aids to producing programs that can process lsof field output are included in the lsof distribution. The first is a C header file, lsof_fields.h, that contains symbols for the field identification characters, indexes for storing them in a table, and explanation strings that may be compiled into programs. Lsof uses this header file.
The second aid is a set of sample scripts that process field output, written in awk, Perl 4, and Perl 5. They're located in the scripts subdirectory of the lsof distribution.
The third aid is the C library used for the lsof test suite. The test suite is written in C and uses field output to validate the correct operation of lsof. The library can be found in the tests/LTlib.c file of the lsof distribution. The library uses the first aid, the lsof_fields.h header file.
Lsof can be blocked by some kernel functions that it uses - lstat?(2), readlink?(2), and stat?(2). These functions are stalled in the kernel, for example, when the hosts where mounted NFS file systems reside become inaccessible.
Lsof attempts to break these blocks with timers and child processes, but the techniques are not wholly reliable. When lsof does manage to break a block, it will report the break with an error message. The messages may be suppressed with the -t and -w options.
The default timeout value may be displayed with the -h or -? option, and it may be changed with the -S [t] option. The minimum for t is two seconds, but you should avoid small values, since slow system responsiveness can cause short timeouts to expire unexpectedly and perhaps stop lsof before it can produce any output.
When lsof has to break a block during its access of mounted file system information, it normally continues, although with less information available to display about open files.
Lsof can also be directed to avoid the protection of timers and child processes when using the kernel functions that might block by specifying the -O option. While this will allow lsof to start up with less overhead, it exposes lsof completely to the kernel situations that might block it. Use this option cautiously.
You can use the -b option to tell lsof to avoid using kernel functions that would block. Some cautions apply.
First, using this option usually requires that your system supply alternate device numbers in place of the device numbers that lsof would normally obtain with the lstat?(2) and stat?(2) kernel functions. See the ALTERNATE DEVICE NUMBERS section for more information on alternate device numbers.
Second, you can't specify names for lsof to locate unless they're file system names. This is because lsof needs to know the device and inode numbers of files listed with names in the lsof options, and the -b option prevents lsof from obtaining them. Moreover, since lsof only has device numbers for the file systems that have alternates, its ability to locate files on file systems depends completely on the availability and accuracy of the alternates. If no alternates are available, or if they're incorrect, lsof won't be able to locate files on the named file systems.
Third, if the names of your file system directories that lsof obtains from your system's mount table are symbolic links, lsof won't be able to resolve the links. This is because the -b option causes lsof to avoid the kernel readlink?(2) function it uses to resolve symbolic links.
Finally, using the -b option causes lsof to issue warning messages when it needs to use the kernel functions that the -b option directs it to avoid. You can suppress these messages by specifying the -w option, but if you do, you won't see the alternate device numbers reported in the warning messages.
On some dialects, when lsof has to break a block because it can't get information about a mounted file system via the lstat?(2) and stat?(2) kernel functions, or because you specified the -b option, lsof can obtain some of the information it needs - the device number and possibly the file system type - from the system mount table. When that is possible, lsof will report the device number it obtained. (You can suppress the report by specifying the -w option.)
You can assist this process if your mount table is supported with an /etc/mtab or /etc/mnttab file that contains an options field by adding a ``dev=xxxx'' field for mount points that do not have one in their options strings. Note: you must be able to edit the file - i.e., some mount tables like recent Solaris /etc/mnttab or Linux /proc/mounts are read-only and can't be modified.
You may also be able to supply device numbers using the +m and +m m options, provided they are supported by your dialect. Check the output of lsof's -h or -? options to see if the +m and +m m options are available.
The ``xxxx portion of the field is the hexadecimal value of the file system's device number. (Consult the st_dev field of the output of the lstat?(2) and stat?(2) functions for the appropriate values for your file systems.) Here's an example from a Sun Solaris 2.6 /etc/mnttab'' for a file system remotely mounted via NFS:
There's an advantage to having ``dev=xxxx entries in your mount table file, especially for file systems that are mounted from remote NFS servers. When a remote server crashes and you want to identify its users by running lsof on one of its clients, lsof probably won't be able to get output from the lstat?(2) and stat?''(2) functions for the file system. If it can obtain the file system's device number from the mount table, it will be able to display the files open on the crashed NFS server.
Some dialects that do not use an ASCII /etc/mtab or /etc/mnttab file for the mount table may still provide an alternative device number in their internal mount tables. This includes AIX, Apple Darwin, FreeBSD, NetBSD, OpenBSD, and Tru64 UNIX. Lsof knows how to obtain the alternative device number for these dialects and uses it when its attempt to lstat?(2) or stat?(2) the file system is blocked.
If you're not sure your dialect supplies alternate device numbers for file systems from its mount table, use this lsof incantation to see if it reports any alternate device numbers:
Lsof is able to examine the kernel's name cache or use other kernel facilities (e.g., the ADVFS 4.x tag_to_path() function under Tru64 UNIX) on some dialects for most file system types, excluding AFS, and extract recently used path name components from it. (AFS file system path lookups don't use the kernel's name cache; some Solaris VxFS file system operations apparently don't use it, either.)
Lsof reports the complete paths it finds in the NAME column. If lsof can't report all components in a path, it reports in the NAME column the file system name, followed by a space, two `-' characters, another space, and the name components it has located, separated by the `/' character.
When lsof is run in repeat mode - i.e., with the -r option specified - the extent to which it can report path name components for the same file may vary from cycle to cycle. That's because other running processes can cause the kernel to remove entries from its name cache and replace them with others.
Lsof's use of the kernel name cache to identify the paths of files can lead it to report incorrect components under some circumstances. This can happen when the kernel name cache uses device and node number as a key (e.g., SCO OpenServer) and a key on a rapidly changing file system is reused. If the UNIX dialect's kernel doesn't purge the name cache entry for a file when it is unlinked, lsof may find a reference to the wrong entry in the cache. The lsof FAQ (The FAQ section gives its location.) has more information on this situation.
Lsof can report path name components for these dialects:
FreeBSD HP-UX Linux NetBSD NEXTSTEP OpenBSD OPENSTEP SCO OpenServer SCO|Caldera UnixWare Solaris Tru64 UNIX
Lsof can't report path name components for these dialects:
Examining all members of the /dev (or /devices) node tree with stat?(2) functions can be time consuming. What's more, the information that lsof needs - device number, inode number, and path - rarely changes.
Consequently, lsof normally maintains an ASCII text file of cached /dev (or /devices) information (exception: the /proc-based Linux lsof where it's not needed.) The local system administrator who builds lsof can control the way the device cache file path is formed, selecting from these options:
Path from the -D option; Path from an environment variable; System-wide path; Personal path (the default); Personal path, modified by an environment variable.
Consult the output of the -h, -D? , or -? help options for the current state of device cache support. The help output lists the default read-mode device cache file path that is in effect for the current invocation of lsof. The -D? option output lists the read-only and write device cache file paths, the names of any applicable environment variables, and the personal device cache path format.
Lsof can detect that the current device cache file has been accidentally or maliciously modified by integrity checks, including the computation and verification of a sixteen bit Cyclic Redundancy Check (CRC) sum on the file's contents. When lsof senses something wrong with the file, it issues a warning and attempts to remove the current cache file and create a new copy, but only to a path that the process can legitimately write.
The path from which a lsof process may attempt to read a device cache file may not be the same as the path to which it can legitimately write. Thus when lsof senses that it needs to update the device cache file, it may choose a different path for writing it from the path from which it read an incorrect or outdated version.
If available, the -Dr option will inhibit the writing of a new device cache file. (It's always available when specified without a path name argument.)
When a new device is added to the system, the device cache file may need to be recreated. Since lsof compares the mtime of the device cache file with the mtime and ctime of the /dev (or /devices) directory, it usually detects that a new device has been added; in that case lsof issues a warning message and attempts to rebuild the device cache file.
Whenever lsof writes a device cache file, it sets its ownership to the real UID of the executing process, and its permission modes to 0600, this restricting its reading and writing to the file's owner.
Two permissions of the lsof executable affect its ability to access device cache files. The permissions are set by the local system administrator when lsof is installed.
The first and rarer permission is setuid-root. It comes into effect when lsof is executed; its effective UID is then root, while its real (i.e., that of the logged-on user) UID is not. The lsof distribution recommends that versions for these dialects run setuid-root.
HP-UX 11.11 and 11.23 Linux
The second and more common permission is setgid. It comes into effect when the effective group IDentification number (GID) of the lsof process is set to one that can access kernel memory devices - e.g., ``kmem, ``sys, or ``system''.
An lsof process that has setgid permission usually surrenders the permission after it has accessed the kernel memory devices. When it does that, lsof can allow more liberal device cache path formations. The lsof distribution recommends that versions for these dialects run setgid and be allowed to surrender setgid permission.
AIX 5. and 5.3-ML1 Apple Darwin 7.x Power Macintosh systems FreeBSD 4.x, 4.1x, 5.x and .x for x86-based systems FreeBSD 5.x and .x for Alpha, AMD64 and Sparc64-based systems HP-UX 11.00 NetBSD 1., 2.x and 3.x for Alpha, x86, and SPARC-based systems NEXTSTEP 3. for NEXTSTEP architectures OpenBSD 2. and 3.[0-9] for x86-based systems OPENSTEP 4.x SCO OpenServer Release 5.0.6 for x86-based systems SCO|Caldera UnixWare 7.1.4 for x86-based systems Solaris 2.6, 8, 9 and 10 Tru64 UNIX 5.1
(Note: lsof for AIX 5L and above needs setuid-root permission if its -X option is used.)
Lsof for these dialects does not support a device cache, so the permissions given to the executable don't apply to the device cache file.
The -D option provides limited means for specifying the device cache file path. Its ? function will report the read-only and write device cache file paths that lsof will use.
When the -D b, r, and u functions are available, you can use them to request that the cache file be built in a specific location (b[path]); read but not rebuilt (r[path]); or read and rebuilt (u[path]). The b, r, and u functions are restricted under some conditions. They are restricted when the lsof process is setuid-root. The path specified with the r function is always read-only, even when it is available.
The b, r, and u functions are also restricted when the lsof process runs setgid and lsof doesn't surrender the setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for a list of implementations that normally don't surrender their setgid permission.)
A further -D function, i (for ignore), is always available.
When available, the r function tells lsof to read the device cache file, but not update it. When a path argument accompanies -Dr, it names the device cache file path. The r function is always available when it is specified without a path name argument. If lsof is not running setuid-root and surrenders its setgid permission, a path name argument may accompany the r function.
When available, the u function tells lsof to attempt to read and use the device cache file. If it can't read the file, or if it finds the contents of the file incorrect or outdated, it will read information from the kernel, and attempt to write an updated version of the device cache file, but only to a path it considers legitimate for the lsof process effective and real UIDs.
Lsof's second choice for the device cache file is the contents of the LSOFDEVCACHE environment variable. It avoids this choice if the lsof process is setuid-root, or the real UID of the process is root.
A further restriction applies to a device cache file path taken from the LSOFDEVCACHE environment variable: lsof will not write a device cache file to the path if the lsof process doesn't surrender its setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for information on implementations that don't surrender their setgid permission.)
The local system administrator may choose to have a system-wide device cache file when building lsof. That file will generally be constructed by a special system administration procedure when the system is booted or when the contents of /dev or /devices) changes. If defined, it is lsof's third device cache file path choice.
You can tell that a system-wide device cache file is in effect for your local installation by examining the lsof help option output - i.e., the output from the -h or -? option.
Lsof will never write to the system-wide device cache file path by default. It must be explicitly named with a -D function in a root-owned procedure. Once the file has been written, the procedure must change its permission modes to 0644 (owner-read and owner-write, group-read, and other-read).
The default device cache file path of the lsof distribution is one recorded in the home directory of the real UID that executes lsof. Added to the home directory is a second path component of the form .lsof_hostname.
This is lsof's fourth device cache file path choice, and is usually the default. If a system-wide device cache file path was defined when lsof was built, this fourth choice will be applied when lsof can't find the system-wide device cache file. This is the only time lsof uses two paths when reading the device cache file.
The hostname part of the second component is the base name of the executing host, as returned by gethostname?(2). The base name is defined to be the characters preceding the first `.' in the gethostname?(2) output, or all the gethostname?(2) output if it contains no `.'.
The device cache file belongs to the user ID and is readable and writable by the user ID alone - i.e., its modes are 0600. Each distinct real user ID on a given host that executes lsof has a distinct device cache file. The hostname part of the path distinguishes device cache files in an NFS-mounted home directory into which device cache files are written from several different hosts.
The personal device cache file path formed by this method represents a device cache file that lsof will attempt to read, and will attempt to write should it not exist or should its contents be incorrect or outdated.
The -Dr option without a path name argument will inhibit the writing of a new device cache file.
The -D? option will list the format specification for constructing the personal device cache file. The conversions used in the format specification are described in the 00DCACHE file of the lsof distribution.
If this option is defined by the local system administrator when lsof is built, the LSOFPERSDCPATH environment variable contents may be used to add a component of the personal device cache file path.
The LSOFPERSDCPATH variable contents are inserted in the path at the place marked by the local system administrator with the ``%p conversion in the HASPERSDC format specification of the dialect's machine.h header file. (It's placed right after the home directory in the default lsof'' distribution.)
Thus, for example, if LSOFPERSDCPATH contains ``LSOF, the home directory is ``/Homes/abe, the host name is ``lsof.itap.purdue.edu, and the HASPERSDC format is the default (``%h/L), the modified personal device cache file path is:
The LSOFPERSDCPATH environment variable is ignored when the lsof process is setuid-root or when the real UID of the process is root.
Lsof will not write to a modified personal device cache file path if the lsof process doesn't surrender setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for a list of implementations that normally don't surrender their setgid permission.)
If, for example, you want to create a sub-directory of personal device cache file paths by using the LSOFPERSDCPATH environment variable to name it, and lsof doesn't surrender its setgid permission, you will have to allow lsof to create device cache files at the standard personal path and move them to your subdirectory with shell commands.
The local system administrator may: disable this option when lsof is built; change the name of the environment variable from LSOFPERSDCPATH to something else; change the HASPERSDC format to include the personal path component in another place; or exclude the personal path component entirely. Consult the output of the -D? option for the environment variable's name and the HASPERSDC format specification.
Errors are identified with messages on the standard error file.
Lsof returns a one (1) if any error was detected, including the failure to locate command names, file names, Internet addresses or files, login names, NFS files, PIDs, PGIDs, or UIDs it was asked to list. If the -V option is specified, lsof will indicate the search items it failed to list.
It returns a zero (0) if no errors were detected and if it was able to list some information about all the specified search arguments.
When lsof cannot open access to /dev (or /devices) or one of its subdirectories, or get information on a file in them with stat?(2), it issues a warning message and continues. That lsof will issue warning messages about inaccessible files in /dev (or /devices) is indicated in its help output - requested with the -h or >B -? options - with the message:
Inaccessible /dev warnings are enabled.
The warning message may be suppressed with the -w option. It may also have been suppressed by the system administrator when lsof was compiled by the setting of the WARNDEVACCESS definition. In this case, the output from the help options will include the message:
Inaccessible /dev warnings are disabled.
For a more extensive set of examples, documented more fully, see the 00QUICKSTART file of the lsof distribution.
To list all open files, use:
To list all open Internet, x.25 (HP-UX), and UNIX domain files, use:
To list all open IPv4 network files in use by the process whose PID is 1234, use:
Presuming the UNIX dialect supports IPv6, to list only open IPv6 network files, use:
To list all files using any protocol on ports 513, 514, or 515 of host wonderland.cc.purdue.edu, use:
To list all files using any protocol on any port of mace.cc.purdue.edu (cc.purdue.edu is the default domain), use:
To list all open files for login name ``abe'', or user ID 1234, or process 456, or process 123, or process 789, use:
To list all open files on device /dev/hd4, use:
To find the process that has /u/abe/foo open, use:
To send a SIGHUP to the processes that have /u/abe/bar open, use:
To find any open file, including an open UNIX domain socket file, with the name /dev/log, use:
To find processes with open files on the NFS file system named /nfs/mount/point whose server is inaccessible, and presuming your mount table supplies the device number for /nfs/mount/point, use:
To do the preceding search with warning messages suppressed, use:
To ignore the device cache file, use:
To obtain PID and command name field output for each process, file descriptor, file device number, and file inode number for each file of each process, use:
To list the files at descriptors 1 and 3 of every process running the lsof command for login ID ``abe'' every 10 seconds, use:
To list the current working directory of processes running a command that is exactly four characters long and has an 'o' or 'O' in character three, use this regular expression form of the -c c option:
To find an IP version 4 socket file by its associated numeric dot-form address, use:
To find an IP version 6 socket file (when the UNIX dialect supports IPv6) by its associated numeric colon-form address, use:
To find an IP version 6 socket file (when the UNIX dialect supports IPv6) by an associated numeric colon-form address that has a run of zeroes in it - e.g., the loop-back address - use:
To obtain a repeat mode marker line that contains the current time, use:
To add spaces to the previous marker line, use:
Since lsof reads kernel memory in its search for open files, rapid changes in kernel memory may produce unpredictable results.
When a file has multiple record locks, the lock status character (following the file descriptor) is derived from a test of the first lock structure, not from any combination of the individual record locks that might be described by multiple lock structures.
Lsof can't search for files with restrictive access permissions by name unless it is installed with root set-UID permission. Otherwise it is limited to searching for files to which its user or its set-GID group (if any) has access permission.
The display of the destination address of a raw socket (e.g., for ping) depends on the UNIX operating system. Some dialects store the destination address in the raw socket's protocol control block, some do not.
Lsof can't always represent Solaris device numbers in the same way that ls?(1) does. For example, the major and minor device numbers that the lstat?(2) and stat?(2) functions report for the directory on which CD-ROM files are mounted (typically /cdrom) are not the same as the ones that it reports for the device on which CD-ROM files are mounted (typically /dev/sr0). (Lsof reports the directory numbers.)
The support for /proc file systems is available only for BSD and Tru64 UNIX dialects, Linux, and dialects derived from SYSV R4 - e.g., FreeBSD, NetBSD, OpenBSD, Solaris, UnixWare.
Some /proc file items - device number, inode number, and file size - are unavailable in some dialects. Searching for files in a /proc file system may require that the full path name be specified.
No text (txt) file descriptors are displayed for Linux processes. All entries for files other than the current working directory, the root directory, and numerical file descriptors are labeled mem descriptors.
Lsof can't report fully or correctly on HP-UX 9.01, 10.20, and 11.00 locks because of insufficient access to kernel data or errors in the kernel data. See the lsof FAQ (The FAQ section gives its location.) for details.
The AIX SMT file type is a fabrication. It's made up for file structures whose type (15) isn't defined in the AIX /usr/include/sys/file.h header file. One way to create such file structures is to run X clients with the DISPLAY variable set to ``:0.0''.
Lsof may access these environment variables.
Frequently-asked questions and their answers (an FAQ) are available in the 00FAQ file of the lsof distribution.
That file is also available via anonymous ftp from lsof.itap.purdue.edu at pub/tools/unix/lsofFAQ. The URL is:
Lsof was written by Victor A. Abell <email@example.com> of Purdue University. Many others have contributed to lsof. They're listed in the 00CREDITS file of the lsof distribution.
The latest distribution of lsof is available via anonymous ftp from the host lsof.itap.purdue.edu. You'll find the lsof distribution in the pub/tools/unix/lsof directory.
You can also use this URL:
Lsof is also mirrored elsewhere. When you access lsof.itap.purdue.edu and change to its pub/tools/unix/lsof directory, you'll be given a list of some mirror sites. The pub/tools/unix/lsof directory also contains a more complete list in its mirrors file. Use mirrors with caution - not all mirrors always have the latest lsof revision.
Some pre-compiled Lsof executables are available on lsof.itap.purdue.edu, but their use is discouraged - it's better that you build your own from the sources. If you feel you must use a pre-compiled executable, please read the cautions that appear in the README files of the pub/tools/unix/lsof/binaries subdirectories and in the 00* files of the distribution.
More information on the lsof distribution can be found in its README.lsof_<version> file. If you intend to get the lsof distribution and build it, please read README.lsof_<version> and the other 00* files of the distribution before sending questions to the author.
Not all the following manual pages may exist in every UNIX dialect to which lsof has been ported.
access?(2), awk?(1), crash?(1), (3C), ff?(1), fstat?(8), fuser?(1), gethostname?(2), isprint?(3), kill?(1), localtime?(3), lstat?(2), modload?(8), mount?(8), netstat?(1), (8L), perl?(1), ps?(1), readlink?(2), setlocale?(3), stat?(2), strftime?(3), time?(2), uname?(1).
Tutoriais de Tecnologia Web


Degree in Economics, Politics and Social Science from Roskilde University, Denmark; MBA from California State University, East Bay, USA, and from IMADEC, Austria. Born 1967. Joined ORIGIO in May 2015 as President & Managing Director. 20 years of global experience in various managerial positions within the Biopharm, ITC and Medtech industries, and within Capital Markets. Following a career at a hedge fund, he was CEO of Copenhagen Bankers and co-founded NetDania.com. Mr. Hansen worked for Novo Nordisk, the global leader in diabetes care, from 1995-2008 in General Management, Finance and Business Development roles in Central & East Europe, and as Managing Director, Novo Nordisk Scandinavia AB (2003-2008). In 2008 he joined Taconic Biosciences Inc. as President & Officer, General Manager of the Research Models & Solutions Division.


When you are renting a 5, 10, 15, 20, 30 or 40 yard dumpster, you want a company you can trust with prices that make you smile. Give us a call today and see the difference we can make in your next construction or clean out project.
Simply give us a call and we will help you figure out your dumpster rental needs.
Our dumpsters usually go out same-day or next-day depending on when you call.
We provide top-notch service, while going easy on your bottom line. What more could you ask for?
Our trained operators are here to give you a fast and hassle-free experience from start to finish.
Once you are done, simply give us a call and we will get your dumpster picked up right away!
Our staff is here to help whenever you need it. Simply pick up the phone and give us a call.
Most cities or municipalities do not have many regulations regarding dumpster rental as long as you keep the dumpster entirely on your own property during the rental period. If you need to place your container on the street in any way, you will likely have to obtain a permit from the appropriate building permit office in your town. You can check with your local public works department to be sure.
Most Firebaugh dumpster rental companies will take care of securing this permit for you if you rent from them. Make sure that if you’re planning to put the dumpster on the street, the company has made the appropriate arrangements. You should also ensure that you get the permit in a timely manner and at the correct cost. If you thought the dumpster company was getting a permit and they did not, you will be the one who will have to pay the fine that is issued by the authorities.
Your little friend rented dumpster holds up to a couple of tons of dirt. This dimensions are good for your bathroom remodeling task.
Choose the size of dumpster to rent that you will need for the position you will be performing or have done.
Someone who is performing a home renovation task would most probably need a core place to store all of the dirt and garbage they are going to accumulate. Through renovations, there are several materials for example floor tile, wall picture, cabinetry and also kitchen counter covers, among others. Most of the people don't possess or even have direct access to a trash bin just right to store every one of the material.
Something is valuable (similar to copper tubes), and dumpsters come with locks which will prevent thieves. You need to consider a website which will quote you the greatest price and also delivery dates from a basic, and limited, online kind. If you are a novice at renovation -- a homeowner signing up for most of your kitchen renovation for instance, most of these Rent a Waste Management Dumpster in Firebaugh, CA sites undoubtedly are a real furthermore and a time saver which will help you have organized. Once you have ordered up your dumpster, they will supply it and put it quickly on your good deal, where you basically fill it up subsequently call as you prepare for acquire.
Dumpster rental is actually quite simple. You will just need to do a little study before you decide on your company. How big the container is one of the biggest things that you can find to be varied. These types of canisters are generally significant but there could be some which are larger than other individuals. You need to look at the amount of garbage you will be disposing of before making your decision. You want one that holds everything, however you don't necessarily want one that could always be 50 percent empty.
Redesigning your bathroom efficiently into the best replica of the picture which you see in your head is easiest when you eliminate the debris remaining from the ideas for bathroom renovation as quickly as possible. It is possible to transform space conveniently and also beautifully with no bunch of litter and wreck when you use the use of any Rent a Waste Management Dumpster in Firebaugh, CA. A design Rent a Waste Management Dumpster in Firebaugh, CA is a perfect choice for your bathroom renovation. It should be positioned outside of your home in a location for all of the excess waste to end up being disposed of.
Costs: Charges throughout Dumpster rental service business depends upon firm to company and so keep on looking at the charges of the company until you didn't find a suitable company. In addition come companies also bills you delivery costs apart from rental costs so make certain to enquire about precisely the same from the firm. Delivery costs can be any where from $25 to $50 or more. Other than rental charges several companies additionally charges every day rental fees and so make sure to obvious this point having rental service provider. In addition do not forget in relation to tax which you need to shell out over recharged amount. So don't hesitate to find out about tax add-on.
The best way to begin is to start with the simplest means of search. Read through your local mobile phone directories regarding Rent a Waste Management Dumpster in Firebaugh, CA and see what exactly comes up. The local surf forecast in a small area, there may be virtually no businesses that totally advertise underneath that service. You might try perusing your nearest metropolitan region to see if you will discover any companies which will rent long-distance. Make sure and appearance through the newspaper as well. If you fail to find any situation that immediately jumps out at you, go around and also take a look at a number of the dumpsters in your area. See whether they have a firm name on the side. If so, obtain the information with the company and provides them a telephone call. They may be equipped to help you out.
Each junk removal business is distinct. Some tend to be qualified to help hazardous components, while others remain to non-hazardous items. A few also accomplish garbage removal as well as construction web site cleanup. A few full-service companies will even help you go through the items within the building to accelerate the clean-out process. But almost all junk transporting companies really exist to make your cleanout--and the life--just a little bit much easier.
A specialty services that requires Rent a Waste Management Dumpster in Firebaugh is actually community cleanup programs and other charity type projects. Most of the dumpster company will work with the planner of such of your event and infrequently times utilize discounts for the particular sake with the community. The service such as this that makes the particular professional trash solution businesses stand out from the remaining and make these individuals the one halt company that anyone can go to with regards to dumpster needs.
If you move ahead to move forward, you must take certain measures regarding your Rent a Waste Management Dumpster in Firebaugh. Here are a couple of them: Yard cleanups: Via overgrown properties to particles caused by storm damage, sometimes you just have far more yard waste than you are able to deal with yourself. Don't produce an ugly pile outside. Dumpster services give you a simple answer for transporting off actually leaves, trees, plants, even unwanted dirt.
Together with spring rapidly approaching, families in the south east are aware that using lovely spring season days come the dreadful storms involving spring: the particular howling wind gusts, heavy rainfall, hail, tornadoes and in some cases our notorious late snowfalls. Every one of these disruptive conditions patterns could leave in their wakes a large mess available for you and your others who live nearby to clean up. But where do you even commence? Here are a few suggestions to get your town together to clean up after a storm.
Basements certainly are a huge challenge that will need a Rent a Waste Management Dumpster in Firebaugh. You may be wasting old garbage that you've got collected within the last forty years otherwise you may decide to redecorate your cellar. Either way, the next day Rent a Waste Management Dumpster in Firebaugh is actually imperative to finish the same job.
Dumpster rental could be the remedy if you have many trash. You might have a huge occasion in the planning and need an easy method to dispose of every one of the trash. You will be planning a large demolition and need a quick place to retail store debris if you don't take countless trips to the eliminate. Here are some tips that might help you receive started.
On the sadder note maybe your parents have developed down using illness and require to move to an elderly care facility. Or maybe your mother's or father's both have passed on and you require to get their property sold. You already know that your mother's or father's have built up a lot of things via years of reminiscences and you wish to save the particular sentimental things and toss the junk very last thing that.
Maybe you are putting a bathroom on to your home or business. You will additionally need to rent the dumpster to keep the remodelling running in time and without problems. You will possibly only need to rent a small dumpster for this challenge as it hold up to two tons.
Exactly why are these services very theraputic for you? Whether it is renovating the house or constructing a new one, you just have so much to complete other than removing that junk at the end of the morning. You have to take charge of the indoor, painting, style, catering in a very party. It truly is a full time job. It's also possible to go for these types of if you want to handily get rid of the junk that your barbecue party put aside.
A dumpster is a large container, which can be mostly consisting of steel or plastic. They're used for your temporary hard drive of muddle and it helps with disposing the trash generated your own house renovation or construction challenge hassle free.
It is shrewd to rent some sort of dumpster with trolley wheels on in order to move it from the household to the barn on the garage if needed.
With all these kind of advantages, you should definitely opt for a Rent a Waste Management Dumpster in Firebaugh, CAs organization to clean the house and atmosphere around the house construction site.
You shouldn't seem like you have to place a huge full in your spending budget to get rid of waste materials. Look at the rates of several corporations in your area and see how they assess against one another. You can do this by simply calling every one individually or using the internet for getting price comparisons. There are many web based internet sites that allow customers to look at the rates and services of several companies at the same time. There is commonly no charge for this kind of the internet and no accountability to purchase.
These kind of Rent a Waste Management Dumpster in Firebaugh, CAs make it possible for a tenant to get rid of as much junk as they should. For example, for anyone who is redoing an entire roof there may a lot of rubbish falling from every route. These dumpsters permit you to get rid of your junk as it will come instead of having a heap of garbage to bother with after your task is completed. They generate these dumpsters consequently durable of which weight isn't an issue. Additionally, they provide an appropriate lining intended for materials that may be dangerous if not disposed of instantly, such as sharpened objects or areas with nails sticking out from them.
Although people do not know it, there are certain products that cannot be positioned inside these kind of Rent a Waste Management Dumpster in Firebaugh, CAs. It is vital that you know which materials are not to go in your own dumpster when you rent 1. Special squanders or dangerous wastes must not be placed in these kind of containers. Neglecting to follow these pointers can result in penalties and fees as well. Components that are required to be recycled are not permitted in dumpsters for some other trash - they can be to be recycled and within their own package.
Yard cleanups: From overgrown qualities to trash caused by surprise damage, at times you just have a lot more yard waste materials than you are able to deal with yourself. Don't produce an unsightly pile outdoors. Dumpster services provide a simple remedy for trucking off simply leaves, trees, plants, even unwanted dirt.
Now that you know which next day Rent a Waste Management Dumpster in Firebaugh, CA to choose for your structure job, you are to rent it and get your job underway. It can be nice to know you can save money when you will not order some sort of next day Rent a Waste Management Dumpster in Firebaugh, CA that's too large for ones specific structure job.
Please use the form below to contact us. We look forward to working with you and will get back to you as soon as possible. All fields are required


Jobs in L&T Hydrocarbon – Hiring Online
Are you looking for job in L&T Hydrocarbon Engineering, a subordinate company of Larsen & Toubro Limited (L&T), serves the Oil and Gas sector worldwide. The company delivers ‘design to build’ world-class solutions for oil & gas processing, petroleum refining, chemicals & petrochemicals and fertilizer sectors.
The key aspects of our business philosophy are on-time delivery, cost competitiveness, high-quality standards with the focus on best in class HSE and IT security practices. We believe in an attitude and approach that allow for flexibility of operation and agility in response. The business is structured into the following verticals: Onshore, Offshore, Construction Services, Modular Fabrication, Engineering Services
are you looking for job in L&T Hydrocarbon Engineering – L & T HL & T Hydrocarbons offers a variety of job opportunities including areas Administrative, Internships, Finance & Accounting, Marketing / Publicity / Advertising, Sales, Sales Planning. Whether you’re professional in Administrative, Accounting and Finance, Engineering, Human Resources, Information Technology / Services, Marketing and Trading and any other areas, there is a career opportunity for you at L&T Hydrocarbon.
Applying for job and further details Click the below link Apply now!
Apply now for the jobs
- Multiple Jobs Vacancies Open in Dubai Airports
- Latest Job Vacancies Open in Dubai Ports World
- Abu Dhabi Ports Job Opportunities – Abu Dhabi Ports Jobs
- Makamin Offshore Saudi Needs Staff
L&T Hydrocarbon Benefits
L&T Hydrocarbon provides employees with competitive pay and comprehensive benefits program that will allow you to develop professionally and reach long-term goals of the race. The balance of Work / Life is encouraged at L&T Hydrocarbon and the company offers several programs like “live like work” that offers advice, referrals and resources on parenting, career planning, family care and leaves of operation (planning) education. Other benefits include flexible work arrangements with supervisor approval, adoption assistance and dependent care spending accounts. L&T Hydrocarbon also provides other pay and competitive advantages.
more related keywords: l&t hydrocarbon Jobs, l&t hydrocarbon Recruitment, l&t hydrocarbon vacancy, l&t hydrocarbon projects, l&t hydrocarbon bangalore, l&t hydrocarbon engineering limited contact details, l&t hydrocarbon salary, l&t hydrocarbon new projects, l&t hydrocarbon eip login, l&t hydrocarbon wiki


Sneak Peek: From Our School Counselor!
We are ready and excited to be on winter break! You cannot pour from an empty cup, so be sure to take time to spend with your loved ones. I am always very thankful and touched that our community knows how to support each other. Those who reached out because you need a hand were met by another family’s hands ready to help. Our staff and families worked hard to fulfill wishes for many in need this year. I love creating that magic for our students! Thank you so much for your willingness to support our Forest Ridge community! This time of year and ALL year I know our students learn kindness and gratitude from all of you. THANK YOU and have a RELAXING break!


Joseph Epstein is an essayist and short story writer. He is the author of Fred Astaire (Yale University Press) and served as contributing editor for the Weekly Standard.
Next in the summer 2012 Issue
A review of The Book of Man: Readings on the Path to Manhood, by William J. Bennett
A review of Silenced: How Apostasy and Blasphemy Codes are Choking Freedom Worldwide, by Paul Marshall and Nina Shea
Reading the Iliad in English.


.- "The dignity of their ministry doesn't exempt priests from difficulty, from temptations and from weaknesses that sometimes shake and put their path towards holiness to the test," said Cardinal Oscar Andres Rodriguez Maradiaga on Friday. To avoid "burnout," he said, pastors must center their attention on Christ, but also remain conscious of their own human and psychological needs.
The Honduran cardinal and head of Caritas Internationalis was speaking in Rome at the release of the book, "Ease and hardship in the pastoral service and the mission of the Church. Recognizing and curing 'burnout' in devotion to others."
Reflecting on the content and theme of the new book, the prelate said that priests, overwhelmed by the many challenges, excessive requests and possible difficulties arising within their ministry can become tired, experience psychological harm and eventually suffer from "pastoral burnout."
As their ministry goes beyond just "things to do," requiring their full attention and participation in relations with people of all ages and conditions, explained Cardinal Maradiaga, "if it is not balanced with a healthy interior life, it can cause a sense of uncertainty and inadequacy emerge, or also the fear of failing or feeling judged, thus (making them) lose sight of the very meaning of their work."
To combat the possibility "denaturing" their sense of altruism in loving others, he said, they must "nourish a constant attention to themselves, to their own human and psychological needs. But also a constant attention to He who they are called to serve, Jesus the Good Shepherd ..."
Citing the research of the book's author, Professor Giuseppe Crea, Cardinal Maradiaga explained that to avoid this "wearing spiral," they must be conscious of how to live their devotion to others, noting personal hardships, "but above all the profound motivations of their service."
This requires a lifestyle coherent with the faith, he said, and a love "genuinely oriented to the good and the salvation of those that are entrusted to their pastoral care."


Good morning, and here’s what’s “out there” about the Seahawks for today, August 31, after finishing the preseason with a record of 4-0 following their 21-3 victory over the Oakland Raiders Thursday night.
Danny O’Neil of the Seattle Times recaps last night’s victory, and speaks to the team’s depth that was continually on display through four preseason games,”The Seahawks outscored opponents 67-21 in the second half of exhibition games this season, which speaks to the team’s improved depth. Seattle must trim its roster to 53 players on Friday, and will open the regular season Sept. 9 in Arizona. ‘We did a great job this preseason,’ [Russell] Wilson said. ‘But now it’s time to look forward on to what’s next, and that’s the season. Obviously, we have to take one step at a time.'”
O’Neil also highlights rookie defensive end Bruce Irvin in his game notebook, who tallied his first NFL sack last night, “It took Bruce Irvin 3 ½ games before he finally got to the opponent’s quarterback. Once he registered his first half a sack in the third quarter against Oakland, Irvin couldn’t wait to get back there. He had another sack in the fourth quarter, a tackle for loss and nearly another sack, turning Seattle’s exhibition finale into a coming-out party for the Seahawks’ first-round pick. ‘I mean, I wanted to get a sack,’ Irvin said. ‘I came so close last week. I wanted to get my feet wet.’ ”
Eric Williams of the Tacoma News Tribune digests Thursday night’s win, with a couple notes on running back Vai Taua, “Running back Vai Taua is one of those players who stood out Thursday. The University of Nevada product served as a tackling dummy most of 2011, working as the scout squad running back for Seattle while spending most of the season on the practice squad. But Taua finally got a chance to dish out some punishment Thursday. Taua finished with 49 yards on nine carries, including a 2-yard touchdown run. Taua also had five catches for 39 yards as he attempts to lock up a spot on Seattle’s 53-man roster. Taua offers some versatility because he can play both tailback and fullback, along with playing on special teams.”
Dave Boling of the Tacoma News Tribune takes a look at Seattle’s ball-hawking defense, who has scored points in three of the team’s four games this preseason, “Particularly relevant with the first turnover was that it was first-round draft pick Bruce Irvin who forced a fumble on a punt to set up the Seahawks’ first score. Irvin tackled Raiders returner Roscoe Parrish, forcing a fumble that was recovered by fellow rookie Bobby Wagner. The turnover set up a 25-yard field goal by Steven Haushka. In the second quarter, another rookie, cornerback Jeremy Lane, picked off a Matt Leinart pass intended for Brandon Carswell to set up another Haushka field goal (29 yards). The Seahawks led the NFC in turnover differential through the first three exhibition games at plus-five, having forced eight turnovers. The turnovers helped the Hawks power to the league’s best scoring differential of plus-60 (101-41).”
John Boyle of the Everett Herald has his game report from Thursday night, “Seahawks coach Pete Carroll likes a lot of what he has seen from his team coming out of his third preseason in Seattle. ‘We’re so much tighter with what we’re doing,’ Carroll said. ‘The messaging and philosophy is embedded. Our style is clear. Now I don’t know if we’re going to bring it to life in the regular season, I don’t know that, but we’re going to try. … This is the style of play that we’ve been looking for’ ”
Brady Henderson of mynorthwest.com sums up Thursday night’s performance from rookie defensive end Bruce Irvin, “It was the type of performance the Seahawks had in mind when they made Irvin the 15th overall pick. And it was just what he needed after a quiet preseason, even if it came in a meaningless game. ‘It feels good to finally have a little success,’ a smiling Irvin said afterward before putting his night in the proper perspective. ‘But it don’t count. The stat sheet starts over next week. That’s why I wasn’t really concerned when people was worried. It don’t count, so I’ve just got to keep working and get ready for the season next week.’ ”
Art Thiel of SportsPressNW.com wraps Thursday’s victory and Seattle’s preseason, “For whatever it’s worth in dominating the Titans, Broncos, Chiefs and Raiders in the preseason, the Seahawks allowed averages of 248 yards of total offense and 15 first downs in a combined 122-44 domination of the scoreboard. Leading the NFC in takeaways before the game with seven, the defense recovered another fumble and added an interception. ‘It’s exciting, but you have to take it with a grain of salt,’ said cornerback Richard Sherman. ‘Every (offense) is vanilla, they’re not doing much different. No schemes. But we have extremely high expectations for ourselves.’ ”
Curtis Crabtree of 950 KJR AM takes a crack at predicting the Seahawks 53-man roster.
Mike Sando of ESPN.com revisits three nuggets from Thursday’s matchup with the Raiders, including a comment on Bruce Irvin’s impact, “First-round draft choice Bruce Irvin played deep into the game as the Seahawks tried to get their rookie defensive end into a rhythm. They were going to leave him in the game until Irvin produced, and once he did, they weren’t going to take him out. Irvin feasted on the Raiders’ backups in the second half. He finished with 1.5 sacks and three quarterback hits after failing to register on the defensive stat sheet in the first three preseason games. Irvin also forced a fumble while working on the punt-coverage team. Irvin can now emerge from the preseason with something to build upon.”
Sando also rehashes a conversation he had with Matt Williamson of Scouts, Inc., who believes naming rookie quarterback Russell Wilson the starter was the move that could put Seattle over the top, ” ‘I very much believe Russell Wilson will have the best year of any quarterback in the division,’ Williamson said. ‘Sam Bradford has a chance to be a very good one, but he looks terrible and his supporting cast is a mess. Arizona is a mess. I’m not a huge Smith believer.’ In Wilson, Williamson see the potential for Cam Newton-type production. He thought Wilson, a third-round choice, should have gone a round earlier. ‘One thing about him, his college history shows he doesn’t turn the ball over,’ Williamson said. ‘He’ll do more at this level, but he is not going to hurt the team the way rookie quarterbacks usually do. He’s very smart, really knows where to go with the ball.’ Williamson went with Pete Carroll as his projected coach of the year. ‘We’ll look back in 16 games and say, ‘Wow, naming Wilson the starter over Matt Flynn was a gutsy move by Coach Carroll and that is why they won the West,’ ‘ Williamson said.”
Scott Pianowski of YahooSports.com lists the Seattle Seahawks as one of his “Five NFL teams that are better than you think“. Pianowski says, “Seattle just completed a dominant 4-0 preseason, outscoring opponents by 78 points, and while that doesn’t guarantee a thing going forward, a strong August has correlated to a strong season over the last couple of decades (mind you, it didn’t help Seattle in 2009, when a 4-0 preseason led to a 5-11 mark). I’m expecting the Seahawks to post a winning record in 2012, and they should challenge San Francisco for the division title.”
From our fullback Michael Robinson, we have the much-anticipated next installment of his “Real Rob Report“, which features appearances by quarterback Russell Wilson, cornerback Richard Sherman, guard John Moffitt, center Max Unger, defensive end Greg Scruggs, and punter Jon Ryan.
Finally, Tony Ventrella gives us a video recap of Thursday’s events.


The year 2013 is almost here, which means we will begin to create our list of resolutions very soon. Even though many children may not understand what New Year’s resolutions are, we created a fun list that we bet parents would be jumping for joy over if their children actually resolved to do these things (we know we would!):
- I will not throw food or toys at my brother/sister
- When I scream about something, I won’t shriek or make my parents jump out of their skin
- I will work on trying to understand what the word “no” means (but all I can do is “try”)
- I will say thank you more
- I will not color on objects that are not meant to be colored on
- I will not leave my toys out where my parents can trip on them
- I will not be the pickiest eater that my parents know
- I will not lose interest in anything my parents buy me for at least a month
- I will not ask silly questions that no one can answer but me
- I will give more hugs and kisses each and every year
What resolution would add to this list for your child?
Have a Happy New Year!


Start with one of Maui's top 10 beaches, add a several mile oceanfront walkway, mix in a well appointed island style condo, and top off with a spectacular Maui sunset. No wonder they say "Maui No Ka Oi" (Maui is the best)!
Polo Beach Club Condo #502 is a beautiful ocean front unit with Island feel decor situated approximately 40 feet from the ocean surf. Located on the south side of the resort, this unit overlooks the pool/spa, Molokini and Lanai. It offers incredible sunset viewing from the lanai. The unit offers the following amenities:
Dingo Dog DesignWebsite Design and SEO Company
Copyright. Polo Beach Condo. All rights reserved.


"Ya know what.. I think that the ladies who took my blood pressure are full of it.. My boss has an electronic blood pressure tester and I used it within 30 minutes of the first test.. I'm at 110/70.. which is what I normally am and have ..."
Are you sure you want to delete your ?
You will no longer be able to add new data to this tracker.


Gay marriage is at the top of the news these days, so the Trap Door Theatre's decision to produce David Mamet's bitter comedy Boston Marriage could not be more timely. Mamet's tale is a faux-Victorian intrigue about two nineteenth-century lesbians whose live-in relationship is considered by society to be platonic. ("Boston marriage" was a term for romantic friendships between unmarried women.) At first glance the subject matter could hardly be further from Mamet's trademark style. The playwright and screenwriter is known for his tough-talking, macho male characters. His critics have decried a perceived misogyny in his plays, especially in Oleanna and Speed-the-Plow. Perhaps as a response to his detractors, Mamet wrote this all-female sendup, spinning out an elaborate sexual ruse amid the florid, Jamesian language of the Victorian era.
Imperious doyenne Anna (Sarah Davida) proudly reports to her long-time lover Claire (Lisa Manuli) that she has duped a gullible wealthy man into giving her a prized necklace and financial assistance that will support both women in style. But Anna's glee turns to pique when she learns that Claire plans an assignation with a new lover, an underage girl. Worse, Claire has the cheek to ask Anna for the use of the house for her tryst. Anna relents in exchange for a chance to watch the seduction. The plan is upended when the girl recognizes Anna's new necklace as her own mother's and flees. Faced with financial ruin and romantic disappointment, the Sapphic duo scramble to recover the sugar daddy and the girl as well.
Mamet's script features a dazzling parody of oh-so-proper Victorian language punctuated by sudden bursts of vivid profanity. The contrast makes for most of the humor in Boston Marriage, which director Stuart Meltzer stages as an arch, tongue-in-cheek burlesque reminiscent of Charles Busch's Vampire Lesbians of Sodom. This strategy exploits the skills of Davida, who has a dry comic delivery and excellent timing, wringing quite a bit of humor out of long, deadpan pauses. Meltzer also sets loose Ivonne Azurdia as a slapstick Scottish maid whom Anna continually mistakes as Irish, berating and insulting the poor wretch at every turn. The result is a fizzy entertainment that's a nice vehicle for the young cast -- but it's a misinterpretation of the text, playing it as if it were Oscar Wilde and ignoring Mamet's darker, disquieting undertones.
Trap Door Theatre at the Black Box Theatre, Miami Dade College North Campus, Building #5, 11380 NW 27th Ave., Miami
By David Mamet, directed by Stuart Meltzer. With Ivonne Azurdia, Sarah Davida, and Lisa Manuli. Through March 20. Call305-237-1438.
Mamet isn't merely having a go at Victorian style, he's laying an ambush for politically correct feminism, the very critics who took shots at him for failing to write fully realized female characters. Boston Marriage is Mamet's revenge. Here are fully developed female characters all right, but they are verbose, loathsome preeners, and their treatment of the hard-luck servant is a pointed critique of upper-class feminist hypocrisy. Anna and Claire continually decry their mistreatment by men, then blithely dun the maid with endless humiliations until they realize the weak, subservient young woman is the means to their salvation (a story structure Mamet used in the earlier Speed-the-Plow).
The playwright is practicing his own form of equal opportunity: These women aren't meant to be empathetic; they're as awful as his usual male characters. This production, however, opts to ignore the script's provocations, painting Anna and Claire as nastily funny but ultimately positive heroines, while the maid is a freckle-faced Raggedy Ann of no consequence. The result is a production that's charming and safe, two terms not usually linked with this author. In fact Mamet comes not to praise lesbian feminism, but to bury it.
If you like this story, consider signing up for our email newsletters.
SHOW ME HOW
You have successfully signed up for your selected newsletter(s) - please keep an eye on your mailbox, we're movin' in!
Despite its shortcomings, the performance serves as a credible showcase for its acting ensemble and production artists. The black-box theater is graced by Michael McKeever's evocative, minimalist Victorian décor and producer Meredith Lasher's costume design, an array of luxuriant Victorian fashions. The production is also a calling card for the company itself. Operating with little institutional or philanthropic support, Trap Door has limited resources but a clear mission. Meltzer and Lasher intend an ongoing collaboration with students at their Miami Dade College north campus base, encouraging young artists to develop their own theater companies. This not only generates gigs for working actors, it serves to excite and inspire a whole new generation of creativity in South Florida.


had been looking for a way to open up the fashion system ever since her studies at the Gerrit Rietveld Academy in Amsterdam. How can we create without participating in the endless, trend-driven cycle of consumption? The answer came in the form of JOIN collective
, a design and research project which explores fashion as a collective practice: anyone can participate. Thus, she transformed the traditional relationship between creator and client.
: 12h30 (UTC+1)
You have to register for the talk here
You will receive a link to the webinar the same day by email.
If you have any issues, please contact email@example.com


A few years ago, a bookless library would have been a crazy concept, like a waterless swimming pool or a breadless sandwich.
Yet such a library is opening in San Antonio, Texas, this fall. There, with nary a book in sight, patrons will read on computer screens.
Crazy? Pat Conley doesn’t think so.
As the director of the Washington County library system, she is watching as per-capita demand for books stagnates, computer demand soars and big, free-standing libraries begin to fade into history.
In a recent presentation about the future of libraries, she said the county won’t be getting a bookless library soon, but it is taking steps in that direction.
The demand for old-fashioned books has stalled. Excluding e-books and other computer downloads, the number of materials checked out of county libraries — including affiliate libraries in Stillwater and Bayport — was 9 percent less in 2012 than the year before.
The decline was partly because the library cut back its hours and closed three libraries. But circulation of e-books and other computer downloads rose 126 percent during that time.
Ramsey County is seeing the same trend.
Sandy Walsh, deputy director of libraries, said computer-based checkouts as a percentage of total circulation are on pace to be double that of 2012.
Walsh cautioned that although the trend toward e-books is clear, it’s moving slowly. Downloadable checkouts are just 4.5 percent of the total, she said, so demand for paper-based books will be strong for a long time.
Bookless libraries may be common in the future, but not soon. “It’s an interesting idea, for sure,” Walsh said.
The Washington County library system is expanding its e-book collection, Conley said. But it isn’t inexpensive — libraries pay about $30 for an e-book.
Many publishers won’t sell to libraries, for fear it will hurt book sales. One sells e-books that can be checked out only 26 times.
“You really are leasing that book,” Conley said. “You don’t own it. There is a lot of angst about that.”
The trend from paper books to e-books is one reason that buildings can be smaller.
“The community library of 5,000 to 30,000 square feet — that is where the future lies,” Conley said. A 5,000-square-foot library — the size of the bookless library in Texas — is roughly the size of a basketball court.
And the free-standing Carnegie Library is becoming a thing of the past. Conley said today’s libraries share space with coffee shops, government offices and stores.
The R.H. Stafford Library in Woodbury is a good example, she said. One of the busiest in the state, it sits alongside an ice cream shop, a YMCA and an indoor playground and park.
Ramsey County’s Walsh said libraries are evolving into community centers, offering meeting spaces and public services. Ramsey County has libraries sharing space with community centers in New Brighton and North St. Paul.
Washington County already is moving in the direction of book-free libraries.
When it wanted to expand into Hugo in 2010, instead of building a library, it added a kiosk. Patrons can request books via computer and have them delivered to lockers.
Is a bookless library in the county’s future? Maybe.
“We are in the process of accessing what that would look like,” Conley said.
Architectural drawings on the Texas library’s website show rows of stools facing computer screens in a room that looks like a classroom.
“It could be a great adjunct to the traditional library system,” Conley said.
“It is an exciting time. It is an experimental time.”
HOW TO ORDER AN E-BOOK
Card-carrying library patrons can check out e-books by accessing a library system’s website.
— Ramsey County: rclreads.org
— Washington County: www.co.washington.mn.us/library


Discussion in 'General Discussion' started by JBeukema, Aug 19, 2009.
Guns to be allowed on campus? : News : KRCG
The chances of a whacko coming onto a campus and killing you are next to nothing.
Arming students is a stupid idea...I'd not pay tuition to any college that allowed students to carry weapons.
Separate names with a comma.


Renoline will be stocking Rat Blockers in all sizes up to 250 mm – also for lined pipes and back flow preventers. They are produced from Marine Grade Stainless Steel AISI 316 and have gone through thorough testing and EU-approval. Furthermore it is patented worldwide and as can be seen from the following video it is very straightforward to install – it takes longer to remove the lid to the well than it does to actually install the Rat Blocker.
Every year thousands of hotels, restaurants, canteens and cafés are closed due to rat problems resulting in loss of money and reputation. This could be avoided by installing a Rat Blocker and furthermore rats are a source of water contamination and spread diseases. This is an inexpensive and environmentally friendly way of preventing rat attacks which in 95 % of cases originate from the sewers. This is also a way of reducing the use of poison which according to a UK study 75 % of rats are now resistant to.