New version of the problem

[maobin]

Version:1.38.3

1.

New User,does not generate files: .bashrc .bash_logout,

Cause ssh:-bash-3.2$

2.

Version changed?

user[504] => access [503]
user[504] => user[504]

[maobin]

Version:1.38.3

1.

New User,does not generate files: .bashrc .bash_logout,

Cause ssh:-bash-3.2$

2.

Version changed?

user[504] => access [503]
user[504] => user[504]

3.

Default vm-Pop3d is stop？

[zEitEr]

3.

Default vm-Pop3d is stop?

Run in shell as superuser


cd /usr/local/directadmin/custombuild
./build update
./build dovecot
./build todovecot

[zEitEr]

Version:1.38.3

1.

New User,does not generate files: .bashrc .bash_logout,

Cause ssh:-bash-3.2$

Should they be created? If so, you might want to create them with sh-script with any content inside.


2.

Version changed?

user[504] => access [503]
user[504] => user[504]

Is default now http://www.directadmin.com/features.php?id=961 for new installations.

[maobin]

Should they be created? If so, you might want to create them with sh-script with any content inside.



Is default now http://www.directadmin.com/features.php?id=961 for new installations.

Now the question is:
Version:1.38.3
PuTTY Login:


login as: username
username@8.8.8.8's password:
-bash-3.2$

Normal should be:


username@localhost$

[zEitEr]

I have no idea, what are you talking about, and what has it to do with Directadmin.

[toml]

Since most new users on DA systems don't have ssh access, creating .bashrc or .profile files shouldn't normally be an issue.

If you really want them created, you should make sure your have a skeleton created for new users. In CentOS/RHEL that would be in /etc/skel you would have the default file structure you want for new users.

For example:

[root@krusty skel]# ls -la /etc/skel
total 20
drwxr-xr-x 2 root root 4096 Nov 11 10:14 .
drwxr-xr-x 63 root root 4096 Apr 27 00:14 ..
-rw-r--r-- 1 root root 33 Jan 21 2009 .bash_logout
-rw-r--r-- 1 root root 176 Jan 21 2009 .bash_profile
-rw-r--r-- 1 root root 124 Jan 21 2009 .bashrc