Mailinglist Archive: opensuse-security (394 mails)

< Previous Next >
Re: [suse-security] Some services fail when rebooting after kernel update
  • From: Olaf Kirch <okir@xxxxxxx>
  • Date: Mon, 8 Dec 2003 09:55:15 +0100
  • Message-id: <20031208085515.GB7023@xxxxxxx>
Hi,

> <notice>/etc/init.d/rc5.d/S10sshd start
> Starting SSH daemon
> failed
> <notice>startproc: execve (/usr/sbin/sshd) [ /usr/sbin/sshd ], [
> PWD=/ HOSTNAME=lux CONSOLE=/dev/console PREVLEVEL=N AUTOBOOT=YES
> REDIRECT=/dev/tty1 MACHTYPE=i386-suse-linux LINES=34 SHLVL=2
> COLUMNS=105 BOOT_IMAGE=linux SHELL=/bin/bash HOSTTYPE=i386
> OSTYPE=linux HOME=/ TERM=linux PATH=/sbin:/bin:/usr/sbin:/usr/bin
> RUNLEVEL=5 INIT_VERSION=sysvinit-2.82 _=/sbin/startproc
> DAEMON=/usr/sbin/sshd ]
> <notice>'/etc/init.d/rc5.d/S10sshd start' exits with status 7

This looks like startproc exits with status code 7. (There is no
exit(7) in the openssh shource code anywhere). Exit code 7 from
startproc means "program is not running". This sounds a little
weird. Does sshd run despite this error?
What does sshd say if you try to run it manually using
"sshd -Ddd"?

> 2) Alsa sound daemon
[..]
> and assume that the appropriate module should be called
>
> snd-card-intel8x0
>
> instead of snd-intel8x0, which no longer exists.

I'll try to find out why that module was renamed, because all
our other kernels seem to use snd-intel8x0.o

> Could I just create a link to solve this?

You could, but I think the better approach is to edit
/etc/modules.conf and change the "alias snd-card-0" line:

alias snd-card-0 snd-card-intel8x0

Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@xxxxxxx | tempfile names today!
---------------+

< Previous Next >
Follow Ups
References