Hello everyone, and welcome to this Pluralsight module.
My name is Andrew Mallet,
and I'm here as your instructor to help guide you through the module,
Troubleshoot User Access, a module where we're going to go through and,
well, troubleshoot all of the problems related to our users.
Well, what does that mean?
Well, things like disk quotas,
how we can restrict space to individual users or groups.
Now, obviously, this might confuse some of our users thinking,
well, Billy can store on this drive, why can't I?
Well, maybe Billy hasn't added as many photos as you have added.
We'll take a look at login issues.
There are obviously ways that we can disable an
account or we can lock an account,
maybe these are some of the issues that a user is having,
but also look at different ways that they can gain access to
the system and what they should expect.
Password issues.
Now of course we all understand about trying to remember passwords,
we've probably struggled with this a little bit ourselves, but
there's also the issue of struggling to set a password,
so looking at our password complexity rules and looking at ways
that we can try and explain this to our users.
File access,
being able to access the files or the directories that we
feel that we should have access to.
And then making sure that we have the correct sudo privileges
if we need to escalate to do certain tasks.
Some of the things that we might find, though,
is that we have the privilege to do the task,
but we're getting things like maybe variables aren't coming through,
so we can look at what causes that.
So that's what we've got on the menu.
I do hope it's something that you're looking forward to,
and we're about to go in and take a look at our first issue and that's quotas.
When we start working through our disk quotas,
the idea is that we can start limiting space to
individual users or individual groups.
So we're going to look at installing the quota tools,
checking for our quota modules that they are in place,
looking at the mount options to make sure that quotas
are enabled on our mount points, enabling our quotas,
and then creating and setting those limits.
Once we've done that, then of course we need to report on usage,
who's using what and who's using the most,
who do we need to keep an eye on.
We get a lot of information coming back about similar users and why
one user might be storing more than another user.
So the first thing, installing our tools.
We're going to be working on our Ubuntu system, so we can run our apt update.
We can go ahead and install the quota, this is our quota
tools, and then we can run our quota ‑‑version just to
check what has been added in.
Now that's all going to be good, but of course there's a little bit
of configuration that we need to put in place.
However,
on some cloud‑based systems, we might find that it really means cut down,
and we even have that with our Vagrant system that we don't have
everything perhaps a normal install might have. Now that's probably
because many of the extra elements you're not necessarily going to use,
maybe a bit like our quota system.
So we can look under lib and modules and look for where our name then starts
with any character that's got the word quota_v, for version,
followed by any version number and then a .ko and anything following at the end.
Now we don't have anything, and we won't on my Vagrant ubuntu system.
We can go ahead and install the extra kernel drivers that we need.
Then if we go through and run our search again,
we should get results coming back.
So that's what we need to look at, and we're going to look at
that with some hands‑on from both me and yourselves, where we're
going to get this up and running. Come on, let's go through and find that command line.