On 2015/10/24 14:54, Petter Reinholdtsen wrote: > [Rui Xiang] >> Hi，list > > Hi. > >> It seems that reboot or force reboot through *sysvinit* have the problem. >> Furthermore, using reboot -f in *systemd* should also have this >> problem, right? >> >> And is that a bug for current reboot process in sysvinit or systemd? >> >> All comments are welcome, thanks. > > I must admit, that the only scenario I can think of that would cause > SysV init to die like this is running out of memory very early in the > startup of the process. >
Hi Petter, You mean init will be killed at boot time when there is no memory, right? However, we sure the memory is enough at boot time. But apps maybe use a lot of memory after boot, then reboot, and catch the error. Thanks, Xishi Qiu > Are you sure the kernel isn't running out of memory? Perhaps you can > try using valgrind to figure out why init exits? > > I'm trimming the list of receivers to the sysvinit mailing list, to > avoid flodding too many people. >
