Sponsored Content
Full Discussion: Squid+DNS
Operating Systems Linux Squid+DNS Post 302202514 by andryk on Thursday 5th of June 2008 03:44:41 AM
Old 06-05-2008
Glad to hear that.
 

10 More Discussions You Might Find Interesting

1. Solaris

Solaris DNS Client For Microsoft DNS Server

hey guys, how to add soalris box as a microsoft DNS Client ? and how to register in the microsoft DNS ?? i managed to query from the DNS server after adding /etc/resolve.conf and editing /etc/nsswitch.conf but i need to register the soalris server (dns Client) into Microsoft DNS automatically.... (3 Replies)
Discussion started by: mduweik
3 Replies

2. UNIX for Dummies Questions & Answers

Squid dns

Hi Guys I have a squid proxy server. I have some settings in the no proxy for exclusions on 700 client machines using firefox. I need to add to this exclusion but instead of changing 700 machines settings, is there anyway you can allow the squid server to handle this. I have gone into the... (1 Reply)
Discussion started by: beardiebeardie
1 Replies

3. UNIX for Advanced & Expert Users

Squid Error

Hi all , i m getting below error in access.log while running skype application on linux. Proxy packages : Squid redirected through SquidGuard with LDAP auth. system : Ubuntu 6.06 Firewall : pf 227032649.603 0 system_IP_add TCP_DENIED/407 1802 GET... (0 Replies)
Discussion started by: jagnikam
0 Replies

4. Web Development

Need help for Configuring Squid-2.6

Hi, Previously I was using squid-2.5 accelerated but due to link breaking issue, I have upgraded it to 2.6 but i am unable to configure it with accelerated support. Kindly help me to make it accelerated proxy server. My 2.6 squid.conf : ##################################################... (0 Replies)
Discussion started by: jagnikam
0 Replies

5. Linux

caching in squid

hi, i installed fedora core 12, and i installed squid v 3, i need to know how can i cache everything. anyone can help me please (1 Reply)
Discussion started by: zazoo
1 Replies

6. UNIX for Advanced & Expert Users

DNS server choice: Windows DNS vs Linux BIND

I'd like to get some opnions on choosing DNS server: Windows DNS vs Linux BIND comparrsion: 1) managment, easy of use 2) Security 3) features 4) peformance 5) ?? I personally prefer Windows DNS server for management, it supports GUI and command line. But I am not sure about security... (2 Replies)
Discussion started by: honglus
2 Replies

7. Red Hat

DNS A-Record point to another DNS

Hi, I have a question on how to point the DNS server-1's A-record to second DNS server, which is DNS server-2. So, the computer can access other domain which only listed in the DNS server-2. The scenario is as follow: http://img689.imageshack.us/img689/6333/12234.png How to configure this... (4 Replies)
Discussion started by: Paris Heng
4 Replies

8. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

9. IP Networking

Squid vs iptables = no Squid access.log?

Hello, I have a pretty useless satellite link at home (far from any civilization), so I wanted to set up caching in order to speed things up. My Squid 2.6 runs "3128 transparent" and is set up quite well on a separate machine. I also have my dd-wrt router to move all port 80 traffic through... (0 Replies)
Discussion started by: theWojtek
0 Replies

10. Solaris

DNS client added to DNS server but not working

Hi, We have built a new server (RHEL VM)and added that IP/hostname into dns zone configs file on DNS server (Solaris 10). Reloaded the configuration using and added nameserver into resolv.conf on client. But when I am trying nslookup, its not getting resolved. The nameserver is not able to... (8 Replies)
Discussion started by: snchaudhari2
8 Replies
RWHOD(8)						    BSD System Manager's Manual 						  RWHOD(8)

