I have a number of open files connecting to the rpcbind process running on HPUX 11.00. Usinf lsof -p rpcbind I am unable to identify the ip addresses of the open files. Example of one below - Any ideas?
rpcbind 19754 root 100u inet 72,0x72 0t0 TCP 79.60.53.40:* (BOUND) (2 Replies)
hello
Sorry but i don't understand very well the lsof command with the man.
Can you explain to me what is the use of this command ?
thank you (2 Replies)
Hi All,
I'm having a problem with "lsof" in HP-UX system. Its giving me 2 two different results when running it.
1 . lsof -p 'PID' | wc -l -----gives some value
2 . lsof | grep 'PID' | wc -l
The above two commands gives me two different values with the same PID......
Thanks (6 Replies)
Hi All,
My target is to find the biggest files opened by any process and from that i have to find process id and the corresponding file also.
To get the process id which is accessing the biggest file in the given file system, i am using the below command.
lsof -s /home/arun/my_work |... (3 Replies)
I'm looking to list all of the files open at a certain time up on a UNIX box.
From looking on the internet, it looks as though lsof is the most common.
However have tried this and got the following:
ksh: lsof: not found
Now having gone into bash mode and hit tab twice I see that lsof... (3 Replies)
Hi,
I typed lsof -i :80 in my putty but i am not able to get sockets related to port 80
Can any one help me out soon
Can anyone point out the reason for not able to get the related sockets
Output of what i am getting in my putty is displayed below
training@use:~> lsof -i :80... (4 Replies)
In Linux and Solaris lsof accepts the -X switch which allows to see if deleted files are still in use and eat disk space. In HP-UX it is now working and it is a problem... today one of my filesystems on the server was increasing very fast but existing file sizes were not really changing. lsof shows... (3 Replies)
Hi,
I am trying to find the files in a specific directory that are currently in open state. I need this information to archive the old files that are not active in the directory.
I get the following output when I try the command $ lsof +d '/var/tmp/'|awk '{print $9}'|sort -u
NAME... (1 Reply)
Discussion started by: ryzen7
1 Replies
LEARN ABOUT DEBIAN
shorewall-exclusion
SHOREWALL-EXCLUSION(5) [FIXME: manual] SHOREWALL-EXCLUSION(5)NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file.
SYNOPSIS
!address-or-range[,address-or-range]...
!zone-name[,zone-name]...
DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by
a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in
CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the
form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words.
Warning
If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the
rule generated for a parent zone.
For example:
/etc/shorewall/zones:
#ZONE TYPE
z1 ip
z2:z1 ip
...
/etc/shorewall/policy:
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
/etc/shorewall/rules:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule.
In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also
be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows:
o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT
match set1 OR NOT match set2 ... OR NOT match setN.
o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1
AND NOT match set2 ... AND NOT match setN.
EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4
!192.168.3.4
Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4
!192.168.1.0/24,10.1.3.4
Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8
!192.168.1.3-192.168.1.12,10.0.0.0/8
Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9
192.168.1.0/24!192.168.1.3,192.168.1.9
Example 5 - All parent zones except loc
any!loc
FILES
/etc/shorewall/hosts
/etc/shorewall/masq
/etc/shorewall/rules
/etc/shorewall/tcrules
SEE ALSO shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
shorewall-tunnels(5), shorewall-zones(5)NOTES
1. shorewall-ipsets
http://www.shorewall.net/manpages/shorewall-ipsets.html
[FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)