Thank you for the quick response, Ciro. I tried with QEMU and the same problem exists. The script is being killed when the login service is started.
I will try and ask in the appropriate community. Thanks, Swamy. On Fri, Apr 3, 2020 at 6:54 PM Ciro Santilli <ciro.santi...@gmail.com> wrote: > I would suggest that you try to run it on QEMU as well where things > will go much faster and to try and that will potentially decide if it > is a gem5 bug or not if it woks on QEMU. > > Then if it does not work on QEMU either, try extracting the init > problem from gem5 and asking on a community that might know more about > it. > > On Fri, Apr 3, 2020 at 12:01 PM swamy saranam > <raj.rockinggu...@gmail.com> wrote: > > > > Hi, > > > > I am trying to start cassandra server at the bootup phase using > systemd.service. I used the gem5.service to start this script. The script > is starting but it is getting killed at the login phase. > > > > But when I run the same script after login, it is working perfectly > fine. I tried changing the type of the service from idle to oneshot and > added the "Before=" condition in [Unit] section of gem5.service. Even then > the service is killed with the following error: > > > > Process: 496 ExecStart=/sbin/gem5init_web_serving (code=killed, > signal=HUP) > > Jan 28 10:58:27 ubuntu systemd[1]: gem5.service: Main process exited, > code=killed > > Jan 28 10:58:27 ubuntu systemd[1]: gem5.service: Failed with result > 'signal' > > > > Can anyone help me out with this issue. > > > > Thanks, > > Swamy. > > _______________________________________________ > > gem5-users mailing list > > gem5-users@gem5.org > > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users > -- -- *S R Swamy Saranam* CS14D403 Research Scholar Dept of Computer Science and Engineering IIT Madras Chennai, Tamilnadu-600036
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
