Get a list of services and levels with rc-update -s
then del and re-add each service to recreate the links.
i.e., each service that should be started has a link in /etc/runlevels/*
Also, try running depscan.sh -u but I think this is done on startup
anyway.
BillK
On Sat, 2007-12-08 at 12:42 +0
Marzan, Richard non Unisys schrieb:
> This might or might not be an issue related to your kernel
> configuration. There is an option in the kernel to allow IA32
> executables to run under the AMD64 platform. I don't know the particular
> name of this option in the .config file but, nonetheless, it
Randy Barlow schrieb:
> Stefan G. Weichinger wrote:
>> looks fine but doesn't start at next boot. Or more exactly: It seems to
>> get started, but doesn't run then.
>
> Does this only happen at boot, or does it also happen if you manually
> call /etc/init.d/sshd start?
Only at boot, I can start i
> -Original Message-
> From: Stefan G. Weichinger [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 07, 2007 1:21 AM
> To: gentoo-user@lists.gentoo.org
> Subject: [gentoo-user] services not starting since move to amd64
>
>
> Greets, gentoo-users,
>
> a
Stefan G. Weichinger wrote:
> looks fine but doesn't start at next boot. Or more exactly: It seems to
> get started, but doesn't run then.
Does this only happen at boot, or does it also happen if you manually
call /etc/init.d/sshd start?
--
Randy Barlow
http://electronsweatshop.com
--
[EMAIL PR
Greets, gentoo-users,
as soem of you might remember I only recently migrated my system to
amd64 (fresh install).
I don't exactly know if there is a relation to this move but since then
I have the problem that some services simply don't start when the system
boots.
For example xinetd, sshd and s
6 matches
Mail list logo
