Ipmi is your friend.

Is that the same database my user couldn’t connect to today?

There’s always backups… Right?

… Right?

Thanks for the follow up!

It is plausible that location used to be a bathroom in a now missing building. I just don’t think TP would hold up like that at all. TP is generally designed to come apart over time, especially in the presence of water, to help it go through wastewater pipes and get processed when it reaches the wastewater plant at the end of the line.

So I think, even if the holder is genuinely part of the original building that was there, someone added to it with, what looks like, a TP roll… For art.

I don’t believe for a second that this is an actual roll of paper. I think it’s art made to look like what we all think it is.

To be fair, I knew a lot of people who struggled with word problems in math class.

Aww, C’mon, don’t sell yourself short like that, I’m sure you’re great at… Something…

For example, you would probably be way more useful than an AI, if there was a power outage.

Yeah, that’s my main take away.

Not only did she put it back in the fridge in this completely fabricated story, but they did so without washing it?

Who does that?

I’m not a coder, and… Well… Thanks, I hate it.

Even I know this is horrific. Where the fuck does this statement end? Which of these brackets refer to this section of other brackets. Idfk.

I could give a shit less if it was just for a single block per or something but “;}}}” hurts me.

Makes aeroplane noises and gestures above head

Yes you will.

Good song tho.

I moved my DNS to a pair of raspberry Pi 3’s running bind, with a DNS stub zone for my homelab domain that points to my homelab DNS servers.

That way the internet keeps working whether my homelab works or not. Keeps the wife aggro down.

You can do whatever you want. Don’t let anyone tell you it’s “wrong”. A big part of homelabbing is to try stuff. If it doesn’t work, that’s fine, you learned something, and that was the point.

For me, I don’t see a UPS as essential. It’s generally a good idea, but not strictly essential. My servers are on 24/7, because I have services that do things overnight for me. I also know that some people access my lab when I’m not awake, so I just leave it on so it can be ready for anything at any time. It poses some unique challenges sometimes when running stuff that’s basically 24/7/365.

Be safe, have fun, learn stuff.

Yep, there’s actually quite a few more than what I mentioned, if you get into the advanced dialogs.

IMO, it’s unnecessarily complicated, but given that NTFS is used for network file sharing in large companies, I get why it’s so crazy. They probably demand those kinds of granular permissions.

I know Linux is a lot simpler. Just read/write/execute, and a single group, single owner, and a setting for “everyone else” kind of thing, which is generally sufficient for 90% of use cases.

As an IT person, hearing that someone has already restarted to try to fix it, gives me mixed feelings.

First, they might be lying. I’ve had it happen that people tell me they’ve done something when they have not. Restarting is usually an easy one to verify, just check the uptime of the system.

Second, maybe they did everything right, and actually restarted, that’s cool that they tried something before calling in. I appreciate that.

Third, if the second thing is true then, I’m now frustrated, because now I have to get dirty with whatever is happening since a reboot that should have fixed the problem, didn’t fix it. I know it’s not going to be an easy fix. Most of the time, I’m right, unfortunately.

I’m all for users trying stuff before calling in. But recognise that you don’t, and shouldn’t have access to some things. Sometimes that’s administrator rights, sometimes that’s a piece of software, sometimes it’s the ability to turn off the AV/firewall.

It can be a lot of things. If you’re not sure if what you’re trying won’t screw things up more than they already are, then don’t do it. If it’s something simple that you know how to do, go for it. If you happen to get it fixed, so much the better.

“Customer self resolved” is usually the fastest way to get a problem resolved. That’s good for you, for me, and good for everyone.

I’m a sysadmin and I work with Windows a lot.

The short version is that only the users granted permission to a given set of files can access those files. With NTFS permissions it’s… Complicated. You can have explicit permission to a file, or implied permission via a group that you’re a part of, or some combination of those things. You can also have read, but no write. You can have append but not create, you can have delete, but not list. It’s a lot of very granular, very crazy permissions.

There’s also deny permissions which overrule everything.

What has likely happened is that the posters user account doesn’t have implied or explicit permission to the file, but if you sign in as an administrator, even if the administrator doesn’t have permission to read/write/append/delete the file, the administrator has permission to take ownership of a file, and as owner, change the permissions of a file. Being owner doesn’t mean you can open/read/write/append/delete anything, you can just change permissions and give yourself (or anyone else) permissions to the file.

Changing ownership is a right which, as far as I’m aware, cannot be revoked from admin level users. They can always change ownership. Owners of files cannot be denied the right to change the permissions of a file as far as I know. This will always result in some method by which administrative level accounts can recover access to files and folders.

In my experience, exceptions exist but are extremely rare (usually to do with kernel level stuff, and/or lockouts by security/AV software).

The poster might legally and physically own the device and all the data contained therein, and may have an administrative level account on that device, but the fact is, their NTFS permissions are not set to allow them access to the data. The post they’re replying to is trying to let them know how to fix it by using an administrative level account and they’re not tech-savvy enough to follow along.

I don’t blame them. File permissions issues are challenging even for me, and I fully understand the problem.

I just want to be clear, this was like highschool cs classes. I took things a bit more seriously in college.

I never wrote messy code or illogical code, or any code that didn’t work. We were learning C++ in those days and if you know anything about C++, you can basically cram an entire program into a single line. You can also do some shorthand stuff for calculations and updates to variables… So while the class was instructed to use whitespace and comments and update variables like “var = var + #” I would do var += #… I wouldn’t comment it, mainly out of hubris.

I was pretty good at it but I was lazy as all hell with it.

I don’t code, at best I script. I’m a sysadmin, not a dev, so I play around in PowerShell mostly.

I just started to naturally do all of this. Not because I was taught to, but because I’ve written too many scripts that I later looked at, and thought, WTF is going on here… Who tf wrote this? (Of course it was me)…

So instead of confusing my future self, I started putting in comments. One at the beginning to describe what the file name can’t, and inline comments to step me through what’s happening, and more importantly why I did what I did.

The sheer number of comments can sometimes double the number of lines in my script, but later when I’m staring into the abyss of what I wrote, I appreciate me.