ben <[EMAIL PROTECTED]> writes: > > Thanks. But would that explanation be compatible with the fact that my > > system most of the time functions all-right and then suddenly for some > > time (one day and then a few minutes) not? If libc.so.6 wasn't > > backwards compatible I would expect that the problem would arise all > > the time. And why should the great majority of programs, in a more or > > less up to date woody system, depend on glibc5 or glibc4? > > > > given that the disfunction is only occasional, it would seem that some app > that runs only occasionally provokes the dependency issue. got anything set > up in cron that might be doing this?
I was thinking of that. But to my uneducated eye entries in cron.d, cron.daily, cron weekly and cron.monthly looked rather inoffensive. Or is there something in the following lists which could be the offender? Is there some other "source" of cron jobs? (anacrontab and crontab only start the jobs in these directories.) cron.daily: 0anacron, 5snort, apache, calendar, cfengine, dwww, exim, find, logrotate, man-db, mgetty, modutils, netbase, netkit-inetd, standard, sysklogd, tetex-bin, tripwire-1.2 cron.d: anacron, exim, logcheck, postgresql, shaper, tiger cron.weekly: 0anacron, apt-move, cfengine, cfingerd, cvs, dpkg-mountable, efax, htdig, lpr, man2html, man-db, sysklogd cron.monthly: 0anacron, rwhod, standard Andreas Goesele
