In that case, your syslog probably overfilled the partition and the
machine can't figure out what to do with the overflowing log files (as
logrotate must be run through the crontab entry)
Michael Havens wrote:
> I don't run cron jobs.
>
> On Thursday 23 October 2003 09:54 am, Bart Garst said:
> ~ My suggestion is to look at what cron jobs may have been running at the
> ~ time you tried to start kspread.
> ~
> ~ I know some crone jobs on my machine slow it down just like you
> ~ described.
> ~
> ~ Use 'man 5 crontab' to learn how to read '/etc/crontab' and try to match
> ~ the times.
> ~
> ~ Bart
> ~
> ~
> ~
> ~ On Thu, 2003-10-23 at 09:16, Michael Havens wrote:
> ~ > I was told that I should keep my computer running all the time (or at
> least ~ > that linux was designed/could do that; so yesterday I turned it on
> and went ~ > to school for the day. When I got home the machine was still
> going (which ~ > was a good sign) but when I loaded a program it took three
> times as long. ~ > (for instance: I loaded kspread <which takes 10 seconds
> normally> and it took ~ > like 30)
> ~ >
> ~ > Any idea as to what the problem is?
> ~ > --
> ~ > <:-)~MIKE~(-:>
> ~ >
> ~ > ---------------------------------------------------
> ~ > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> ~ > To subscribe, unsubscribe, or to change you mail settings:
> ~ > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ~
> ~
> ~ ---------------------------------------------------
> ~ PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
> ~ To subscribe, unsubscribe, or to change you mail settings:
> ~ http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
> ~
>
(text/plain)