Comment # 23 on bug 965564 from Franck Bui

(In reply to Dominique Leuenberger from comment #22)
> (In reply to Dr. Werner Fink from comment #21)
> > (In reply to Dominique Leuenberger from comment #18)
> > 
> > > So in this case any remainings of systemd's limits is just confusing, as
> > > systemd is not pid1
> > 
> > The design of systemd and any other init program is that it has pid 1. 
> > Otherwise it can not wipe out any zombi of a died daemon process.
> 
> right.. and the init program in the build bot is called /.build/build - NOT
> systemd. Systemd just wrongly survives as being spawned out of initrd
> already and setting up limits which are not on the actual system. THAT's the
> issue and that's what we claim systemd should cleanup
> 

Then don't use systemd at all.

PID1 is not supposed to be started and replaced by another init system later.

Also I would suggest to teach your init system to do some basic initialisations
when starting instead of totally relying on an undefined state.