|
a/debian/upmpdcli.init |
|
b/debian/upmpdcli.init |
| 1 |
#!/bin/sh
|
1 |
#!/bin/sh
|
| 2 |
### BEGIN INIT INFO
|
2 |
### BEGIN INIT INFO
|
| 3 |
# Provides: upmpdcli
|
3 |
# Provides: upmpdcli
|
| 4 |
# Required-Start: $network $local_fs $remote_fs
|
4 |
# Required-Start: $network $local_fs $remote_fs mpd
|
| 5 |
# Required-Stop: $remote_fs
|
5 |
# Required-Stop: $remote_fs
|
| 6 |
# Default-Start: 2 3 4 5
|
6 |
# Default-Start: 2 3 4 5
|
| 7 |
# Default-Stop: 0 1 6
|
7 |
# Default-Stop: 0 1 6
|
| 8 |
# Short-Description: UPnP Renderer front-end to MPD
|
8 |
# Short-Description: UPnP Renderer front-end to MPD
|
| 9 |
# Description: upmpdcli is as an UPnP Media Renderer front-end
|
9 |
# Description: upmpdcli is as an UPnP Media Renderer front-end
|
| 10 |
# to MPD, and enables you to control it with any UPnP controller
|
10 |
# to MPD, and enables you to control it with any UPnP controller
|
| 11 |
# running, for example, on an Android tablet. It uses the MPD
|
11 |
# running, for example, on an Android tablet. It uses the MPD
|
| 12 |
# instance to actually play the tracks. A typical configuration
|
12 |
# instance to actually play the tracks. A typical configuration
|
| 13 |
# might have for example, MPD running on a Raspberry PI, with
|
13 |
# would have for example, MPD running on a Raspberry PI, with
|
| 14 |
# upmpdcli on the same host or any other Linux PC on the network.
|
14 |
# upmpdcli on the same host or any other Linux PC on the network.
|
| 15 |
### END INIT INFO
|
15 |
### END INIT INFO
|
| 16 |
|
16 |
|
| 17 |
# Author: Jean-Francois Dockes <jf@dockes.org>
|
17 |
# Author: Jean-Francois Dockes <jf@dockes.org>
|
| 18 |
|
18 |
|