Re: /var filled up and can't login locally or remotely
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Hannah Schroeter wrote: Hi! On Wed, May 10, 2006 at 04:17:11PM +0200, Marian Hettwer wrote: Even if you use the bash-static package, bash gets installed into /usr/local/bin (IIRC) and you may not have /usr while being in single user mode. The latter should not really be a problem. init prompts for the shell to execute anyway if you boot into single user, so you can say /bin/ksh then even if root's shell were changed. That's right too. Forgot about that :) However that point of mine isn't meant to imply that it were a good idea or necessary to change root's shell. I just plain think it's not a good idea. Period :) sudo works just fine. ACK. regards, Marian iD8DBQFEYu/ngAq87Uq5FMsRAs++AJ4/PBDggMbUp6YxVsXmdBGZ0XZDSQCePxWU HbdnAeVkVQVP4RjgIX08d88= =DA2F -END PGP SIGNATURE-
Re: /var filled up and can't login locally or remotely
On Wed, May 10, 2006 at 12:40:28PM +0700, Tito Mari Francis Esca?o wrote: | I got me a 3.8 box as gateway with bash as root's default shell. The | pf logs filled up the /var partition and bash complained about not | being able to load libiconv which I believe is a dependency of bash. | With the failure of loading libiconv, I can't login on the gateway box | and I can't login remotely via SSH. I tried rebooting to single user | but the shell provided (is that ksh or csh?) doesn't seem to change | what root's default shell should be. | Is there a way I can get thru this without replacing the gateway | server and not reinstalling OpenBSD 3.8 from scratch? Thanks! Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. That being said, you could try booting bsd.rd (you did install that, right ?) and fix your issue from the shell it provides. Otherwise, boot from some install medium (CD/floppy/network/whathaveyou) and go from there. And why would you change to bash ? For root !? ksh provides most of what bash has. And if you really really really need bash for all the bashisms, dont do that stuff as root. Cheers, Paul 'WEiRD' de Weerd -- [++-]+++.+++[---].+++[+ +++-].++[-]+.--.[-] http://www.weirdnet.nl/ [demime 1.01d removed an attachment of type application/pgp-signature]
Re: /var filled up and can't login locally or remotely
reboot in single mode (boot -s) manually mount your partitions and delete unneeded trash :) Tito Mari Francis Escaqo wrote: I got me a 3.8 box as gateway with bash as root's default shell. The pf logs filled up the /var partition and bash complained about not being able to load libiconv which I believe is a dependency of bash. With the failure of loading libiconv, I can't login on the gateway box and I can't login remotely via SSH. I tried rebooting to single user but the shell provided (is that ksh or csh?) doesn't seem to change what root's default shell should be. Is there a way I can get thru this without replacing the gateway server and not reinstalling OpenBSD 3.8 from scratch? Thanks!
Re: /var filled up and can't login locally or remotely
Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. My 2 cents, -- Giancarlo Razzolini Linux User 172199 Moleque Sem Conteudo Numero #002 Slackware Current OpenBSD Stable Snike Tecnologia em Informatica 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: /var filled up and can't login locally or remotely
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, Giancarlo Razzolini wrote: Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell There is absolutely no reason to change root's shell. There is even no reason at all to work as root. Use sudo, or even su -m, or execute bash after you became root. Even if you use the bash-static package, bash gets installed into /usr/local/bin (IIRC) and you may not have /usr while being in single user mode. static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. You might consider leaving root untouched... regards, Marian iD8DBQFEYfXlgAq87Uq5FMsRAsqkAKDHnGW/2u+zvW/jRpqk1XSaHeNH0wCghnnv R1FTuxp8v+eiICa6TA8zTAo= =x40p -END PGP SIGNATURE-
Re: /var filled up and can't login locally or remotely
Hi! On Wed, May 10, 2006 at 04:17:11PM +0200, Marian Hettwer wrote: [...] Changing the root shell doesn't hurt. But you have to install your shell There is absolutely no reason to change root's shell. There is even no reason at all to work as root. Use sudo, or even su -m, or execute bash after you became root. Even if you use the bash-static package, bash gets installed into /usr/local/bin (IIRC) and you may not have /usr while being in single user mode. The latter should not really be a problem. init prompts for the shell to execute anyway if you boot into single user, so you can say /bin/ksh then even if root's shell were changed. However that point of mine isn't meant to imply that it were a good idea or necessary to change root's shell. sudo works just fine. [...] Kind regards, Hannah.
Re: /var filled up and can't login locally or remotely
On Wed, May 10, 2006 at 10:50:14AM -0300, Giancarlo Razzolini wrote: Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. My 2 cents, If you change it, fine. But don't tell others that this is not a problem. It can be a very big one if a critical box is 500km away in some datacenter and your remote upgrade failed because you removed all packages without thinking that you still need to keep bash... If you don't believe me that these things happen, search the archive. Btw: the static flavor was removed: http://www.openbsd.org/cgi-bin/cvsweb/ports/shells/bash/Makefile.diff?r1=1.34r2=1.35f=h Tobias -- Giancarlo Razzolini Linux User 172199 Moleque Sem Conteudo Numero #002 Slackware Current OpenBSD Stable Snike Tecnologia em Informatica 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: /var filled up and can't login locally or remotely
On 5/10/06, Giancarlo Razzolini [EMAIL PROTECTED] wrote: Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. As others have said there is no reason to change root's shell. And to expand upon that it's good practice to KISS. It's much easier to avoid problems and to fix them when they happen if as little is changed to root and the default system files as possible. My 1/2 cent. Greg -- OpenBSD User 782012
Re: /var filled up and can't login locally or remotely
Greg Thomas wrote: On 5/10/06, Giancarlo Razzolini [EMAIL PROTECTED] wrote: Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. As others have said there is no reason to change root's shell. And to expand upon that it's good practice to KISS. It's much easier to avoid problems and to fix them when they happen if as little is changed to root and the default system files as possible. As good example to help understand this in practice is just like this. You install your package bash-static, you think you are clever, fine. Then time pass, you work with someone else, a new release come out, you need to upgrade that box, but it happen to be remote. You forgot that you replace the default shell as you didn't document your changes, or your co worker didn't know you did this. Then you go as usual and follow the GREAT upgrade from Nick for remote upgrade, remove the packages not needed without thinking really. Your great BASH-Static is gone! Then you continue your upgrade after the kernel install, reboot your box and BANG! Great your box still work with the new kernel, but hey, you can't login anymore there can you. You have no more BASH shell on your system. So, having the default shell replace from the default install is A VERY bad idea! If you don't believe me. Search the archive and this happen to people very knowledgeable. It will bit you one day for sure. That's just one example, or you can think of this as well, you install BASH-static right. Then you use packages update because you want the latest of BASH without thinking as well. Sure it work, but then you new updated version is NOT static in that case and then the first time you system have problem, well again library as missing, etc. Many example comes to mind if you think about it. Use BASH for the users if you want, but leave the default root alone. You have no idea all the trouble you will save yourself. Daniel
Re: /var filled up and can't login locally or remotely
Daniel Ouellet wrote: As good example to help understand this in practice is just like this. You install your package bash-static, you think you are clever, fine. Then time pass, you work with someone else, a new release come out, you need to upgrade that box, but it happen to be remote. You forgot that you replace the default shell as you didn't document your changes, or your co worker didn't know you did this. Then you go as usual and follow the GREAT upgrade from Nick for remote upgrade, remove the packages not needed without thinking really. Your great BASH-Static is gone! Then you continue your upgrade after the kernel install, reboot your box and BANG! Great your box still work with the new kernel, but hey, you can't login anymore there can you. You have no more BASH shell on your system. So, having the default shell replace from the default install is A VERY bad idea! If you don't believe me. Search the archive and this happen to people very knowledgeable. It will bit you one day for sure. That's just one example, or you can think of this as well, you install BASH-static right. Then you use packages update because you want the latest of BASH without thinking as well. Sure it work, but then you new updated version is NOT static in that case and then the first time you system have problem, well again library as missing, etc. Many example comes to mind if you think about it. Use BASH for the users if you want, but leave the default root alone. You have no idea all the trouble you will save yourself. Daniel I use bash for personal reasons. I use sudo too. I don't see this as a big problem. I know that people forget to check the packages before an upgrade. But hey, this might break other things as well. Not critical as the shell, but might break. Further more, all my upgrades are done locally. I do not have the luxury of having a remote serial console with those nasty pci cards that can put even the BIOS to go through the serial. I can live with it. Will not recommend people anymore to change the root shell, but don't see any serious reason to not, if you are a zealous system admin. My 2 cents, -- Giancarlo Razzolini Linux User 172199 Moleque Sem Conteudo Numero #002 Slackware Current OpenBSD Stable Snike Tecnologia em Informatica 4386 2A6F FFD4 4D5F 5842 6EA0 7ABE BBAB 9C0E 6B85 [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: /var filled up and can't login locally or remotely
the shell, but might break. Further more, all my upgrades are done locally. I do not have the luxury of having a remote serial console with those nasty pci cards that can put even the BIOS to go through the serial. I can live with it. Will not recommend people anymore to change Who said you need to have serial console to do remote upgrades. Yes it might be nice, but hey, I have a truck load of servers without remote console access and I sure upgrade them remotely as well without a problem. I just did it again for 3.9 and because I always use one service per servers, like mail, or dns, or smtp, or www, etc. One applications per servers, making the upgrade is so easy and doing remote, the first one take me more time, but after that, may be 15 to 20 minutes max each. And sometimes, I do multiples at once. So easy! You got to love OpenBSD! Regards, Daniel
Re: /var filled up and can't login locally or remotely
Tobias Ulmer wrote: On Wed, May 10, 2006 at 10:50:14AM -0300, Giancarlo Razzolini wrote: Paul de Weerd wrote: Don't change root's shell. It's set to a static shell (/bin/ksh these days) for a reason. Changing the root shell doesn't hurt. But you have to install your shell static. I use the bash-static from packages, and hadn't any problems. I think that booting in single and cleaning some trash, might solve the problem. Also you might want to consider installing the bash-static. My 2 cents, If you change it, fine. But don't tell others that this is not a problem. It can be a very big one if a critical box is 500km away in some datacenter and your remote upgrade failed because you removed all packages without thinking that you still need to keep bash... If you don't believe me that these things happen, search the archive. There's a more basic rule I like: KEEP IT SIMPLE, KEEP IT LEAN. The more stuff you slop into your system: ..The more stuff you have to keep up to date. ..The more complicated upgrades become. ..The more likely something will go wrong. ..The more things you have to worry about security holes in. ..The less often you will do updates/upgrades because it is difficult. ..The more ignorant you will look when confronted with a system without the slop. and so on... I doubt many people have had a non-responsive system and said to themselves, Gee, if only I had installed bash on it. Learn your base system. If you really NEED something, where you can say clearly why and what benefit there is to you that outweighs the risks, well, fine. But slopping your system with crud just to make it look like something else or just because you can is not a good idea. Nick.
/var filled up and can't login locally or remotely
I got me a 3.8 box as gateway with bash as root's default shell. The pf logs filled up the /var partition and bash complained about not being able to load libiconv which I believe is a dependency of bash. With the failure of loading libiconv, I can't login on the gateway box and I can't login remotely via SSH. I tried rebooting to single user but the shell provided (is that ksh or csh?) doesn't seem to change what root's default shell should be. Is there a way I can get thru this without replacing the gateway server and not reinstalling OpenBSD 3.8 from scratch? Thanks!
