On 04/05/2011 04:08 PM, Severin Gehwolf wrote:
On Tue, 2011-04-05 at 22:03 +0200, Michał Piotrowski wrote:
W dniu 5 kwietnia 2011 21:49 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
W dniu 5 kwietnia 2011 21:48 użytkownik Michał Piotrowski
<mkkp4x4@gmail.com> napisał:
Try to add some informations about ordering to ypbind script

### BEGIN INIT INFO
# Provides: ypbind
# Required-Start: $local_fs $remote_fs $network
# Required-Stop: $local_fs $remote_fs $network
# Short-Description: Starts the ypbind daemon
# Description: The Apache HTTP Server is an extensible server
Without apache part :)

### END INIT INFO

or better - rewrite this POS
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind to
native systemd service
I am afraid that none of these scripts
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypbind
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/yppasswdd
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypserv
http://notendur.hi.is/~johannbg/systemd/etc/rc.d/init.d/ypxfrd
does have the correct ordering information.

I can help with rewriting to native sysetmd services, but I need a
tester - I do not use this service, so I'm not sure if I can correctly
configure and test.
Is there documentation somewhere as to how to write a native systemd
service? Thanks!

--Severin

I thought that was the "GREAT" thing about systemd - it would work with all the existing init scripts!

Sounds like it falls short.


--
Stephen Clark
NetWolves
Sr. Software Engineer III
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark@netwolves.com
http://www.netwolves.com