On Wednesday, February 20, 2019 9:17:34 AM CST Chris Schanzle wrote:
> On 2/16/19 12:14 PM, Bill Gee wrote:
> > ...After the usermod programs ran, I then did a "find -uid=500" with an
> > exec option to change ownership. Repeat for changing GID. It found a few
> > dozen files that were not in
In article <2f86eabc-697f-4f57-3a0a-f2e5da13d...@nist.gov>,
Chris Schanzle via CentOS wrote:
> My guess is you used something like
>
> Â find -uid=500 -exec chown 1000 {} \;
>
> This will start a chown process for each file, changing only one file at a
> time. That's a lot of work the syste
On 2/16/19 12:14 PM, Bill Gee wrote:
...After the usermod programs ran, I then did a "find -uid=500" with an exec
option to change ownership. Repeat for changing GID. It found a few dozen files that
were not in my home directory.
On the server I ran the two "find" commands against the entire
Hello everyone -
Update: Many thanks to Matt Miller for the tip on usermod options. That
worked very well! I did not know those options existed and would never have
thought to look for them.
After making and testing backups, I started with my main workstation. Rebooted
in runmode=3, then
On Thu, Feb 14, 2019 at 11:04:11AM -0600, Bill Gee wrote:
> I think I can do this in two steps.
> 0) backup, backup, backup!
This is already running and you've tested the restore process, right?
> 1) On the server - use "find" to find all files owned by UID=500. Chown
> them to UID=1000. Repeat
Hello everyone -
I have a question regarding UID and GID numbers. First, a bit of background:
Yesterday I suffered a complete power failure. My UPS batteries ran everything
for an hour, but that was not long enough. My CentOS6 server shut itself down,
just like it should. When the power cam
6 matches
Mail list logo
