[NMLUG] bashrc error...

[deathandtaxes at caglan.net (Dan Parrish)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sean Leffler wrote:
| Hi all,
|
| I have a ProFTP server that uses simple username/passwords to keep users
| directories separate.
|
| Something went wonky and I'm not sure what.
|
| One of my users just told me that for the past few weeks (weeks!) they
| have not been able to get on the ftp site. When you logon, instead of
| dumping the user into the appropriate directory, they get a 550 error
| and get placed in the /ftp/pub directory and cannot get into their
| assigned directory. (/ftp/pub/uptown in this case)
|
| Ok now for more strangeness, when I go in and su to the appropriate
| account, it gives me this:
|
| bash: /home/ftp/pub/uptown/.bashrc: Permission denied
|
| the passwd entry for this user is:
| uptown:x:506:506::/home/ftp/pub/uptown:/bin/bash
|
| You can see that it supposed to (and used to) dump the ftp user into
| their specific directory, which is used to do, but now, no dice...
|
| This has apparently happened to all of the ftp accounts except one. (I'm
| not sure why the one is not affected.)
|
| Googling specific ProFTP/bashrc errors turned up little, and googling
| bashrc errors turned up thousands.
|
| Has anyone seen this behavior before? I would rather not have to wipe it
| and start over  (seems like cheating...)
|
| Thanks,
| Sean
|
|
|
| _______________________________________________
| NMLUG mailing list
| NMLUG@nmlug.org
| http://www.nmlug.org/mailman/listinfo/nmlug
I'm just going to go after the usuals first...I'd like to assume you've
already done this, but you didn't mention it.

AFAIK, a ~/.bashrc file isn't looked at by proftpd, but you might be
running something non-default.  If so, you should mention that, too.
Just by having your proftpd auth vs. the /etc/passwd file doesn't
necessarily mean that that the ~/.bashrc file is parsed.  If this is the
case, here's what I'd do.

First, I'd check the permissions on all the directories all the way down
to the .bashrc file in question.  Make sure they are executable all the
way up and down for the user or group that the proftpd daemon is running
as.  I don't think the .bashrc file itself has to be executable, but the
parent directories certainly do.

If that all checks out, I don't know what I'd do second.  If you have
proftpd parsing the .bashrc files, why is this?  I'm not familiar with
doing this and am interested in the potential benefits.

- -Dan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB9yyxnURHNoE9YE4RAmLmAKCfLpcZkrJFuXcsVrlB8reWoAH0BwCgpGlE
tmCMT/JuKmnVhxGWklOA4oY=
=gGYV
-----END PGP SIGNATURE-----