[Sunhelp] Setup syslog entries to another host?

Robert.Cross at scottish-newcastle.co.uk Robert.Cross at scottish-newcastle.co.uk
Thu Jul 22 04:38:10 CDT 1999


--Boundary_(ID_xkilHTH8X28sOrQ8dugrjw)
Content-Type: TEXT/PLAIN
Content-Transfer-Encoding: 7BIT

jmb wrote:
>I maybe wrong....but my first idea would be to make a symbolic link so
>syslog on the localhost would be a kind of an alias of syslog on the
>remote host.
>Can it work that way?

Yes, you CAN do that. But, what you're actually doing is just making sure
that the syslog CONFIGURATION is the same on the two machines. It won't
actually send the entries to the other machine. I also would have thought it
a bad idea to have a syslog.conf as an NFS link. What happens if your 
destination goes down, or the network fails on the source - no messages! =8-o

If you want to make the syslog configurations the same, the best method I know
is a small cron job on the 'slave' machines that sucks the file from the 
'master' 
machine and then restarts syslogd. You can, of course, add all kinds of frills, 
e.g.
not restarting syslogd if syslog.conf wasn't changed.

If you want to send the syslog output to another host, just edit 
/etc/inet/hosts, 
(this is the file that /etc/hosts points to - or at least on Solaris 2.6 and 
previous).
Move the alias 'loghost' to the machine that you want to receive the log 
entries,
it'll probably be attached to 127.0.0.1 by default. We've redirected outputs 
from
various Suns and IBM kit to one Sun for processing here, so I'm pretty sure that
this is the correct way.

Keep at it - ain't Unix wonderful?

Regards

Bob Cross, Systems Programmer, Scottish & Newcastle plc
[we make many fine beers, but lousy disclaimers, an automatically added example 
of the latter follows this text - sorry]

**********************************************************************
The information contained in this message and any attachments:

1. does not constitute an offer or an acceptance of an offer or a
representation or warranty, nor shall it form any part of a legally
binding contract.

2. has been compiled with care but no representation or warranty
(express or implied) is made as to its accuracy or completeness and no
liability can be accepted for any loss arising from the use of any of
the information.

3. may include opinions or views, which unless expressly stated
otherwise, are not those of the company or any person in relation to
whom the company would have vicarious liability or responsibility.

4. is not guaranteed to be free from any so-called computer viruses
and it is strongly recommended that you check for such viruses before
down-loading it to your computer equipment.

5. may include hypertext links to the sites of other companies or
persons, the content of which this company has no control over and
accepts no liability for.

6. is for the exclusive use of the addressee and may contain confidential,
privileged, work product immunity and/or non-disclosable information.
If you are not the intended recipient and receive this message and any
attachments, you must not read, copy, transmit, disclose or otherwise use
any of them (or part of them) in any way (to do so may be unlawful) and
we would be grateful if you could inform us immediately of any such
receipt and subsequently entirely and permanently erase the message and
any attachments from your equipment.

E-mail is an informal method of communication and is subject to
possible data corruption.  For these reasons it will normally be
inappropriate to rely upon information contained in an e-mail without
obtaining tangible written confirmation of it.
**********************************************************************
--Boundary_(ID_xkilHTH8X28sOrQ8dugrjw)--






More information about the SunHELP mailing list