[SLE] No shell in /etc/passwd
I changed my shell in /etc/passwd, which I type the path to it wrong, now when I try and log in, it gives me an error saying I don't have a valid shell and then disconnects the sesssion. The problem is, well the machine is in a remote area, and I don't have physically access to it. I tried rlogin in which doesn't work either. Any ideas? Jack -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
got r00t? here's where you basically hack your way into the system. if you were root, then you should have a backdoor account somewhere where you can make the changes. then go into yast, system administrator, user admin.., and set the shell of root to bash. ryan -~->-----Original Message----- -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->Sent: Wednesday, January 05, 2000 3:43 PM -~->To: SuSE Linux English -~->Subject: [SLE] No shell in /etc/passwd -~-> -~-> -~-> -~->I changed my shell in /etc/passwd, which I type the path to it -~->wrong, now -~->when I try and log in, it gives me an error saying I don't have a valid -~->shell and then disconnects the sesssion. The problem is, well -~->the machine -~->is in a remote area, and I don't have physically access to it. I tried -~->rlogin in which doesn't work either. Any ideas? -~-> -~->Jack -~-> -~-> -~->-- -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->For additional commands send e-mail to -~->suse-linux-e-help@suse.com -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~-> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
got r00t?
here's where you basically hack your way into the system. if you were root, then you should have a backdoor account somewhere where you can make the changes. then go into yast, system administrator, user admin.., and set
shell of root to bash.
ryan
-~->-----Original Message----- -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->Sent: Wednesday, January 05, 2000 3:43 PM -~->To: SuSE Linux English -~->Subject: [SLE] No shell in /etc/passwd -~-> -~-> -~-> -~->I changed my shell in /etc/passwd, which I type the path to it -~->wrong, now -~->when I try and log in, it gives me an error saying I don't have a valid -~->shell and then disconnects the sesssion. The problem is, well -~->the machine -~->is in a remote area, and I don't have physically access to it. I
----- Original Message -----
From: Ryan The Great
-~->rlogin in which doesn't work either. Any ideas? -~-> -~->Jack -~-> -~-> -~->-- -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->For additional commands send e-mail to -~->suse-linux-e-help@suse.com -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
do you have an account that uses another shell (like bsh or something?)
ryan
-~->-----Original Message-----
-~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com]
-~->Sent: Wednesday, January 05, 2000 3:56 PM
-~->To: Ryan The Great; SuSE Linux English
-~->Subject: Re: [SLE] No shell in /etc/passwd
-~->
-~->
-~->
-~->----- Original Message -----
-~->From: Ryan The Great
Nope. See I recompile bash and though I copied it over to /usr/local/bin (I
guess I didn't) and then did a vi /etc/passwd and changed all the account
(except root) to point to the 'new' bash. Either it didn't copy over right
(or I copied it to the wrong place) or I missed typed all the shells for
those accounts. The only account at this point is root. I do have 'r'
access to a couple programs like rsh and rlogin, but they don't like working
to well without a shell.
I tried doing a
/bin/rsh host.domain.com /bin/sh
but it gave a permission denied. If I do a /bin/rsh host.domain.com it asks
for a password, then fails with a "no shell" error message.
Jack
----- Original Message -----
From: Ryan The Great
do you have an account that uses another shell (like bsh or something?)
ryan
-~->-----Original Message----- -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->Sent: Wednesday, January 05, 2000 3:56 PM -~->To: Ryan The Great; SuSE Linux English -~->Subject: Re: [SLE] No shell in /etc/passwd -~-> -~-> -~-> -~->----- Original Message ----- -~->From: Ryan The Great
-~->To: Jack Barnett ; SuSE Linux English -~-> -~->Sent: Wednesday, January 05, 2000 2:44 PM -~->Subject: RE: [SLE] No shell in /etc/passwd -~-> -~->I do have 'r00t', and I did have a back door account. But the -~->problem is my -~->backdoor got globbed at the same time. I recompiled bash, but -~->installed it -~->in the wrong place. I changed everything in /etc/passwd to -~->reflect this, -~->(even on my second and thrid accounts) and then it went down. -~->I don't have -~->physically access either. The good thing is, I do a .rhosts file, but -~->rlogin gives an error about no shell and rsh give the same -~->error, if I try -~->to execute any command (/bin/ls, /bin/sh) it gives a permission deneid -~->error. -~-> -~->Jack -~-> -~-> -~-> -~->> got r00t? -~->> -~->> here's where you basically hack your way into the system. if you were -~->root, -~->> then you should have a backdoor account somewhere where you -~->can make the -~->> changes. then go into yast, system administrator, user -~->admin.., and set -~->the -~->> shell of root to bash. -~->> -~->> -~->> ryan -~->> -~->> -~->-----Original Message----- -~->> -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->> -~->Sent: Wednesday, January 05, 2000 3:43 PM -~->> -~->To: SuSE Linux English -~->> -~->Subject: [SLE] No shell in /etc/passwd -~->> -~-> -~->> -~-> -~->> -~-> -~->> -~->I changed my shell in /etc/passwd, which I type the path to it -~->> -~->wrong, now -~->> -~->when I try and log in, it gives me an error saying I don't have a -~->valid -~->> -~->shell and then disconnects the sesssion. The problem is, well -~->> -~->the machine -~->> -~->is in a remote area, and I don't have physically access to it. I -~->tried -~->> -~->rlogin in which doesn't work either. Any ideas? -~->> -~-> -~->> -~->Jack -~->> -~-> -~->> -~-> -~->> -~->-- -~->> -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->> -~->For additional commands send e-mail to -~->> -~->suse-linux-e-help@suse.com -~->> -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~-> -~->> -~->> -~->> -- -~->> To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->> For additional commands send e-mail to suse-linux-e-help@suse.com -~->> Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~->> -~-> -~-> -~->-- -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->For additional commands send e-mail to -~->suse-linux-e-help@suse.com -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~-> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
try using one of the accounts that have a shell correctly entered.
if you can access this account, you can then take over root (even if root
doesn't have a shell defined).
-~->-----Original Message-----
-~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com]
-~->Sent: Wednesday, January 05, 2000 4:04 PM
-~->To: Ryan The Great; SuSE Linux English
-~->Subject: Re: [SLE] No shell in /etc/passwd
-~->
-~->
-~->
-~->Nope. See I recompile bash and though I copied it over to
-~->/usr/local/bin (I
-~->guess I didn't) and then did a vi /etc/passwd and changed all
-~->the account
-~->(except root) to point to the 'new' bash. Either it didn't
-~->copy over right
-~->(or I copied it to the wrong place) or I missed typed all the shells for
-~->those accounts. The only account at this point is root. I do have 'r'
-~->access to a couple programs like rsh and rlogin, but they don't
-~->like working
-~->to well without a shell.
-~->
-~->I tried doing a
-~->
-~->/bin/rsh host.domain.com /bin/sh
-~->
-~->but it gave a permission denied. If I do a /bin/rsh
-~->host.domain.com it asks
-~->for a password, then fails with a "no shell" error message.
-~->
-~->Jack
-~->
-~->----- Original Message -----
-~->From: Ryan The Great
Root has a shell define, it is the only one on the system, everyone else
don't have a shell. I know root's password, but for security reasons I
disabled telnet login and .rhosts for the root account (DOH!).
Jack
----- Original Message -----
From: Ryan The Great
try using one of the accounts that have a shell correctly entered. if you can access this account, you can then take over root (even if root doesn't have a shell defined).
-~->-----Original Message----- -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->Sent: Wednesday, January 05, 2000 4:04 PM -~->To: Ryan The Great; SuSE Linux English -~->Subject: Re: [SLE] No shell in /etc/passwd -~-> -~-> -~-> -~->Nope. See I recompile bash and though I copied it over to -~->/usr/local/bin (I -~->guess I didn't) and then did a vi /etc/passwd and changed all -~->the account -~->(except root) to point to the 'new' bash. Either it didn't -~->copy over right -~->(or I copied it to the wrong place) or I missed typed all the shells for -~->those accounts. The only account at this point is root. I do have 'r' -~->access to a couple programs like rsh and rlogin, but they don't -~->like working -~->to well without a shell. -~-> -~->I tried doing a -~-> -~->/bin/rsh host.domain.com /bin/sh -~-> -~->but it gave a permission denied. If I do a /bin/rsh -~->host.domain.com it asks -~->for a password, then fails with a "no shell" error message. -~-> -~->Jack -~-> -~->----- Original Message ----- -~->From: Ryan The Great
-~->To: Jack Barnett ; SuSE Linux English -~-> -~->Sent: Wednesday, January 05, 2000 2:57 PM -~->Subject: RE: [SLE] No shell in /etc/passwd -~-> -~-> -~->> do you have an account that uses another shell (like bsh or -~->something?) -~->> -~->> ryan -~->> -~->> -~->-----Original Message----- -~->> -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->> -~->Sent: Wednesday, January 05, 2000 3:56 PM -~->> -~->To: Ryan The Great; SuSE Linux English -~->> -~->Subject: Re: [SLE] No shell in /etc/passwd -~->> -~-> -~->> -~-> -~->> -~-> -~->> -~->----- Original Message ----- -~->> -~->From: Ryan The Great -~->> -~->To: Jack Barnett ; SuSE Linux English -~->> -~-> -~->> -~->Sent: Wednesday, January 05, 2000 2:44 PM -~->> -~->Subject: RE: [SLE] No shell in /etc/passwd -~->> -~-> -~->> -~->I do have 'r00t', and I did have a back door account. But the -~->> -~->problem is my -~->> -~->backdoor got globbed at the same time. I recompiled bash, but -~->> -~->installed it -~->> -~->in the wrong place. I changed everything in /etc/passwd to -~->> -~->reflect this, -~->> -~->(even on my second and thrid accounts) and then it went down. -~->> -~->I don't have -~->> -~->physically access either. The good thing is, I do a -~->.rhosts file, but -~->> -~->rlogin gives an error about no shell and rsh give the same -~->> -~->error, if I try -~->> -~->to execute any command (/bin/ls, /bin/sh) it gives a -~->permission deneid -~->> -~->error. -~->> -~-> -~->> -~->Jack -~->> -~-> -~->> -~-> -~->> -~-> -~->> -~->> got r00t? -~->> -~->> -~->> -~->> here's where you basically hack your way into the system. if you -~->were -~->> -~->root, -~->> -~->> then you should have a backdoor account somewhere where you -~->> -~->can make the -~->> -~->> changes. then go into yast, system administrator, user -~->> -~->admin.., and set -~->> -~->the -~->> -~->> shell of root to bash. -~->> -~->> -~->> -~->> -~->> -~->> ryan -~->> -~->> -~->> -~->> -~->-----Original Message----- -~->> -~->> -~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com] -~->> -~->> -~->Sent: Wednesday, January 05, 2000 3:43 PM -~->> -~->> -~->To: SuSE Linux English -~->> -~->> -~->Subject: [SLE] No shell in /etc/passwd -~->> -~->> -~-> -~->> -~->> -~-> -~->> -~->> -~-> -~->> -~->> -~->I changed my shell in /etc/passwd, which I type the -~->path to it -~->> -~->> -~->wrong, now -~->> -~->> -~->when I try and log in, it gives me an error saying -~->I don't have -~->a -~->> -~->valid -~->> -~->> -~->shell and then disconnects the sesssion. The -~->problem is, well -~->> -~->> -~->the machine -~->> -~->> -~->is in a remote area, and I don't have physically -~->access to it. -~->I -~->> -~->tried -~->> -~->> -~->rlogin in which doesn't work either. Any ideas? -~->> -~->> -~-> -~->> -~->> -~->Jack -~->> -~->> -~-> -~->> -~->> -~-> -~->> -~->> -~->-- -~->> -~->> -~->To unsubscribe send e-mail to -~->suse-linux-e-unsubscribe@suse.com -~->> -~->> -~->For additional commands send e-mail to -~->> -~->> -~->suse-linux-e-help@suse.com -~->> -~->> -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~->> -~-> -~->> -~->> -~->> -~->> -~->> -~->> -- -~->> -~->> To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->> -~->> For additional commands send e-mail to -~->suse-linux-e-help@suse.com -~->> -~->> Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~->> -~->> -~->> -~->> -~-> -~->> -~-> -~->> -~->-- -~->> -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->> -~->For additional commands send e-mail to -~->> -~->suse-linux-e-help@suse.com -~->> -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~-> -~->> -~->> -- -~->> To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->> For additional commands send e-mail to suse-linux-e-help@suse.com -~->> Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~->> -~->> -~-> -~-> -~->-- -~->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com -~->For additional commands send e-mail to -~->suse-linux-e-help@suse.com -~->Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -~-> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
[Charset iso-8859-1 unsupported, filtering to ASCII...]
Root has a shell define, it is the only one on the system, everyone else don't have a shell. I know root's password, but for security reasons I disabled telnet login and .rhosts for the root account (DOH!).
Jack
Jack, do you have ssh installed on your system (or OpenSSH for that matter)? I hope you do, especially if you are administering it over an untrusted network! In which case you can simply ssh in to your machine as root. While root telnet is disabled, ssh will still give you direct root access. Else, you may have to go into ftp and hope that you have one of those previous versions installed with security holes through which you can get root access :-(. Hope this helps, Alex. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
do you have X-windows running on the server?
-~->-----Original Message-----
-~->From: Jack Barnett [mailto:jbarnett@axil.netmate.com]
-~->Sent: Wednesday, January 05, 2000 4:12 PM
-~->To: Ryan The Great; SuSE Linux English
-~->Subject: Re: [SLE] No shell in /etc/passwd
-~->
-~->
-~->
-~->Root has a shell define, it is the only one on the system, everyone else
-~->don't have a shell. I know root's password, but for security reasons I
-~->disabled telnet login and .rhosts for the root account (DOH!).
-~->
-~->Jack
-~->
-~->----- Original Message -----
-~->From: Ryan The Great
On Wed, 05 Jan 2000, you wrote:
Root has a shell define, it is the only one on the system, everyone else don't have a shell. I know root's password, but for security reasons I disabled telnet login and .rhosts for the root account (DOH!).
Jack
This is a longshot since you probably couldn't go in as root, but what about ftp? Any way to replace the passwd file or maybe create a link to your shell in the proper location? -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Darren R. Weber drw@linuxfan.com ICQ# 2849193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
----- Original Message -----
From: Darren R. Weber
On Wed, 05 Jan 2000, you wrote:
Root has a shell define, it is the only one on the system, everyone else don't have a shell. I know root's password, but for security reasons I disabled telnet login and .rhosts for the root account (DOH!).
Jack
This is a longshot since you probably couldn't go in as root, but what about ftp? Any way to replace the passwd file or maybe create a link to your shell in the proper location?
Yep, it worked, download the password file, edit it, upload it as root. See other email. Thanks again, Jack
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Darren R. Weber drw@linuxfan.com ICQ# 2849193 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jack Barnett wrote:
----- Original Message ----- From: Darren R. Weber
To: Jack Barnett Cc: Sent: Wednesday, January 05, 2000 5:23 PM Subject: Re: [SLE] No shell in /etc/passwd On Wed, 05 Jan 2000, you wrote:
Root has a shell define, it is the only one on the system, everyone else don't have a shell. I know root's password, but for security reasons I disabled telnet login and .rhosts for the root account (DOH!).
Jack
This is a longshot since you probably couldn't go in as root, but what about ftp? Any way to replace the passwd file or maybe create a link to your shell in the proper location?
Yep, it worked, download the password file, edit it, upload it as root. See other email.
Pardon me for not contributing to the solution, but it seems to me you have just exposed a security hole in that server. The benefits of disabling root telnet is offset by allowing root ftp. MOTO. -- George Toft http://www.georgetoft.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
----- Original Message -----
From: George Toft
Jack Barnett wrote:
----- Original Message ----- From: Darren R. Weber
To: Jack Barnett Cc: Sent: Wednesday, January 05, 2000 5:23 PM Subject: Re: [SLE] No shell in /etc/passwd On Wed, 05 Jan 2000, you wrote:
Root has a shell define, it is the only one on the system, everyone
else
don't have a shell. I know root's password, but for security reasons I disabled telnet login and .rhosts for the root account (DOH!).
Jack
This is a longshot since you probably couldn't go in as root, but what about ftp? Any way to replace the passwd file or maybe create a link to your shell in the proper location?
Yep, it worked, download the password file, edit it, upload it as root. See other email.
Pardon me for not contributing to the solution, but it seems to me you have just exposed a security hole in that server. The benefits of disabling root telnet is offset by allowing root ftp. MOTO. -- George Toft http://www.georgetoft.com
I forgot to disable root telnet, it is disabled now. Jack
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi all, I'm trying to introduce first LINUX box in my company. Its task is to handle what is being handled by HP-UX as NFS server. It actually connects to all hp workstations. Here are what I have done so far: I exported <linux>:/tmp directory by putting into /etc/exports and run /usr/sbin/exportfs to activate it. In HP workstation, I used "sam" to mount <linux>:/tmp to local directory, say /tmpnfs. It works until now. I moved further exporting <linux>:/working1 to same Hp workstation by using the same /etc/export file as mention above. Now couldn't mount <linux>:/working1 anymore onto local directory. The error message is "<linux>:/working1 access denial. when I ls -l on linux. I found the permission status of /tmp, /working1 is difference as below - the character 't' of /tmp versus 'x' /working1 drwxrwxrwt /tmp drwxrwxrwx /working1 What puzzle me is that if /tmp is functionning, why /working1 does not work ? Would somebody give me some ideas or suggestions, Please. I don't want to fail this project, as I have a few more linux boxes to implement. Thanks in advance and appreciate any comments and/or suggestions. Rgds, Nixien -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I'm trying to introduce first LINUX box in my company. Its task is to handle what is being handled by HP-UX as NFS server. It actually connects to all hp workstations. Here are what I have done so far:
I exported <linux>:/tmp directory by putting into /etc/exports and run /usr/sbin/exportfs to activate it. In HP workstation, I used "sam" to mount <linux>:/tmp to local directory, say /tmpnfs. It works until now. I moved further exporting <linux>:/working1 to same Hp workstation by using the same /etc/export file as mention above. Now couldn't mount <linux>:/working1 anymore onto local directory. The error message is "<linux>:/working1 access denial. when I ls -l on linux. I found the permission status of /tmp, /working1 is difference as below - the character 't' of /tmp versus 'x' /working1
drwxrwxrwt /tmp
drwxrwxrwx /working1
What puzzle me is that if /tmp is functionning, why /working1 does not work ?
The t on the end of the /tmp directory pemissions means the sticky bit is set. I don't think Linux worries about this, but HPUX might. I wouldn't have thought it would make any difference, but "chmod +t /working1" will make them the same. I don't know what /usr/sbin/exportfs is supposed to do. I've never seen that before. To make the nfsd reread the exports file you send the process a SIGHUP. I've had problems with that and always take the easy route: reboot the machine after changing /etc/exports. One more thing: are there any messages in your log file complaining about an unauthorised NFS access? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi Derek, /usr/sbin/exportfs is a file I created to activate new entry in /etc/exports, Here is who it looks like: #!/bin/sh (press RETURN) killall -HUP /usr/sbin/rpc.mountd killall -HUP /usr/sbin/rpc.pcnfsd killall -HUP /usr/sbin/rpc.nfsd echo re-exported file systems Here is the messages I got after running /usr/sbin/exportfs. Don't ask me why, I don't have the answer either. The only thing I know is no matter how the messages are being produced. /tmp still able to exports. lc:~ # exportfs /usr/sbin/rpc.mountd: no process killed /usr/sbin/rpc.pcnfsd: no process killed /usr/sbin/rpc.nfsd: no process killed re-exported file systems This the rpc information: slc:~ # rpcinfo -p program vers proto port 100000 2 tcp 111 rpcbind 100000 2 udp 111 rpcbind 100024 1 udp 700 status 100024 1 tcp 702 status 100003 2 udp 2049 nfs 100005 1 udp 704 mountd 100005 1 tcp 706 mountd 100005 2 udp 709 mountd 100005 2 tcp 711 mountd 100021 1 udp 1024 nlockmgr 100021 3 udp 1024 nlockmgr 100021 1 tcp 1024 nlockmgr 100021 3 tcp 1024 nlockmgr 150001 1 udp 718 pcnfsd 150001 2 udp 718 pcnfsd 150001 1 tcp 721 pcnfsd 150001 2 tcp 721 pcnfsd This is my /etc/exports. # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /tmp T3T3V(rw) tndslr00(rw) tde01(rw) /working1 tndslr00(rw) /mytar tndslr00(rw) FYI, /tmp works perfectly, why not /working1 and /mytar which newly created. Symptom persists even after reboot. Does anyone have any clues about the situations. Appreciate any comments and pointers. Rgds, Nixien -----Original Message----- From: fountai@hursley.ibm.com [mailto:fountai@hursley.ibm.com] Sent: Thursday, January 06, 2000 11:24 PM To: SuSE English Subject: Re: [SLE] inexplainable access denial NFS
I'm trying to introduce first LINUX box in my company. Its task is to handle what is being handled by HP-UX as NFS server. It actually connects to all hp workstations. Here are what I have done so far:
I exported <linux>:/tmp directory by putting into /etc/exports and run /usr/sbin/exportfs to activate it. In HP workstation, I used "sam" to mount <linux>:/tmp to local directory, say /tmpnfs. It works until now. I moved further exporting <linux>:/working1 to same Hp workstation by using the same /etc/export file as mention above. Now couldn't mount <linux>:/working1 anymore onto local directory. The error message is "<linux>:/working1 access denial. when I ls -l on linux. I found the permission status of /tmp, /working1 is difference as below - the character 't' of /tmp versus 'x' /working1
drwxrwxrwt /tmp
drwxrwxrwx /working1
What puzzle me is that if /tmp is functionning, why /working1 does not work ?
The t on the end of the /tmp directory pemissions means the sticky bit is set. I don't think Linux worries about this, but HPUX might. I wouldn't have thought it would make any difference, but "chmod +t /working1" will make them the same. I don't know what /usr/sbin/exportfs is supposed to do. I've never seen that before. To make the nfsd reread the exports file you send the process a SIGHUP. I've had problems with that and always take the easy route: reboot the machine after changing /etc/exports. One more thing: are there any messages in your log file complaining about an unauthorised NFS access? -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
You got me stumped here. The only thing I can suggest is to make the lines for /tmp and /working1 below the same - that is, add the other 2 machines to the exports list. I can't see why it should make a difference... Try renaming the /working1 to /workingx: maybe NFS doesn't like the digit in the filename. Can't see why that should make a difference either. Who owns the /tmp and /working1 directories? The same user (root)? Ensure they are the same. Try creating a completely new directory somewhere else and see if NFS likes that. Try mounting from another machine if you have one. Try mounting from the linux server itself (ie mount localhost:/working1) to see whether the problem is at the client or server end. Sorry I can't help any more. It looks to me like everything is OK so I can't see why it won't work. Is there anything in /var/log/messages to help explain the problem? When I get desperate I try to attach an strace to the process (the server process in this case) to see if that gives any clues. Maybe you could try that?
This is my /etc/exports. # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /tmp T3T3V(rw) tndslr00(rw) tde01(rw) /working1 tndslr00(rw) /mytar tndslr00(rw)
FYI, /tmp works perfectly, why not /working1 and /mytar which newly created. Symptom persists even after reboot.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Hi Derek and all, Having commented line /tmp and others, left only /working1. Everything works as usual. Obviously, Suse accepts one and only one line, ie the first line of entry. No wanders why I couldn't exported /mnt/cdrom previously. See below: # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #/tmp T3T3V(rw) tndslr00(rw) tde01(rw) /working1 tndslr00(rw) #/mytar tndslr00(rw) #/mnt/cdrom T3T3V(ro) I still don't believe suse has this limitation- only capable of exporting one /directory - do you ? Does anyone had similar experience before, how do you go about solving it? -----Original Message----- From: fountai@hursley.ibm.com [mailto:fountai@hursley.ibm.com] Sent: Friday, January 07, 2000 5:01 PM To: SuSE English Subject: Re: [SLE] inexplainable access denial NFS You got me stumped here. The only thing I can suggest is to make the lines for /tmp and /working1 below the same - that is, add the other 2 machines to the exports list. I can't see why it should make a difference... Try renaming the /working1 to /workingx: maybe NFS doesn't like the digit in the filename. Can't see why that should make a difference either. Who owns the /tmp and /working1 directories? The same user (root)? Ensure they are the same. Try creating a completely new directory somewhere else and see if NFS likes that. Try mounting from another machine if you have one. Try mounting from the linux server itself (ie mount localhost:/working1) to see whether the problem is at the client or server end. Sorry I can't help any more. It looks to me like everything is OK so I can't see why it won't work. Is there anything in /var/log/messages to help explain the problem? When I get desperate I try to attach an strace to the process (the server process in this case) to see if that gives any clues. Maybe you could try that?
This is my /etc/exports. # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /tmp T3T3V(rw) tndslr00(rw) tde01(rw) /working1 tndslr00(rw) /mytar tndslr00(rw)
FYI, /tmp works perfectly, why not /working1 and /mytar which newly created. Symptom persists even after reboot.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
You're saying that Linux exports only the first entry in the /etc/exports file? Most odd. That's not how it works for everyone else! Try deleting the exports file and recreating it. It may have a hidden character or other corruption. Other than that I haven't got a clue...
Having commented line /tmp and others, left only /working1. Everything works as usual. Obviously, Suse accepts one and only one line, ie the first line of entry. No wanders why I couldn't exported /mnt/cdrom previously. See below: # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #/tmp T3T3V(rw) tndslr00(rw) tde01(rw) /working1 tndslr00(rw) #/mytar tndslr00(rw) #/mnt/cdrom T3T3V(ro)
I still don't believe suse has this limitation- only capable of exporting one /directory - do you ?
Does anyone had similar experience before, how do you go about solving it?
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
A collegue of mine has a Linux only network, and even that give NFS problems. I had NFS problems with Linux against HP-UX. IMO NFS has a long way to go before it is has production maturaty. We could deduct NIS possibly being a common problem base. Do you have NIS running? Koos Pol ---------------------------------------------------------------------- S.C. Pol T: +31 20 3116122 Systems Administrator F: +31 20 3116200 Compuware Europe B.V. E: koos_pol@nl.compuware.com Amsterdam PGP public key available -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I have intention to implement linux to replace one of the HPUX NFS server, if it is not as stable as I wish. I think, this idea could be a big mistake. Perhaps I should do a more thorough trial before implementing it. Can you provide more information on what NFS problem that you mentioned, I could learn from your experience. I do not have NIS running . Thanks for everything. Rgds, Nixien -----Original Message----- From: koos@nl.compuware.com [mailto:koos@nl.compuware.com]On Behalf Of Koos Pol Sent: Friday, January 07, 2000 8:53 PM To: suse-linux-e Subject: Re: [SLE] inexplainable access denial NFS A collegue of mine has a Linux only network, and even that give NFS problems. I had NFS problems with Linux against HP-UX. IMO NFS has a long way to go before it is has production maturaty. We could deduct NIS possibly being a common problem base. Do you have NIS running? Koos Pol ---------------------------------------------------------------------- S.C. Pol T: +31 20 3116122 Systems Administrator F: +31 20 3116200 Compuware Europe B.V. E: koos_pol@nl.compuware.com Amsterdam PGP public key available -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Derek and all,
Long live!
Having recreated a complete new exports file according to your advise. now
my linux box able to export /working1 /tmp and etc. Once again Thank you,
Derek.
<hpux>#mount <linux>:/working1 / Having commented line /tmp and others, left only /working1. Everything
works
as usual. Obviously, Suse accepts one and only one line, ie the first line
of entry. No wanders why I couldn't exported /mnt/cdrom previously.
See below:
# See exports(5) for a description.
# This file contains a list of all directories exported to other
computers.
# It is used by rpc.nfsd and rpc.mountd.
#/tmp T3T3V(rw) tndslr00(rw) tde01(rw)
/working1 tndslr00(rw)
#/mytar tndslr00(rw)
#/mnt/cdrom T3T3V(ro) I still don't believe suse has this limitation- only capable of exporting
one /directory - do you ? Does anyone had similar experience before, how do you go about solving it? --
To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
--
To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
nixien wrote:
Hi Derek, /usr/sbin/exportfs is a file I created to activate new entry in /etc/exports, Here is who it looks like:
#!/bin/sh (press RETURN)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this will cause an error, unless you defined "press RETURN" as a command. But this is odd. I tried your script with the same result. after that, I killed (more accidently) rpc.nfsd and restarted it from hand. ("rpc.nfsd") After that, I was able to killall -HUP ... it. odd. When nfds is started by the scripts (/sbin/init.d/nfsserver) there are additional parameters given. (I can't figure out what will result for these) Juergen
killall -HUP /usr/sbin/rpc.mountd killall -HUP /usr/sbin/rpc.pcnfsd killall -HUP /usr/sbin/rpc.nfsd echo re-exported file systems
Here is the messages I got after running /usr/sbin/exportfs. Don't ask me why, I don't have the answer either. The only thing I know is no matter how the messages are being produced. /tmp still able to exports.
slc:~ # exportfs /usr/sbin/rpc.mountd: no process killed /usr/sbin/rpc.pcnfsd: no process killed /usr/sbin/rpc.nfsd: no process killed re-exported file systems
-- =========================================== __ _ Juergen Braukmann juergen.braukmann@gmx.de| -o)/ / (_)__ __ ____ __ Tel: 0201-743648 dk4jb@db0qs.#nrw.deu.eu | /\\ /__/ / _ \/ // /\ \/ / ===========================================_\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Jack Barnett wrote:
I changed my shell in /etc/passwd, which I type the path to it wrong, now when I try and log in, it gives me an error saying I don't have a valid shell and then disconnects the sesssion. The problem is, well the machine is in a remote area, and I don't have physically access to it. I tried rlogin in which doesn't work either. Any ideas?
After all the suggestions, one important lesson was not menioned: *NEVER* LOGOUT AFTER CHANGING SOMETHING IN THE PASSWORD FILE. DO AN EXTRA LOGIN FIRST TO SEE IF ALL IS OK. Koos Pol ---------------------------------------------------------------------- S.C. Pol T: +31 20 3116122 Systems Administrator F: +31 20 3116200 Compuware Europe B.V. E: koos_pol@nl.compuware.com Amsterdam PGP public key available -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
----- Original Message -----
From: Koos Pol
Jack Barnett wrote:
I changed my shell in /etc/passwd, which I type the path to it wrong,
now
when I try and log in, it gives me an error saying I don't have a valid shell and then disconnects the sesssion. The problem is, well the machine is in a remote area, and I don't have physically access to it. I tried rlogin in which doesn't work either. Any ideas?
After all the suggestions, one important lesson was not menioned: *NEVER* LOGOUT AFTER CHANGING SOMETHING IN THE PASSWORD FILE. DO AN EXTRA LOGIN FIRST TO SEE IF ALL IS OK.
Yea I know that. 50 things where going on at the time, and I though I could squeeze some extra time out of the day if I started make, edited either thing, then do something else while waiting for it to finish compiling. It was stupid of me. Even when I was doing it, I thought to myself, "Your going to forget about the changes, logout, do something else then in 2 hours when you need to do something on the system you will be screwed" I push that 'common sense' voice down and told it to shut the hell up. From now on though I will pay full attenation and listen carefully to that little voice. Most of the time that little voice knows more of what is going on then myself : ) I am a shell junkie and always tring out differant types of shells, I have probably did this 10-20 times, but from some reason I just had a glitch in me yesterday that pervented me from accepting input from the common sense part of my brain. I will try and patch it up with allot of strong coffee today. At least I got a good war story out of it. Thanks to everyone who replied, the problem has been resolved and couldn't of done it without you all. Jack
Koos Pol ---------------------------------------------------------------------- S.C. Pol T: +31 20 3116122 Systems Administrator F: +31 20 3116200 Compuware Europe B.V. E: koos_pol@nl.compuware.com Amsterdam PGP public key available
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (9)
-
alex@physical36.chem.ufl.edu
-
fountai@hursley.ibm.com
-
grtoft@yahoo.com
-
jbarnett@axil.netmate.com
-
juergen.braukmann@ruhr-west.de
-
koos.pol@nl.compuware.com
-
nixien@pd.jaring.my
-
ryagatich@csn1.com
-
weberdr@bellsouth.net