Summary: | depcache broken | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Justin <gentoo-bugs> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | depcache |
Description
Justin
2004-09-27 01:36:49 UTC
Created attachment 41126 [details]
depcache
Updated error:
(also I made a mistake since then when adding my own init script for apache-
thus the error there)
# /sbin/depscan.sh
* Caching service dependencies...
/var/lib/init.d/depcache: line 2002: syntax error: unexpected end of file
* Cannot add provide 'apache', as a service with the same name exists!
* Can't find service 'modules' needed by 'crypto-loop'; continuing...
* Can't find service 'hostname' needed by 'domainname'; continuing...
* Can't find service 'logger' needed by 'exim'; continuing...
* Can't find service 'hostname' needed by 'fcron'; continuing...
* Can't find service 'localmount' needed by 'gpm'; continuing...
* Can't find service 'localmount' needed by 'numlock'; continuing...
* Can't find service 'localmount' needed by 'alsasound'; continuing...
* Can't find service 'logger' needed by 'apache'; continuing...
* Can't find service 'localmount' needed by 'bootmisc'; continuing...
* Can't find service 'hostname' needed by 'bootmisc'; continuing...
* Can't find service 'modules' needed by 'checkfs'; continuing...
* Can't find service 'localmount' needed by 'clock'; continuing...
* Can't find service 'localmount' needed by 'consolefont'; continuing...
chances are it's because you have a mistake in one of the init.d scripts or a config file try running it through `strace -f -eopen -o out` and verify that all the files it reads are correct (no syntax errors) one way you could test this is (you should get no errors): $ bash $ source /etc/init.d/* $ get back to us Ooops - yes, all apologies. Someone in the hardened channel on freenode took a look for me, and despite my protests- it seems that somewhere in one of the upgrades one of the init scripts got borked. I fixed that, and naturally the problem went away. Thanks. |