Starting Syslog Services Failed.

Hello
to learn using Suse I have installed a copy of version 8.2 (had it on disk handy) upon an old IBM computer with a 233 processor and 80 M of ram.
Although it boots up fine and will go into the desktop,with most software and tools appearing there I have a minor glitch.

When the system is loading and the black screen appears with the details of what is loading one item lists as Failing.

Starting Syslog services Failed !

I am new to linux and wonder if someone could point me in the right direction for what to check and or correct for this service to run. What does this service do.

The machine is a bit long winded in opening some items and internet access is a bit clunky I tried with Konquerer within a KDE desktop. But all in I felt quiet good considering the set up.

Thanks

SFB.

What happens if you try to start the syslog service manually from a root CLI?

Not sure that I would use it for too long if I were you, you'd miss all the modern apps and there would be security issues with web browsers, etc. If you can't find a computer with more grunt and memory, then try one of the light distros, like Puppy Linux, DSL, AntiX, etc.

What happens if you try to start the syslog service manually from a root CLI?

Not sure that I would use it for too long if I were you, you'd miss all the modern apps and there would be security issues with web browsers, etc. If you can't find a computer with more grunt and memory, then try one of the light distros, like Puppy Linux, DSL, AntiX, etc.
[/b]

Hello Ken

Thanks for the reply. I am not too certain what the piece actually does! How would I write to do this and open from root to the interface.

The system has KDE loading after the root pass word is added. Should I have this service turned on at the loading of the system.

Thanks

SFB.

Get a terminal shell, either from KDE or from the console Alt-F1 for example. Become root with su, if not root already.

/etc/init.d/syslog status

and see what it says, then

/etc/init.d/syslog start

and report all the output.

Get a terminal shell, either from KDE or from the console Alt-F1 for example. Become root with su, if not root already.

/etc/init.d/syslog status

and see what it says, then

/etc/init.d/syslog start

and report all the output.
[/b]

Hello Ken

thank you for the reply I apologise for the delay in getting back to you but the usual got in the way.
Fired up the system as you said, after typing,
/etc/init.d/syslog status

I got

Checking for service syslog: running

Then the second line of type
/etc/init.d/syslog start

I got

Re-Starting syslog services done
linux:~#

Am I right to assume it will only start if I go into this panel or one of the 6 others that are offered that I can interrogate the system!
I checked the Suse administrators manual but it only has four set sentences and I am not that far into using Linux for that yet, should I get another book or manual do you think!
The screen has a red back ground and a yellow triangle with exclamation mark and an old style bomb with a fuse. Does this suggest that something is wrong with the setup or is it just a desktop back ground.

Thank you again Ken

SFB.

Strange it thinks it's both running and not running (since it can be started). Do:

ps ax | grep syslog

to see what the deal is.

The bomb background to remind you that you should normally not use root to login to do work, only for administration.

Strange it thinks it's both running and not running (since it can be started). Do:

ps ax | grep syslog

to see what the deal is.

The bomb background to remind you that you should normally not use root to login to do work, only for administration.
[/b]

Hello Ken

could not figure out how to get a vertical there for a few minutes, Alt Gr + top left key on my keyboard.

The read out is

1099? S 0:00 /sbin/syslog
1770 pts/1 S 0:00 grep syslog

Not sure were to look to find the meaning of those.

SFB.

Ok, it's running. Don't know why you got a false alarm that it wasn't. You should also see entries being added in /var/log/messages now and then.

But you still have the problem that you are running an old, unsupported version without all the modern software everybody else is talking about in forums. You really need to think about getting a computer with more grunt and memory, or installing a more recent distro, one that is light on memory footprint.

Ok, it's running. Don't know why you got a false alarm that it wasn't. You should also see entries being added in /var/log/messages now and then.

But you still have the problem that you are running an old, unsupported version without all the modern software everybody else is talking about in forums. You really need to think about getting a computer with more grunt and memory, or installing a more recent distro, one that is light on memory footprint.
[/b]

Hello Ken

Thank you I will check out the above log and see if anything looks out of place. I will lok at a later distribution it was just I had the boxed set for this one. I am looking at building another computer from new parts, just liked the old IBM. The distributions sounds good with Puppy and DSL. Also heard that there is one called Feather that may be worth a look also.

Good job I did not try with an old IBM server I have it is a P90 with 32MB of Ram. :blink:
It has NT workstation on that and a SCSI hot rack with adaptec software. Shame but I have no discs for that apart from the NT. The things we keep I suppose.

Thanks again.

SFB.