08-09-2001
Problems with /export/home
I'm having a problem with my /export/home directory. A few of my users are getting superblock problems when they try to save files. what's something I can do to fix the problem? I'm running Solaris 7 on an Intel so no Open Boot Prom... any help would be great. thanks..
,AP
8 More Discussions You Might Find Interesting
1. Solaris
My 2GB /export/home/ directory is almost 100% full
df -k | grep /export/home
/dev/vx/dsk/rootdg/vl73 2031711 1951009 19751 99% /export/home
I intend to relocate it to a different 4GB filesystem late at night when there is no user on the system.
How do I go... (3 Replies)
Discussion started by: Msororaji
3 Replies
2. Solaris
Hi all,
i have to need one script:
1. it will capture the unused user accounts in /export/home directory.
2. it will capture the locked user accounts in /export/home directory.
Note: locked accounts will show in /etc/passwd like /bin/false --> (instead of ksh it will show false)
the... (1 Reply)
Discussion started by: krishna176
1 Replies
3. Solaris
Hi Guys,
Thanks for taking the time to read the problem i having outlined below:
Before i go into the problem can you please tell me what the following means?
a. "dt" stands for and what does it means?
Configuration Below:
1x Unix Server
2x Unix Terminals
(both systems are... (3 Replies)
Discussion started by: tlee
3 Replies
4. UNIX for Dummies Questions & Answers
please could someone explain what is /export/home used for ? (1 Reply)
Discussion started by: venhart
1 Replies
5. Solaris
Friends,
I am new to Solaris, but familiar with Linux. Could you throw some light on the need for /export/home directory in Solaris.
In Linux, the default home directory for a normal user is /home/<username>. If domain concept is implemented, then the /home directory of server will be mounted... (4 Replies)
Discussion started by: saagar
4 Replies
6. Solaris
Hello all,
I am trying to set quotas on /export/home filesystem for some of our users on a Solaris Zone I know that you would be redirecting me to some of the documentation pages, but I have already done that.
The /export/home on the Zone is a Veritas FS and I cannot see an entry for... (4 Replies)
Discussion started by: grajp002
4 Replies
7. Solaris
Hi all
i am using solaris 10, i am creating user with
useradd -d/home/user -m -s /bin/sh user
user is created with in the following path
/export/home/user (auto mount)
i need the user to be created like this
(/home as default home directory )
useradd -d /home/user -m -s /bin/sh... (2 Replies)
Discussion started by: kalyankalyan
2 Replies
8. Solaris
I am newbies in solaris, hope u guys can help me,
I need to transfer /export/home directory that currently mount at storage and migrate into local disk. may i know the best way to do it?
Thanks (6 Replies)
Discussion started by: Deeo
6 Replies
LEARN ABOUT LINUX
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)