Suse Syslog-ng help?

[tomii]

Hi..I have a mininal Suse install as I just want to use syslog-ng only. Once installed I can't see to start or stop syslog-ng? where are these located? in /etc/init.d/ there is only reference to the old syslog.

I have also tried to reinstall syslog-ng from src but when doing a 'make' i get the error:

make: *** No targets specified and no makefile found. stop

Whats going wrong?

Thanks!!

 

[mrballcb]

To build from source, the normal series of steps is:

./configure
make
su
make install

A minor issue with compiling from source is that source is normally configured to be installed and run from /usr/local, so your config file will be /usr/local/etc/syslog-ng/syslog-ng.conf. You'll also have to create an init file, which one frequently is provided in the source, such as inside a contrib/ directory. If you put it in the /etc/init.d/ directory, you'll probably have to

chown +x /etc/init.d/syslog-ng

That will make it executable.

If I may be so bold, what is wrong with regular syslog that you want to use syslog-ng? I use both and find that it's typically a bit easier to use the distribution supplied logger, but as usual, this is linux and we build rope (a point to you if you can tell me who that's attributed to ;-).

 

[lgarner]

You could also search for an RPM package at pbone.net, or on the web. I think Suse's come toward RedHat in overall configuration enough that an RH rpm will work, or you can compile the .src.rpm.

 

[IRudebwoy]

I'm running SuSE 10.0 which installs syslog-ng by default. Vanilla syslog is still available but you have to select it to install it. The klogd package owns /etc/init.d/syslog.

If you running SLES9 or earlier you have to select syslog-ng because vanilla syslog is installed by default.

Lorenzo Wacondo (System Administrator)

http://www.laguna-industries.com

## Just because you can do something doesn't mean you should.

 

[tomii]

Hi..Thanks all for your help , I finally got syslog-ng working and logging remotely from another linux client...however, another question/problem I noticed is the it seem to lost it connection when the syslog-ng service is restarted either on the client or syslog server, they are using both tcp though I think its the same with udp? I have to manually restart on the other machine for it to establish connection again, why is that??
Cheers!

 

[mrballcb]

Don't use restart, instead use reload. Reload makes it reread the config file, reopen all log files, and leaves all existing logging connections established.