do i need these users? Post: 302071016

Sponsored Content

Operating Systems Solaris do i need these users? Post 302071016 by csaunders on Tuesday 11th of April 2006 11:19:11 AM

04-11-2006

Registered User

Quote:

Originally Posted by rhfrommn

I would recommend against deleting those. They are all system accounts used for various purposes. For example, listen is the network listener daemon that monitors your system for requests coming in over the network. Turn that off and all of a sudden your box will be unable to accept connections over the network.

There is no harm to leaving these in place, and removing them could cause a variety of problems. Even if you're sure you don't use one of them, I would imagine removing a system account like that could cause future problems when trying to apply patches to your machine which try to update files related to the removed account.

If your concern is security related, definitely turn off the services you don't want in inetd.conf or (or using inetadm in Solaris 10). But I wouldn't remove the related system accounts.

yep im in agreement with you... completley.. but i wanted a second opinon...

csaunders

View Public Profile for csaunders

Find all posts by csaunders

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

no of users

Is there any way to find the number of unique users in a system other than who | cut -d" " -f1 | sort -u | wc -l ?

2. HP-UX

Users

Is there a command to tell what applications certain users ran in past few months? And thier last login? This is on HPUX machine Thanks!

3. Shell Programming and Scripting

users login

Hello everyone I need to send to a file the last command from all users who log in and log out by week or month. My questions are I can do it with the command or I need to do a script ? If the answer is I need to do a script, someone can help me because Im complete new to make a...

4. HP-UX

Limiting SFTP Users While Not Limiting Regular Users?

Hi, I have searched the web and have come back with nothing that is satisfactory for what I require. SFTP is my corporations new file transfer standard. What I require is a method to lock down SFTP users to their directory (they may go to sub directories) while not restricting regular users. ...

5. Solaris

To restrict the users not to change the passwords for NIS users

Hi All, How to restrict the NIS users not to change their passwords in for NIS users?? and my NIS user is unable to login to at client location what could be the problem for this ? Any body can help me. Thanks in advance.

6. Red Hat

Showing all users in 'users' and 'top' commands

Hi All, I work in a multi user environment where my school uses Red Hat Linux server. When I issue commands such as "top" or "users", I get to see what others are doing and what kinds of applications they are running (even ps -aux will give such information). "users" will let me know who else is...

7. Red Hat

users cannot switch with "su" to another users

Hi, i have a problem, it�s because users without belonging wheel group cannot switch to another user , when the password is introduced says not right password. The only solution for now is to add them to wheel users, but then i have another problem, they can login as root. Is there any...

8. Shell Programming and Scripting

Create multiple users with individual passwords to users

hi, i am new to shell scripts i write a shell script to create multiple users but i need to give passwords to that users while creating users, command to write this script

LEARN ABOUT OSF1

errors

errors(4)						     Kernel Interfaces Manual							 errors(4)

NAME

       errors - Contains a record of uucico daemon errors

SYNOPSIS

       /usr/spool/uucp/.Admin/errors

DESCRIPTION

       The /usr/spool/uucp/.Admin/errors file contains a record of uucico daemon errors that the uucp program cannot correct.  For example, if the
       uucico daemon is unable to access a directory that is needed for a file transfer, the uucp program records this in  the	errors	file.	If
       debugging is enabled for the uucico daemon, the uucp program sends the error messages to standard output instead of to the errors file.

EXAMPLES

       Following   is  the  text  of  an  error  that  might  appear  in  the  errors  file:  ASSERT ERROR (uucico) pid: 303 (7/18-8:25:09)  SYS-
       TAT OPEN FAIL /usr/spool/uucp/.Status/ (21) [SCCSID: @(#)systat.c   7.2 87/07/08 16:43:37, FILE: systat.c, LINE:100]

       This error occurred on July 18 at 8:25:09 a.m.  [(7/18-8:25:09)] when the uucico daemon, running as process 303 [(uucico) pid: 303],  could
       not  open  the  /usr/spool/uucp/.Status directory [SYSTAT OPEN FAIL /usr/spool/uucp/.Status/].  To prevent this error from occurring again,
       you should make sure the permissions for the .Status directory are correct.  It should be owned by the uucp login ID and group  uucp,  with
       permissions of 777 (read, write, and execute for owner, group, and all others).

FILES

       Contains  the  errors file and other uucp administrative files Lists the last time a remote system was contacted and the minimum time until
       the next retry

RELATED INFORMATION

       Commands: uudemon.cleanu(4)

       Daemons: uucico(8) delim off

																	 errors(4)