1834757 Members
2888 Online
110070 Solutions
New Discussion

Re: LOGHOST

 
SOLVED
Go to solution
Richard Mitts
New Member

LOGHOST

I was trained to make sure that I enter the machine ID and its qualified domain name and loghost after the IP address example: (205.34.90.1 jots2 jots2.XXX.navy,smil.mil loghost) I am now told that I don't have to do that. Which is the right way and can you explain what loghost does.
Thanks
Richard
5 REPLIES 5
Balaji N
Honored Contributor
Solution

Re: LOGHOST

hi

its always good to have the hostname and FQDN of the host in the /etc/hosts file.

xxx.xxx.xxx.xx hostname hostname.domainname.


regarding the LOGHOST entry, i remember reading that it is the server were the syslog entries are sent to for logging (in solaris). not sure if it works in hp.

hth
-balaji
Its Always Important To Know, What People Think Of You. Then, Of Course, You Surprise Them By Giving More.
Steven E. Protter
Exalted Contributor

Re: LOGHOST

You don't have to do that.

Both ways are right.

I run my newer systems with fully qualified host names because it makes getting their sendmail accepted and many other functions easier in our environment.

I put the fully qualified hostname in /etc/rc.config.d/netconf and thats it.

This is based on HP-UX and Linux experience only. The netconf file is an HP-UX file, this is not a Linux forum, hence no example.

As far as I know there is no huge impact and the decision on which way to go is based on shop standards, which may be confused since you have been trained one way and being told you don't have to.

I can't see a lot of impact in this decision.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Steven E. Protter
Exalted Contributor

Re: LOGHOST

You don't have to do that.

Both ways are right.

I run my newer systems with fully qualified host names because it makes getting their sendmail accepted and many other functions easier in our environment.

I put the fully qualified hostname in /etc/rc.config.d/netconf and thats it.

This is based on HP-UX and Linux experience only. The netconf file is an HP-UX file, this is not a Linux forum, hence no example.

As far as I know there is no huge impact and the decision on which way to go is based on shop standards, which may be confused since you have been trained one way and being told you don't have to.

I can't see a lot of impact in this decision.

As far as HP-UX goes....
[1741]# man loghost
No manual entry for loghost.


SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Richard Mitts
New Member

Re: LOGHOST

Balaji and SEP thanks for the quick response. Beings there is no impact on things I will continue to do it my way, because like you said SEP it makes some functions easier.
"Rich"
Sunil Sharma_1
Honored Contributor

Re: LOGHOST

Hi,

FQDN entry in /etc/hosts file is sufficient to perform all functionality. The entry related to loghost id used by syslog daemon to redirect the syslog messages to different server and it's mainly used in solaris operating system.

SS
*** Dream as if you'll live forever. Live as if you'll die today ***