2014-10-24 14:02 GMT+02:00 Reindl Harald :
> after change clamd to "Type=forking" systemd knows when it's startup has
> finished because it forks after that and the After/Before of the milter
> works relieable
So, it should be fine "Type=forking".
Is anything missing for the package creation?
--
Am 24.10.2014 um 13:54 schrieb Richard Shaw:
On Tue, Oct 21, 2014 at 9:45 AM, Valerio Pachera mailto:siri...@gmail.com>> wrote:
[Service]
EnvironmentFile=/etc/conf.d/
sheep.conf
ExecStart=/usr/sbin/sheep --pidfile /var/run/sheep.pid ${SHEEP_OPTS}
${SHEEP_PATH}
PIDFile=/v
On Tue, Oct 21, 2014 at 9:45 AM, Valerio Pachera wrote:
> [Service]
> EnvironmentFile=/etc/conf.d/
> sheep.conf
> ExecStart=/usr/sbin/sheep --pidfile /var/run/sheep.pid ${SHEEP_OPTS}
> ${SHEEP_PATH}
> PIDFile=/var/run/sheep.pid
> Type=forking
>
Does sheep fork by default? Is there an option to m
2014-10-20 15:04 GMT+02:00 Richard Shaw :
> On a side note, I played around building a package and noticed that only a
> sysvinit file is provided.
Now we have initial systemd support in upstream (master branch).
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/
See, that's easy ! :)
H.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
There's a guy that created a script for he's own purposes.
So, just to have an idea:
[Unit]
Description=Sheepdog QEMU/KVM Block Storage
After=syslog.target
[Service]
EnvironmentFile=/etc/conf.d/
sheep.conf
ExecStart=/usr/sbin/sheep --pidfile /var/run/sheep.pid ${SHEEP_OPTS}
${SHEEP_PATH}
PIDFile=
2014-10-21 8:49 GMT+02:00 Valerio Pachera :
> 2014-10-20 15:04 GMT+02:00 Richard Shaw :
>> On a side note, I played around building a package and noticed that only a
>> sysvinit file is provided. Upstream should develop a systemd service file.
>
> Hi Richard, thank you very much for this note that
2014-10-20 15:04 GMT+02:00 Richard Shaw :
> On a side note, I played around building a package and noticed that only a
> sysvinit file is provided. Upstream should develop a systemd service file.
Hi Richard, thank you very much for this note that I reported in the
developer mailing list.
I'll writ
On a side note, I played around building a package and noticed that only a
sysvinit file is provided. Upstream should develop a systemd service file.
I started working on a minimal one but haven't tested it yet.
[Unit]
Description=Sheepdog distributed storage system
[Service]
ExecStart=/usr/sbin/
2014-10-19 15:57 GMT+02:00 Haïkel :
> Since you're involved upstream, are you committed to subscribe/fix
> bugs that are reported ? collaborate with a packager ?
Sure I can report bugs.
Actually it's the thing I do the most in this project: testing and bug
reporting.
I'm not a developer so I'm not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/19/2014 03:20 PM, Valerio Pachera wrote:
> Hi all,
>
> this may be the wrong list to ask to. If so, please let me know
> which list is more appropriate.
>
> I would like the latest stable version of Sheepdog software to be
> present in fedora
On Sun, Oct 19, 2014 at 8:20 AM, Valerio Pachera wrote:
> Hi all,
>
> this may be the wrong list to ask to.
> If so, please let me know which list is more appropriate.
>
> I would like the latest stable version of Sheepdog software to be
> present in fedora repository.
>
> Sheepdog is a distribut
2014-10-19 15:20 GMT+02:00 Valerio Pachera :
> Hi all,
>
> this may be the wrong list to ask to.
> If so, please let me know which list is more appropriate.
>
Hi,
since sheepdog is already in Fedora Packages Collection, you should
have contacted David (fas: ke4qqq), its maintainer before. You cou
Hi all,
this may be the wrong list to ask to.
If so, please let me know which list is more appropriate.
I would like the latest stable version of Sheepdog software to be
present in fedora repository.
Sheepdog is a distributed object storage system for volume and
container services and manages th
14 matches
Mail list logo
