Mailinglist Archive: opensuse-bugs (4724 mails)

< Previous Next >
[Bug 594223] priorititize sshd on boot
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 9 Apr 2010 11:13:53 +0000
  • Message-id: <20100409111353.A4D83245520@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=594223

http://bugzilla.novell.com/show_bug.cgi?id=594223#c6


--- Comment #6 from Dr. Werner Fink <werner@xxxxxxxxxx> 2010-04-09 11:13:52 UTC
---
How well does that even integrate with rpm? Updating a client would mean
either
attempting to write to a read-only /usr, or overwriting the files in /usr,
thereby possibly making another client's or the server's rpm database
inconsistent with what's on-disk.

You can not maintaine such a cluster on a system based scheme, for such
setups you need to share any other partitions. After an update the local
configuration for the clients have to be distributed. Maybe with other
NFS distributed partitions for every client or with the help of rsync
and a script updating the clients local configuration. For the first case
on the servers side the mount option --bind and --rbind are very useful.

Btw: you way $network -> $networkplus introduce a loop as sshd
requires not only /usr but also plain network.

For a fix the line

# X-Start-Before: +clamd +irq_balancer

should be enough.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
References