On Thu, Jun 12, 2014 at 11:36 AM, Jay D Bhatt <jay.bh...@igate.com> wrote: > Hi Mantas, > > I checked the PID by using command 'echo $$' and got reply 1. > > I used command: exec trace -D /sbin/init and took the log, which is attached. > > In the log , I find lot of (Function not implemented),(No such file or > directory) mentions. It seems difficult to figure out which one might be > causing the problem. > > Could you check the log, if you could point out some problem?
The log looks useful this time; it shows that you're missing two kernel options: > name_to_handle_at(0xffffff9c, 0x96444, 0x7eefb7b8, 0x7eefb844, 0x400) = -1 > ENOSYS (Function not implemented) The kernel is missing CONFIG_FHANDLE=y. Your systemd version seems to work without it, but in recent releases it is now required. > mount("devtmpfs", "/dev", "devtmpfs", MS_NOSUID|MS_STRICTATIME, "mode=755") = > -1 ENODEV (No such device) The kernel is missing CONFIG_DEVTMPFS=y, which is now required. > access("/proc/vz", F_OK) = -1 ENOENT (No such file or > directory) systemd is trying to detect some container mechanisms; ENOENT is expected on bare hardware. > mount("securityfs", "/sys/kernel/security", "securityfs", > MS_NOSUID|MS_NODEV|MS_NOEXEC, NULL) = -1 ENOENT (No such file or directory) > mount("smackfs", "/sys/fs/smackfs", "smackfs", > MS_NOSUID|MS_NODEV|MS_NOEXEC|MS_STRICTATIME, "smackfsdef=*") = -1 ENOENT (No > such file or directory) > stat64("/etc/ima/ima-policy", 0x7eefb958) = -1 ENOENT (No such file or > directory) > open("/sys/fs/smackfs/load2", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE|O_CLOEXEC, > 0666) = -1 ENOENT (No such file or directory) systemd is checking if it should load SMACK or IMA policy; this can be safely ignored if you don't use these security modules. -- Mantas Mikulėnas <graw...@gmail.com> _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel