10-30-2008
Okay, so it does sound like /users is on the root filesystem, which is probably a Bad Thing (TM). It's unusual that you don't have a separate /export/home filesystem, which is the normal location of users' home directories on Solaris.
For completeness can we also see the output of df -k /users and df -i /users (or df -o i if the latter is invalid for Solaris 9, it certainly is on 10, to my surprise). Also, is there definitely no reference to /users in /etc/auto_master?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi, how to create account with the following
be cron enabled
only accessible via sudo (1 Reply)
Discussion started by: vilves
1 Replies
2. IP Networking
how we can find whether net is enabled or not
with out using ping
is there anyway please guide me
thanku ,in advance
sree (1 Reply)
Discussion started by: phani_sree
1 Replies
3. HP-UX
$ uname -a
HP-UX vfauh203 B.11.11 U 9000/800 486452371 unlimited-user license
SCSI TAPE: dev = 0xcd520000 Failed open - st_san_safe enabled ()
is there any tools i can run to further investigate this err0r i received from syslog.log ? im new to hp-ux thanks (1 Reply)
Discussion started by: libchk
1 Replies
4. UNIX for Dummies Questions & Answers
Hi all,
i had 500 users how can i know whether user is disabled or enabled
Thanks,
kalyan (8 Replies)
Discussion started by: kalyan212
8 Replies
5. Solaris
Hi guys.
This may be a stupid question but I am trying to see if my Solaris 9 server has async i/o enabled...
Is there a quick way to determine this?
Thanks in advance. (1 Reply)
Discussion started by: jamie_collins
1 Replies
6. Linux
Hi
when I run the following GET commad:
./snmpget -m ALL -M /data/net/naamab/snmp/snmp_mib/ -v 3 -a MD5 -l authPriv -u test1 -A welcome1 -x DES -X privpass 127.0.0.1 NOVELSAT-MODULATOR-MIB::nsModLineCMMode.0 -d
I get the error:
Encryption support not enabled.
snmpget: USM encryption... (1 Reply)
Discussion started by: naamabm
1 Replies
7. Shell Programming and Scripting
:(
---------- Post updated at 01:51 AM ---------- Previous update was at 01:50 AM ----------
Not working
---------- Post updated at 02:04 AM ---------- Previous update was at 01:51 AM ----------
cp -p /home/* home/exp/*.`date`
i am using this (4 Replies)
Discussion started by: rishiraaz
4 Replies
8. AIX
AIX Version 6.1 and 7.1.
I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device.
It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies
9. What is on Your Mind?
Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019.
See also:
CNN:
Iconic 80s computer The Commodore 64 to return with fully-functional keyboard
YouTube:
The C64 | Trailer
... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT REDHAT
qmail-pw2u
qmail-pw2u(8) System Manager's Manual qmail-pw2u(8)
NAME
qmail-pw2u - build address assignments from a passwd file
SYNOPSIS
qmail-pw2u [ -/ohHuUC ] [ -cchar ]
DESCRIPTION
qmail-pw2u reads a V7-format passwd file from standard input and prints a qmail-users-format assignment file.
A V7-format passwd file is a series of lines. Each line has the format
user:password:uid:gid:gecos:home:shell
where user is an account name, uid and gid are the user id and group id of that account, and home is the account's home directory. pass-
word, gecos, and shell are ignored by qmail-pw2u.
If you put the output of qmail-pw2u into /var/lib/qmail/users/assign, and then run qmail-newu, qmail-lspawn will obey the assignments
printed by qmail-pw2u. WARNING: After changing any users, uids, gids, or home directories in your passwd file, you must run qmail-pw2u and
qmail-newu again if you want qmail-lspawn to see the changes.
RULES
By default, qmail-pw2u follows the same rules as qmail-getpw. It skips user if (1) uid is zero, (2) home does not exist, (3) user does not
own home, or (4) user contains uppercase letters. It then gives each remaining user control over the basic user address and all addresses
of the form user-anything. A catch-all user, alias, controls all other addresses.
You may change these rules by setting up files in /var/lib/qmail/users:
include
Allowed users, one per line. If include exists, and user is not listed in include, user is ignored.
exclude
Ignored users, one per line. If exclude exists, and user is listed in exclude, user is ignored.
mailnames
Replacement names for users. Each line has the form
user:mailname1:mailname2:...
The addresses mailname1 and mailname1-ext and mailname2 and so on will be delivered to user.
WARNING: The addresses user and user-ext will not be delivered to user unless user is listed as one of the mailnames.
A line in mailnames is silently ignored if the user does not exist.
subusers
Extra addresses. Each line has the form
sub:user:pre:
sub will be handled by home/.qmail-pre, where home is user's home directory; sub-ext will be handled by home/.qmail-pre-ext.
append Extra assignments, printed at the end of qmail-pw2u's output.
OPTIONS
-o (Default.) Skip user if home does not exist (or is not visible to qmail-pw2u). Skip user if home is not owned by user.
-h Stop if home does not exist. This is appropriate if every user is supposed to have a home directory. Skip user if home is not
owned by user.
-H Do not check the existence or ownership of home.
-U (Default.) Skip user if there are any uppercase letters in user.
-u Allow uppercase letters in user.
-cchar Use char as the user-extension delimiter in place of -.
-C Disable the user-extension mechanism.
-/ Use home/.qmail-/... instead of home/.qmail-...
SEE ALSO
qmail-users(5), qmail-lspawn(8), qmail-newu(8), qmail-getpw(8)
qmail-pw2u(8)