07-29-2019
Quote:
Originally Posted by
MadeInGermany
1. scanning "unowned" homedirs for recently accessed files. If nothing found, delete. If something found, display it and stop the search - and do not delete.
Yes, that is another possible solution. A problem could be that users put things in their homedir crontab and so some files get regularly accessed even if the accounts are deleted. If this or my solution is better is perhaps depending on the environment you work in, policies in place and - last but not least - personal taste. The real point, though, is to take care of (removed users) data in
some way in specific and to not let accumulate data waste on the system in general.
Quote:
Originally Posted by
MadeInGermany
2. scanning shared project directories in "deepest first fashion" (find -depth), and assign each "unowned" directory to the owner of its parent directory.
This is a very good idea! I will update the above script eventually when i find time.
I hope this helps.
bakunin
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi!
Need your help. How can I delete the cache folder of multiple user home directories via automatically executed shell script on a Mac OS X Server?
Example:
The userdata are stored on a Xsan Volume like this:
/Volumes/Xsan/userdata/mike
/Volumes/Xsan/userdata/peter... (2 Replies)
Discussion started by: nipodrom
2 Replies
2. Shell Programming and Scripting
Hi, I'm currently working on my school assignment on how to verify that all user home directories are writable only by their owner on Solaris with VMware. But I'm not sure why my codes take a very long time to display the results. My friend says it's the `su - $i -c "ls -ld" 2> /dev/null | grep... (1 Reply)
Discussion started by: NuuBe
1 Replies
3. Homework & Coursework Questions
1. The problem statement, all variables and given/known data:
Need to verify that all user home directories are writable only by their owner on Solaris. The script posted below is workable but it is taking a long time to display the results, and I don't seem to be able to fix it or find any... (6 Replies)
Discussion started by: NuuBe
6 Replies
4. Homework & Coursework Questions
Hello i hope this post is ok! and i hope that i get the point of rules :)
i made this tasks by my self but few of them arent working.. and i dont know why!?
u think u could help me? to give me some reasons why dont they work.. and remake my code that will work?
hope to get answer soon!
... (9 Replies)
Discussion started by: eclip
9 Replies
5. Solaris
I've allocated /exports for all user directories by making separate directories under /exports.....
:rolleyes:
now i need to unmount /exports . But i'm unable to do that..
How can i troubleshoot this issue.
Thanks in advance:D (2 Replies)
Discussion started by: vamshigvk475
2 Replies
6. UNIX for Dummies Questions & Answers
Hi,
when I installed debian 8, all files are created and owned by root, when I add new user, for example marco, he can't create directory or change files created by root. I tried with ftp, permission denied.
so, I am interested how to grant to user marco ownership of all files in the system so... (5 Replies)
Discussion started by: alanford
5 Replies
LEARN ABOUT REDHAT
lppasswd
lppasswd(1) Easy Software Products lppasswd(1)
NAME
lppasswd - add, change, or delete digest passwords.
SYNOPSIS
lppasswd [ -a ] [ -g groupname ] [ -x ] [ username ]
DESCRIPTION
lppasswd adds, changes, or deletes passwords in the CUPS digest password file, passwd.md5. When run by a normal user, lppasswd will prompt
for the old and new passwords. When run by the super-user, lppasswd can add new accounts (-a username), change existing accounts (user-
name), or delete accounts (-x username) in the digest password file. Digest usernames do not have to match local UNIX usernames, but only
UNIX usernames are supported by the CUPS client programs (lp(1), lpr(1), etc.)
The -g option specifies a group other than the system group - "sys", "system", or "root", depending on the operating system.
SECURITY ISSUES
The lppasswd command is installed setuid to root. While every attempt has been made to make it secure against exploits that could grant
super-user priviledges to unpriviledged users, paranoid system administrators may wish to disable or change the ownership of the program to
an unpriviledged account.
SEE ALSO
lp(1), lpr(1), CUPS Software Administrators Manual, CUPS Software Users Manual, http://localhost:631/documentation.html
COPYRIGHT
Copyright 1993-2002 by Easy Software Products, All Rights Reserved.
7 June 2001 Common UNIX Printing System lppasswd(1)