Very Computer

by **Alexandre Sidoren** » Sat, 13 Jul 1996 04:00:00

I have found that on recent kernels (>2.0.1 at least) 'crond' is not running
after startup. I.e. if I start it manually from the shell, everything's OK,
but when it is started from /etc/rc.d/rc.multi it starts and then dies (I
can see that when turning on debugging). At least one more program behaves
in the same way, 'gpm'. Everything's fine with 1.3.100 (it seems that this
problem has appeared near 2.0.0). I have no other problems - the system is
quite stable.

I use libc-5.3.12 and sysvinit-2.63

Has somebody else observed this behaviour ?

----------------------------------------
Alexandre Sidorenko

http://caprice.physik.unizh.ch/~sidorenk
----------------------------------------

by **Ian T Zimmerm** » Mon, 15 Jul 1996 04:00:00

> I have found that on recent kernels (>2.0.1 at least) 'crond' is
> not running after startup. I.e. if I start it manually from the
> shell, everything's OK, but when it is started from
> /etc/rc.d/rc.multi it starts and then dies (I can see that when
> turning on debugging). At least one more program behaves in the same
> way, 'gpm'. Everything's fine with 1.3.100 (it seems that this
> problem has appeared near 2.0.0). I have no other problems - the
> system is quite stable. I use libc-5.3.12 and sysvinit-2.63 Has
> somebody else observed this behaviour ?

I run kernel 2.0.0, libc 5.2.18, sysvinit 2.62, no problems whatsoever
with either cron (Vixie's cron) or gpm.

Another suspect may be sysk?logd. I still use 1.2, I think there's a
newer one out there now, maybe you use it?

--
Ian T Zimmerman +-------------------------------------------+
Box 13445 I When the dead are left to bury the dead, I
Berkeley CA 94712 USA I the living remain alone. Arthur Koestler I

by **Maiz** » Fri, 19 Jul 1996 04:00:00

>>> I have found that on recent kernels (>2.0.1 at least) 'crond' is
>>> not running after startup. I.e. if I start it manually from the
>>> shell, everything's OK, but when it is started from
>>> /etc/rc.d/rc.multi it starts and then dies (I can see that when
>>> turning on debugging). At least one more program behaves in the same
>>> way, 'gpm'. Everything's fine with 1.3.100 (it seems that this
>>> problem has appeared near 2.0.0). I have no other problems - the
>>> system is quite stable. I use libc-5.3.12 and sysvinit-2.63 Has
>>> somebody else observed this behaviour ?

>>I run kernel 2.0.0, libc 5.2.18, sysvinit 2.62, no problems whatsoever
>>with either cron (Vixie's cron) or gpm.

>>Another suspect may be sysk?logd. I still use 1.2, I think there's a
>>newer one out there now, maybe you use it?

I just installed 2.0.6 last weekend and noticed that the lpd daemon also dies
during startup, similar to the crond problem described above. I must admit that
I haven't paid much attention to my system as of lately since I have not
attempted to debug the problem. But, if somebody knows the reason for this
could they post it or mail it to me so I can post it.

I was running 1.3.77 before upgrading to 2.0.6 and the lpd daemon started with
no problems.
--

Maizo

by **Alexandre Sidoren** » Fri, 19 Jul 1996 04:00:00

>> I have found that on recent kernels (>2.0.1 at least) 'crond' is
>> not running after startup. I.e. if I start it manually from the
>> shell, everything's OK, but when it is started from
>> /etc/rc.d/rc.multi it starts and then dies (I can see that when
>> turning on debugging). At least one more program behaves in the same
>> way, 'gpm'. Everything's fine with 1.3.100 (it seems that this
>> problem has appeared near 2.0.0). I have no other problems - the
>> system is quite stable. I use libc-5.3.12 and sysvinit-2.63 Has
>> somebody else observed this behaviour ?

>I run kernel 2.0.0, libc 5.2.18, sysvinit 2.62, no problems whatsoever
>with either cron (Vixie's cron) or gpm.

>Another suspect may be sysk?logd. I still use 1.2, I think there's a
>newer one out there now, maybe you use it?

I have found another 2 interesting facts:
1. Vixie's cron does not have these problems for me too, Dillon's one has !
2. After I have added to my rc.local commands for UMSDOS synchronization,
GPM (which is started few lines above in the script) dies no more !

Probably it's somehow related to increased delay between GPM start and some
other process, as nothing has changed save order of starting various
daemons. Any ideas ?

-----------------------------------
Alexandre Sidorenko

http://caprice.physik.unizh.ch/~sidorenk
----------------------------------------

Very Computer

crond dies while startup

crond dies while startup

crond dies while startup

crond dies while startup

crond dies while startup