Sponsored Content
Operating Systems SCO Insuficient space on /dev SCO 5.5 Post 302262832 by edfair on Saturday 29th of November 2008 02:58:15 AM
Old 11-29-2008
Your root filesystem is running out of space. Your issue is not one of removing users but of removing files that may no longer be needed.

You can use scoadmin and account management to find out where individual users are directed into the system and can sometimes tell when they last logged in, assuming that those who haven't logged in recently may no longer be employed. If no other users are pointing to the same area it is sometimes possible to remove the programs and associated data. But you really need to know the working of your system to be able to do it.

One issue you may find is that multiple users may get to the same place and that there is no specific files that belong to an individual.

Files in the /tmp area can usually be removed. Depending on what applications your users run their obsolete data can sometimes be purged and database files rebuilt to smaller sizes.

If you would list applications in use on the system someone familiar with the packages might give you some specific advice.
 

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Ran out of space on /dev/root partition

hi, I have a SCO unix server which has a 36gb hard drive, but the IT company who supplied it assigned 1gb to /dev/root, 15mb to /dev/boot and 33gb to /dev/u. The /dev/root partition is now full, is there a way I can use the 33gb assigned to /dev/u without loosing any data, preferably... (2 Replies)
Discussion started by: Martyn
2 Replies

2. SCO

No space on dev HD (1/42)

Good Evening to all, I am having a problem with our unix server, I give you a little history. last we the logins started getting slower and slower, when we tried to print nothing came out on the network printer, the system had an error ("printer file close error unit=0). Checking... (3 Replies)
Discussion started by: berkmillionare
3 Replies

3. UNIX for Advanced & Expert Users

NOTICE: HTFS: No space on dev hd (1/42)

If somebody solve this error please help me! Thanks in advance! :confused: (7 Replies)
Discussion started by: FCollet
7 Replies

4. SCO

No space on /dev/hd 1/42

No one is able to log in. What can I try? Help!:( (1 Reply)
Discussion started by: ibqti
1 Replies

5. SCO

Xenix Problems - No space on dev 1/40

Hello - I'm a newbie to these forums. Please excuse me if I am posting in the wrong area. My dilemma. The HD on our ancient Xenix system apparently is full. I receive the "no space on dev 1/40" prompt. This occurred after I attempted to purge some unwanted files. This system runs our small... (1 Reply)
Discussion started by: gmbrickley
1 Replies

6. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies

7. AIX

How to increase space /dev/hd4?

A check disk space and find /dev/hd4 used 99%. How to increase space. Thank you for advice. /home/tecsys > df Filesystem 512-blocks Free %Used Iused %Iused Mounted on /dev/hd4 1048576 20624 99% 5977 68% / /dev/hd2 6815744 653032 91% 59194 ... (4 Replies)
Discussion started by: yapcs88
4 Replies
RMUSER(8)						    BSD System Manager's Manual 						 RMUSER(8)

NAME
rmuser -- remove users from the system SYNOPSIS
rmuser [-yv] [-f file] [username ...] DESCRIPTION
The rmuser utility removes one or more users submitted on the command line or from a file. In removing a user from the system, this utility: 1. Removes the user's crontab(1) entry (if any). 2. Removes any at(1) jobs belonging to the user. 3. Sends a SIGKILL signal to all processes owned by the user. 4. Removes the user from the system's local password file. 5. Removes the user's home directory (if it is owned by the user), including handling of symbolic links in the path to the actual home directory. 6. Removes the incoming mail and POP daemon mail files belonging to the user from /var/mail. 7. Removes all files owned by the user from /tmp, /var/tmp, and /var/tmp/vi.recover. 8. Removes the username from all groups to which it belongs in /etc/group. (If a group becomes empty and the group name is the same as the username, the group is removed; this complements adduser(8)'s per-user unique groups.) 9. Removes all message queues, shared memory segments and semaphores owned by the user. The rmuser utility refuses to remove users whose UID is 0 (typically root), since certain actions (namely, killing all the user's processes, and perhaps removing the user's home directory) would cause damage to a running system. If it is necessary to remove a user whose UID is 0, see vipw(8) for information on directly editing the password file. If rmuser was not invoked with the -y option, it will show the selected user's password file entry and ask for confirmation that the user be removed. It will then ask for confirmation to delete the user's home directory. If the answer is in the affirmative, the home directory and any files and subdirectories under it will be deleted only if they are owned by the user. See pw(8) for more details. As rmuser operates, it informs the user regarding the current activity. If any errors occur, they are posted to standard error and, if it is possible for rmuser to continue, it will. The options are as follows: -f file The rmuser utility will get a list of users to be removed from file, which will contain one user per line. Anything following a hash mark ('#'), including the hash mark itself, is considered a comment and will not be processed. If the file is owned by anyone other than a user with UID 0, or is writable by anyone other than the owner, rmuser will refuse to continue. -y Implicitly answer ``yes'' to any and all prompts. Currently, this includes prompts on whether to remove the specified user and whether to remove the home directory. This option requires that either the -f option be used, or one or more user names be given as command line arguments. -v Enable verbose mode. Normally, the output includes one line per removed user; however, with this option rmuser will be much more chatty about the steps taken. username Identifies one or more users to be removed; if not present, rmuser interactively asks for one or more users to be removed. FILES
/etc/master.passwd /etc/passwd /etc/group /etc/spwd.db /etc/pwd.db SEE ALSO
at(1), chpass(1), crontab(1), finger(1), passwd(1), group(5), passwd(5), adduser(8), pw(8), pwd_mkdb(8), vipw(8) HISTORY
The rmuser utility appeared in FreeBSD 2.2. BUGS
The rmuser utility does not comprehensively search the file system for all files owned by the removed user and remove them; to do so on a system of any size is prohibitively slow and I/O intensive. It is also unable to remove symbolic links that were created by the user in /tmp or /var/tmp, as symbolic links on 4.4BSD file systems do not contain information as to who created them. Also, there may be other files cre- ated in /var/mail other than /var/mail/username and /var/mail/.pop.username that are not owned by the removed user but should be removed. The rmuser utility has no knowledge of YP/NIS, and it operates only on the local password file. BSD
May 10, 2002 BSD
All times are GMT -4. The time now is 05:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy