Mailinglist Archive: opensuse (3437 mails)
| < Previous | Next > |
RE: [opensuse] Priority of starting services after reboot on Suse 10 zLinux
- From: "Kamal, Murali" <Murali.Kamal@xxxxxx>
- Date: Tue, 17 Jun 2008 12:08:48 -0400
- Message-id: <23C0CFEF91737340B266E6B1B7F63BBB051DB77F@xxxxxxxxxxxxxxx>
So can I conclude that, there is no way to ensure services start at
custom priority time on SLES 10 using "insserv" or "chkconfig" from
scripts other than writing the symbolic links manually!!
-----Original Message-----
From: Carlos E. R. [mailto:robin.listas@xxxxxxxxxxxxxx]
Sent: Tuesday, June 17, 2008 4:56 AM
To: OS-en
Subject: Re: [opensuse] Priority of starting services after reboot on
Suse 10 zLinux
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Monday 2008-06-16 at 15:26 -0700, John Andersen wrote:
My understanding is that any symlink that is not "properly" managed will
be deleted, or at least, it can be deleted. Maybe they are not deleted
but
overwritten with the new one according to its data. Maybe under some
circumstances they may remain. I don't know.
What I know is that there is no warranty that they are left alone, not
even that they work.
I understand that they are not executed if the start/stop sequence runs
in
parallel mode, but perhaps it is "make" mode. The OP poster found that
out, that was his first problem: his scripts did not execute even though
he
had the correct symlinks.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIVvaTtTMYHG2NR9URAiwiAJ9PwJ9rA+1ZbQoLobDub0Ny+9iYMwCaAlv7
+djkMewSi93UZ3HtKNMTzng=
=M1ad
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
custom priority time on SLES 10 using "insserv" or "chkconfig" from
scripts other than writing the symbolic links manually!!
-----Original Message-----
From: Carlos E. R. [mailto:robin.listas@xxxxxxxxxxxxxx]
Sent: Tuesday, June 17, 2008 4:56 AM
To: OS-en
Subject: Re: [opensuse] Priority of starting services after reboot on
Suse 10 zLinux
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Monday 2008-06-16 at 15:26 -0700, John Andersen wrote:
youYes.
You can build your own links in rc3.d and or rc5.d.
But I wouldn't recommend it.
No, you can't. The next time yast has a look at the services (when
removed.install or remove an rpm with a service) all your symlinks will be
matters isAnd, as a matter of fact, the symlinks are not decisive now, what
thosethe contents of the .depend* files.
It was my understanding that the only symlinks managed by suse are
containing thework.
### BEGIN INIT INFO
### END INIT INFO
Blocks.
And only those depend on .depend. files.
All others (manually created ones) will be left alone and continue to
Are you saying thats wrong?
My understanding is that any symlink that is not "properly" managed will
be deleted, or at least, it can be deleted. Maybe they are not deleted
but
overwritten with the new one according to its data. Maybe under some
circumstances they may remain. I don't know.
What I know is that there is no warranty that they are left alone, not
even that they work.
I understand that they are not executed if the start/stop sequence runs
in
parallel mode, but perhaps it is "make" mode. The OP poster found that
out, that was his first problem: his scripts did not execute even though
he
had the correct symlinks.
- --
Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIVvaTtTMYHG2NR9URAiwiAJ9PwJ9rA+1ZbQoLobDub0Ny+9iYMwCaAlv7
+djkMewSi93UZ3HtKNMTzng=
=M1ad
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |