mstombs wrote:
it also merges in a dhcp lease file…
My recollection was that Dnsmasq is ran with an option not to store a lease file. (See this thread.)
You can get Dnsmasq to dump its cache:
When it receives a SIGUSR1, dnsmasq writes statistics to the system log. It writes the
cache size, the number of names which have had to removed from the cache before they
expired in order to make room for new names and the total number of names that have
been inserted into the cache. For each upstream server it gives the number of queries sent,
and the number which resulted in an error. In --no-daemon mode or when full logging is
enabled (-q), a complete dump of the contents of the cache is made.
But getting the full list of names depends on the -q switch, which I'm sure isn't enabled, and it inconveniently writes the info to syslog.
I'd be curious to know if there was some other way of getting at the Dnsmasq lease info. (Aside from indirectly via the arp table.)
Smith wrote:
is there a way to see currently ssh connected users
This will give you a rudimentary indication:
# ps | fgrep dropbear
440 root 1156 S dropbear -p 22 -a
6672 root 1208 S dropbear -p 22 -a
6684 root 1208 S dropbear -p 22 -a
The low numbered process is the listening daemon that is always present. One additional child is spawned for each user logged in. So user count = dropbear count - 1. (The above illustrates two logins.)
-Tom
Smith (guest) 26 Jun 2012 12:51
(account deleted)
