Modify

#1279 new enhancement

Please make it possible to change UNIX socket path at runtime with run option

Reported by: anonymous Owned by:
Priority: normal Milestone:
Component: Unspecified / other Version: Unspecified
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro:

Description

I would like to run bitlbee in normal user without the need for root to keep all of its settings and data in the user dir. The only thing that prevents that is bitlbee tries to write UNIX socket in /run/bitlbee and it's not possible to change the path without recompiling and hard set the path at configure time. Can we please have an option for specifying alternative UNIX socket path at run time?

Attachments (0)

Change History (1)

comment:1 Changed at 2017-01-20T08:36:34Z by wilmer

Note that that socket is not essential so failure to create it doesn't break anything, it only emits a warning.

(Also that functionality was never used much. If at all. :-/)

Modify Ticket

Action
as new The ticket will remain with no owner.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.