Sponsored Content
Top Forums UNIX for Beginners Questions & Answers [Tip] Housekeeping Tasks Made Easy - User Home directories and Leftover Files Post 303037287 by bakunin on Monday 29th of July 2019 08:45:16 AM
Old 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

Batch delete specific folder from user home directories

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

How to verify all user home directories are writable only by their owner

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

How to verify all user home directories are writable only by their owner

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

i made this tasks. and i need some explenation or just remake my code.

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

How to unmount user home directories ??

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

New user to own files made by root?

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
sticky(8)						      System Manager's Manual							 sticky(8)

Name
       sticky - executable files with persistent text

Description
       The sticky bit (file mode bit 01000), is used to indicate special treatment for certain executable files and directories.

       While the sticky bit, mode 01000 is set on a sharable executable file, the text of that file will not be removed from the system swap area.
       Thus the file does not have to be fetched from the file system upon each execution.  As long as a copy remains in the swap area, the origi-
       nal  text  cannot  be  overwritten  in  the file system, nor can the file be deleted.  Directory entries can be removed so long as one link
       remains.

       Sharable files are made by the and options of

       To replace a sticky file that has been used, clear the sticky bit with and execute the old program to flush the swapped copy.  This can	be
       done  safely  even  if others are using it.  Overwrite the sticky file.	If the file is being executed by any process, writing will be pre-
       vented.	It suffices to simply remove the file and then rewrite it, being careful to reset the owner and mode with and Set the  sticky  bit
       again.

       A  directory  whose  sticky bit is set becomes an append-only directory, or, more accurately, a directory in which the deletion of files is
       restricted.  A file in a sticky directory may only be removed or renamed by a user if the user has write permission for the  directory  and
       the  user  is the owner of the file, the owner of the directory, or the superuser.  This feature is usefully applied to directories such as
       which must be publicly writeable but should deny users the license to arbitrarily delete or rename each others' files.

Restrictions
       Only the superuser can set the sticky bit.

See Also
       chmod(2)

								       RISC								 sticky(8)
All times are GMT -4. The time now is 03:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy