Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
W_Prindl Absent Member.
Absent Member.
1405 views

Is there another way of dealing with startup order and dependencies from other services than manually editing the startup scripts in /etc/init.d ?

My problem is the following: there are several dependencies of services
from each other which are not optimally implemented, so that after
bootup of a server several services have to be started manually,
because their initial start failed because of other services not being
up.

Here a few examples:
dhcpd on OES2 needs ndsd to be up and accessible - so if I start the
server running dhcpd as first server in the tree it fails, because it
does not wait till ndsd is up;
xad or DSfW - needs always an reload after bootup because of namcd /
ndsd interdependency problems (here it is up but users have wrong
access rights via samba) - and because name resolution needs
novell-named to be up (there is no hosts-file workaround as you cannot
enter anything into /etc/hosts without breaking the config);

novell-ipsmd: needs ndsd and if running on an DSfW server novell-named,
too.

The dhcpd problem is the worst, because you need to have console-access
to correct that as all your workstations do not get any IP-addresses.


......


--
W. Prindl

W. Prindl
Labels (2)
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Is there another way of dealing with startup order and dependencies from other services than manually editing the startup scripts in /etc/init.d ?

No, there isn't. If you don't change the /etc/init.d scripts, then you don't
have persistence -- for example, renaming the symbolic link in
/etc/init.d/rcX.d will be changed next time chkconfig is run.

The NDSD process normally has a default start of 2 3 4 5, meaning that it
should start before everything else in run level three or five.

Whats the output of "chkconfig ndsd"?

0 Likes
W_Prindl Absent Member.
Absent Member.

Re: Is there another way of dealing with startup order and dependencies from other services than manually editing the startup scripts in /etc/init.d ?

Yes, I feared that. And the persistence is probably only valid till the
next update of the daemon code.

chkconfig ndsd shows "ndsd on", and "namcd on", too, so those are using
the default settings.

And dhcpd, namcd and novell-ipsmd are started with K08 whereas ndsd is
started with K09.

Probably best to create a K99 script for runlevels 3 and 5 which starts
those services after some sleeping time ?

--
W. Prindl


utlemming wrote:

>No, there isn't. If you don't change the /etc/init.d scripts, then
>you don't have persistence -- for example, renaming the symbolic link
>in /etc/init.d/rcX.d will be changed next time chkconfig is run.
>
>The NDSD process normally has a default start of 2 3 4 5, meaning
>that it should start before everything else in run level three or
>five.
>
>Whats the output of "chkconfig ndsd"?


W. Prindl
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.