On Mon, Oct 08, 2012 at 01:11:04PM -0000, no!chance wrote:
> I think (I hope), I have found the reason. It was apparmor. Maybe, there
> were profile updates in the past?!
> I did the following:
> $ sudo aa-complain rpcbind
> $ sudo service rpcbind restart
> $ sudo service ypbind restart
> $ yptest
> was ok and gave me the list of all users, groups and others
So after making these changes, does everything come up correctly now on
reboot?
> By the way: In 10.04 the logs were much better. Since the introduction
> of unity, most logfiles (e.g. /var/log/messages) are empty and the
> remaining logs - I think - are much less informative.
Logging has nothing to do with unity. The change in log handling has only
consolidated the set of log files being written to, there are no changes to
the verbosity. /var/log/syslog contains all the information that
/var/log/messages used to. Furthermore, 12.04 logs the output of all
upstart jobs under /var/log/upstart.
On Mon, Oct 08, 2012 at 01:11:04PM -0000, no!chance wrote:
> I think (I hope), I have found the reason. It was apparmor. Maybe, there
> were profile updates in the past?!
> I did the following:
> $ sudo aa-complain rpcbind
> $ sudo service rpcbind restart
> $ sudo service ypbind restart
> $ yptest
> was ok and gave me the list of all users, groups and others
So after making these changes, does everything come up correctly now on
reboot?
> By the way: In 10.04 the logs were much better. Since the introduction
> of unity, most logfiles (e.g. /var/log/messages) are empty and the
> remaining logs - I think - are much less informative.
Logging has nothing to do with unity. The change in log handling has only
consolidated the set of log files being written to, there are no changes to
the verbosity. /var/log/syslog contains all the information that
/var/log/messages used to. Furthermore, 12.04 logs the output of all
upstart jobs under /var/log/upstart.