NAME
rwhod -- system status server SYNOPSIS
rwhod [-i] [-p] [-l] [-m [ttl]] DESCRIPTION
The rwhod utility is the server which maintains the database used by the rwho(1) and ruptime(1) programs. Its operation is predicated on the ability to broadcast or multicast messages on a network. The rwhod utility operates as both a producer and consumer of status information, unless the -l (listen mode) option is specified, in which case it acts as a consumer only. As a producer of information it periodically queries the state of the system and constructs status messages which are broadcasted or multicasted on a network. As a consumer of information, it listens for other rwhod servers' status messages, vali- dating them, then recording them in a collection of files located in the directory /var/rwho. The following options are available: -i Enable insecure mode, which causes rwhod to ignore the source port on incoming packets. -p Ignore all POINTOPOINT interfaces. This is useful if you do not wish to keep dial on demand interfaces permanently active. -l Enable listen mode, which causes rwhod to not broadcast any information. This allows you to monitor other machines' rwhod informa- tion, without broadcasting your own. -m [ttl] Cause rwhod to use IP multicast (instead of broadcast) on all interfaces that have the IFF_MULTICAST flag set in their "ifnet" structs (excluding the loopback interface). The multicast reports are sent with a time-to-live of 1, to prevent forwarding beyond the directly-connected subnet(s). If the optional ttl argument is supplied with the -m flag, rwhod will send IP multicast datagrams with a time-to-live of ttl, via a SINGLE interface rather than all interfaces. ttl must be between 0 and 32 (or MAX_MULTICAST_SCOPE). Note that -m 1 is different from -m, in that -m 1 specifies transmission on one interface only. When -m is used without a ttl argument, the program accepts multicast rwhod reports from all multicast-capable interfaces. If a ttl argument is given, it accepts multicast reports from only one interface, the one on which reports are sent (which may be controlled via the host's routing table). Regardless of the -m option, the program accepts broadcast or unicast reports from all interfaces. Thus, this program will hear the reports of old, non-multicasting rwhods, but, if multicasting is used, those old rwhods will not hear the reports generated by this program. The server transmits and receives messages at the port indicated in the ``who'' service specification; see services(5). The messages sent and received, are of the form: struct outmp { char out_line[8]; /* tty name */ char out_name[8]; /* user id */ #ifdef __LP64__ int out_time; /* time on */ #else /* !__LP64__ */ long out_time; /* time on */ #endif /* __LP64__ */ }; struct whod { char wd_vers; char wd_type; char wd_fill[2]; int wd_sendtime; int wd_recvtime; char wd_hostname[32]; int wd_loadav[3]; int wd_boottime; struct whoent { struct outmp we_utmp; int we_idle; } wd_we[1024 / sizeof (struct whoent)]; }; All fields are converted to network byte order prior to transmission. The load averages are as calculated by the w(1) program, and represent load averages over the 5, 10, and 15 minute intervals prior to a server's transmission; they are multiplied by 100 for representation in an integer. The host name included is that returned by the gethostname(3) system call, with any trailing domain name omitted. The array at the end of the message contains information about the users logged in to the sending machine. This information includes the contents of the utmpx(5) entry for each non-idle terminal line and a value indicating the time in seconds since a character was last received on the terminal line. Messages received by the rwho server are discarded unless they originated at an rwho server's port or the -i option was specified. In addi- tion, if the host's name, as specified in the message, contains any unprintable ASCII characters, the message is discarded. Valid messages received by rwhod are placed in files named whod.hostname in the directory /var/rwho. These files contain only the most recent message, in the format described above. Status messages are generated approximately once every 3 minutes. The rwhod utility performs an nlist(3) on /boot/kernel/kernel every 30 minutes to guard against the possibility that this file is not the system image currently operating. SEE ALSO
ruptime(1), rwho(1) HISTORY
The rwhod utility appeared in 4.2BSD. BUGS
There should be a way to relay status information between networks. Status information should be sent only upon request rather than continu- ously. People often interpret the server dying or network communication failures as a machine going down. BSD
December 11, 1993 BSD
All times are GMT -4. The time now is 09:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy