I upgraded systemd to version 44 on my exherbo system and ever since Systemd
fails at boot time.
I've upgraded/reinstalled all the packages that install files to
/etc/system/systemd and /lib/systemd and the directory /lib/systemd doesn't
exist anymore. I've also checked for links under /etc/sy
'Twas brillig, and Mark Hounschell at 05/04/12 18:26 did gyre and gimble:
> I'm not a systemd developer but I am trying to use it in place of
> sysvinit to create a dedicated "run-level" for our application. Is this
> list an appropriate place to inquire about problems I have?
Yup, ask questions h
I'm not a systemd developer but I am trying to use it in place of
sysvinit to create a dedicated "run-level" for our application. Is this
list an appropriate place to inquire about problems I have?
Thanks in advance
Mark
___
systemd-devel mailing list
On 04/05/2012 11:13 AM, Colin Guthrie wrote:
Can't answer this specific part, but I guess a longer term solution
(that is much more intrusive and arguably one you don't necessarily want
to support) is to split out the different services that dovecot offers
into separate systemd units, each of whi
'Twas brillig, and Michal Hlavinka at 05/04/12 11:26 did gyre and gimble:
> On 03/17/2012 02:19 AM, Lennart Poettering wrote:
>> On Fri, 16.03.12 15:55, Michal Hlavinka ([email protected]) wrote:
>>
> For example, lets have dovecot configured to listen for imap(s) and
> lets
> have sy
On 03/17/2012 02:19 AM, Lennart Poettering wrote:
On Fri, 16.03.12 15:55, Michal Hlavinka ([email protected]) wrote:
For example, lets have dovecot configured to listen for imap(s) and lets
have systemd dovecot socket configured to listen for all protocols -
pop3(s) and imap(s). When dovecot
