522742 – net-im/ejabberd-2.1.13-r1 and lower does not creates own directory in /var/run

Bug 522742 - net-im/ejabberd-2.1.13-r1 and lower does not creates own directory in /var/run

Summary: net-im/ejabberd-2.1.13-r1 and lower does not creates own directory in /var/run

Status:	RESOLVED OBSOLETE

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Server (show other bugs)
Hardware:	All Linux

Importance:	Normal critical (vote)
Assignee:	Amadeusz Żołnowski (RETIRED)

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2014-09-13 17:20 UTC by Alexey Skobkin
Modified:	2016-08-21 10:52 UTC (History)
CC List:	4 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexey Skobkin 2014-09-13 17:20:58 UTC

Default /etc/jabber/ejabberdctl.cfg has
EJABBERD_PID_PATH=/var/run/ejabberd/ejabberd.pid

but /etc/init.d/ejabberd does not creates /var/run/ejabberd directory and ejabberd fails to start after reboot.

Reproducible: Always

Steps to Reproduce:
1.Reboot
2. Check ejabberd status
Actual Results:  
Ejabberd does not start correctly.

Expected Results:  
Ejabberd must start correctly :)

Comment 1 Martin Väth 2014-09-14 09:32:21 UTC

Just as a reminder (without having checked whether this applies to ejabberd):

Using /usr/lib/tmpfiles.d instead of "manual" generation in /etc/init.d
is usually simpler and provides compatibility with other init systems…

Comment 2 Amadeusz Żołnowski (RETIRED) gentoo-dev

2016-08-21 10:52:48 UTC

ejabberd-2.1 has been removed from the tree (see bug 539040). Please open a new bug if it occurs in >=ejabberd-16.