yes it was as root, why the ls /etc doesn't return the sudoers ?
# augtool augtool> ls /files/etc/sudoers augtool> ls /files/etc/ modprobe.d/ = (none) puppet/ = (none) sysconfig/ = (none) default/ = (none) environment = (none) ntp.conf/ = (none) inittab/ = (none) services/ = (none) grub.conf/ = (none) securetty/ = (none) xinetd.d/ = (none) hosts/ = (none) exports = (none) passwd/ = (none) pam.d/ = (none) cgrules.conf/ = (none) postfix/ = (none) krb5.conf/ = (none) aliases/ = (none) logrotate.conf/ = (none) logrotate.d/ = (none) sysctl.conf/ = (none) fstab/ = (none) ethers/ = (none) group/ = (none) yum/ = (none) yum.conf/ = (none) security/ = (none) cgconfig.conf/ = (none) ssh/ = (none) crontab/ = (none) cron.d/ = (none) augtool> augtool> # ls -l /etc/sudoers -rw-r----- 1 root root 3797 Aug 25 14:04 /etc/sudoers On Aug 25, 3:23 pm, Rob McBroom <mailingli...@skurfer.com> wrote: > On Aug 25, 2011, at 9:05 AM, Vincent wrote: > > > the augeas tool doesn't return anything when I am trying to get the > > actual spec > > augtool> print /files/etc/sudoers > > augtool> > > > How can I test augtool ? > > Fromhttp://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Augeas > > “You can see which files Augeas has successfully parsed by running augtool ls > /files/ and drilling down from there. If a file hasn’t been properly parsed > by Augeas, it simply won’t show up. This could mean that the file has a > syntax error, the file doesn’t exist, you don’t have permission to read the > file, or it could imply a failure in the lens itself.” > > Are you running `augtool` as root? > > -- > Rob McBroom > <http://www.skurfer.com/> -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
