= Client Init Scripts =

== openSUSE ==

up until openSUSE 11.1 SysV-Init is used.

Start script in {{{/etc/init.d/}}}

=== openSUSE 11.1 NetworkManager ===

in openSUSE 11.1 NetworkManager is default. Before is had been NetControl with commands like {{{ifup eth0}}}

The ordering in somehow strange:

{{{/etc/init.d/}}}
 1. $localfs: boot.localfs
 1. network (parameter localfs) 
 1. $remotefs: $local_fs +nfs +smbfs
 1. network-remotefs -> call network with parameter remotefs)
 1. network (parameter remotefs)

I don't see, how this can work.
nfs and smbfs can not be munted, before network connection is established.

We run into problems, with our init script, that expect network connection to be established.

We rely on {{{waitfornm}}} (wait for NetworkManager), but this is broken,
because it is started at the same time as network-remotefs.
So it worked only half of the times.

==== Workaround ====
add 
{{{
Should-Start: network-remotefs
}}}
to {{{waitfornm}}}

==== SmartClint Init-Script ====

The first SmartClient Init script that requires network connectivity is {{{sc_mkwsconfig}}}

All other SmartClient Init scripts should include the line:
{{{
Should-Start: sc_mkwsconfig
}}}

By using this mechanismus, we only have to adapt {{{sc_mkwsconfig}}} in following versions.