To make finer adjustments, system administrator must edit or create unit files manually.Table 10.2, “Systemd Unit Files Locations” lists three main directories where unit files are stored on the system, the [email protected]:/etc# /etc/init.d/syslog stop Stopping syslogd/klogd: stopped syslogd (pid 1551). done [email protected]:/etc# /etc/init.d/syslog start Starting syslogd/klogd: done [email protected]:/etc#The parameters to pass to the update-rc.d call during installation.Typically this will be the work default followed by either single number or a pair of numbers representing the start/stop sequence number (both are set to the same if only one number is supplied.)The start and stop sequence numbers need to ensure that the the service is started at the appropriate time relative to other services, such as waiting for any service that it depends on before starting (networking for example).This is done by creating copies of the original service configuration files and modifying certain parameters to avoid conflicts with the primary instance of the service.The following procedure shows how to create a second instance of the Additional information with some real-world examples of cases triggered by the ordering and dependencies in a unit file is available in the following article: Is there any useful information about writing unit files?
Once done, the script will show in Ya ST In SUSE it isn't done that way.
On the other hand, if you intend just to modify or extend the behavior of an existing unit, use the instructions from Section 10.6.4, “Modifying Existing Unit Files”.
The following procedure describes the general process of creating a custom service: text editor, it is often faster and more convenient to have it running in the background instead of starting a new instance of the program whenever editing a file.
Of course, non-power users would use Ya ST, which calls chkconfig, to manage the services.
Can't remember seeing this last line in debian: If "script" is the name of a real init script, what does it do?