Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Puppet 4.10 Beginner???s Guide, Second Edition

You're reading from   Puppet 4.10 Beginner???s Guide, Second Edition From newbie to pro with Puppet 4.10

Arrow left icon
Product type Paperback
Published in May 2017
Publisher Packt
ISBN-13 9781787124004
Length 268 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
John Arundel John Arundel
Author Profile Icon John Arundel
John Arundel
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Getting started with Puppet FREE CHAPTER 2. Creating your first manifests 3. Managing your Puppet code with Git 4. Understanding Puppet resources 5. Variables, expressions, and facts 6. Managing data with Hiera 7. Mastering modules 8. Classes, roles, and profiles 9. Managing files with templates 10. Controlling containers 11. Orchestrating cloud resources 12. Putting it all together Index

Users


A user on UNIX-like systems does not necessarily correspond to a human person who logs in and types commands, although it sometimes does. A user is simply a named entity that can own files and run commands with certain permissions, and that may or may not have permission to read or modify other users' files. It's very common, for sound security reasons, to run each service on a system with its own user account. This simply means that the service runs with the identity and permissions of that user.

For example, a web server will often run as the www-data user, which exists solely to own the files the web server needs to read and write. This limits the danger of a security breach via the web server, because the attacker would only have www-data's permissions, which are very limited, rather than root's, which can modify any aspect of the system. It is generally a bad idea to run services exposed to the public Internet as the root user. The service user should have only the minimum permissions...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime