Characters:
Ubuntu 8.04
Apparmor, installed there by default
Windows domain
likewise-open to connect to the parent.
cups-pdf suffering from all of the above.
Ubuntu happily installed on the iron and nicely located in the network. For greater integration with the environment, it is joined by likewise-open. And Ubuntu healed with a domain. Together, they put users' home folders into / home / <domain_name> / <username> and didn’t suspect anything until one day the user tried cups-pdf and was not upset that pdf files didn’t appear at all. And I had to pick up magazines, in which cups-pdf recorded the most interesting moments of his life.
/ var / log / cups / cups-pdf_log
[ERROR] failed to create directory (/ home / <domain_name> / <username> / PDF)
[ERROR] failed to create a user output directory (/ home / <domain_name> / <user_name> / PDF)
')
The user created the PDF directory and gave her full rights
mkdir ~ / pdf
chmod 777 PDF
Everything was correct, but pdf files did not all appear and I had to turn to the supreme Google. Although it’s impossible to expect accurate answers from Google, similar ones
are found .
And the user realized that it prevents him from enjoying the pdf of the insidious and blunt apparmor, which forgot to say likewise-open when connecting to the Windows domain, that @ {HOME} is now not only / home /, but also / home / <domain_name> /
And I had to get the rights big, rutovye and rule the brain apparmor
sudo -i nano /etc/apparmor.d/tunables/home
So that he did not think that the home directory is only / home / but also knew about / home / <domain_name>
@ {HOMEDIRS} = / home / / home / <domain_name>
And everyone rejoiced, because the PDF files themselves went to the right place and it became good.
PS note: domain_name is written exclusively in large letters, it’s like that