Re: bash can not find most of my commands
Alokat wrote: On 02/22/11 17:49, Paul Macdonald wrote: On 22/02/2011 16:40, Alokat wrote: Hi, I have changed my shell from csh to bash ... But after that I have to call reboot like /sbin/reboot. How can I change that without changing the shell. :) don't change your root shell! csh is in the base system so is safe and will always* work, bash is a port and gets updated regularly, there's been at least one occasion when my bash upgrade failed and i couln't login as root. very frustrating.. I just get used to changing to bash after that, much safer! Paul. Paul has satisfied me. I have changed back to csh. Thank for help. Regards, alokat And if you use bash after login or anytime, your original problem remains. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: [SSHd] Increasing wait time?
David Kelly wrote: On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote: Is there a way to configure SSHd, so that the wait time between login attempts increases after X failed tries? Not that I know of. You should look into denyhosts (in the ports) it works well and even has a RBL feature to block some of these script kiddies proactively. Unfortunately, these attempts have become a fact of life. I probably get 20 - 30 attempts a day between my various servers. Depending on how you use ssh from external systems you could add firewall rules to disallow all but known sources. I used portsentry several years ago which is a realtime portscan blocker. It would trigger on this type of ssh portscan for sure. One problem is that it blocks using firewall rules, hosts.deny etc... and would have to be actively maintained. Meaning: I cleaned these entries once a week. I am not sure it is ported to BSD either. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [SSHd] Increasing wait time?
Doug Hardie wrote: On May 6, 2008, at 10:57, Randy Ramsdell wrote: David Kelly wrote: On Tue, May 06, 2008 at 09:31:15AM -0800, Beech Rintoul wrote: Is there a way to configure SSHd, so that the wait time between login attempts increases after X failed tries? Not that I know of. You should look into denyhosts (in the ports) it works well and even has a RBL feature to block some of these script kiddies proactively. Unfortunately, these attempts have become a fact of life. I probably get 20 - 30 attempts a day between my various servers. Depending on how you use ssh from external systems you could add firewall rules to disallow all but known sources. I used portsentry several years ago which is a realtime portscan blocker. It would trigger on this type of ssh portscan for sure. One problem is that it blocks using firewall rules, hosts.deny etc... and would have to be actively maintained. Meaning: I cleaned these entries once a week. I am not sure it is ported to BSD either. Another option is to change the port SSH uses to some very unusual port. I do this on all the systems I use and change the port settings in ssh.conf and sshd.conf. This approach works if you don't have lots of users using SSH as it does require some sophistication to work with it. Since I have only 3 people who can use SSH it works great for me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Yeah this also works well. I just shy away from security through obscurity. However, I also moved ssh to port 40001 or so and monitored SYN packets. I never logged an attempt to log in accept auth'd users. It was never port scanned for ssh specific either. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freebsd filesystem ( hard reboot )
We started using FreeBSD for some network monitoring, but have found that a hard reboot forces us to answer filesytem questions on boot. Is there a way to mount each filesystem without this? Or how can we use FreeBSD in a remote location without needing to intervene in situatutions like this? Thanks, Randy Ramsdell Unix Systems Administrator ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd filesystem ( hard reboot )
Bart Silverstrim wrote: Randy Ramsdell wrote: We started using FreeBSD for some network monitoring, but have found that a hard reboot forces us to answer filesytem questions on boot. Is there a way to mount each filesystem without this? Or how can we use FreeBSD in a remote location without needing to intervene in situatutions like this? What's causing the hard reboots? Is it on a UPS? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Well any number of things, but the most recent was a prolonged power outage. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd filesystem ( hard reboot )
Vince wrote: Randy Ramsdell wrote: We started using FreeBSD for some network monitoring, but have found that a hard reboot forces us to answer filesytem questions on boot. Is there a way to mount each filesystem without this? Or how can we use FreeBSD in a remote location without needing to intervene in situatutions like this? This is unusual in my experience, part of the charm of FreeBSD for me is how rarely I have had to interact with fsck thanks to the whole background fsck thing. What version of FreeBSD are you using? Assuming a 5.x or later since you say you've started to use FreeBSD. I am fairly sure it is v6.2 What is the value of background_fsck in /etc/rc.conf ? This isn't set. Was is supposed to be? So far, I have only installed applications we need. And everything seem fine except the reboot issue. This will be an offsite system so I do not want human intervention on boot for power outages or hard reboots. You can also try setting fsck_y_enable=YES in rc.conf (this will do fsck -y if the initial preen fails.) I will use this. Do you mean by try, that this will work? I assume so. Thanks Vince! Oh, Is there a way to not receive 2 messages for every reply to this thread? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Freebsd filesystem ( hard reboot )
Robert Huff wrote: Randy Ramsdell writes: What is the value of background_fsck in /etc/rc.conf ? This isn't set. Was is supposed to be? So far, I have only installed applications we need. And everything seem fine except the reboot issue. I'm going to jump in here. Based on what you've said, it sounds like: the system was running there was power outage, the system did not have a UPS when the system rebooted, fsck complained but nothing was done about the errors Let me clarify. All our servers are on UPSes, however the power outage outlasted the UPSes. That is why I stated prolonged power outage. Fsck did complain, but everything was fixed as I sat there and dealt with it. We do not want to deal with it in an offsite location and that is why this thread. IF THAT'S TRUE ... ... then the seems in your description is applicable, and should be a red flag. Get someone to the system, reboot it into single user mode, and run (and re-run) fsck until it runs without error. (Answer 'y' to all prompts.) This should be done whenever the file system is not shutdown cleanly. The filesystem is fine. Our set up just does not recover gracefully on hard reboots. (And consider a UPS, even it it only keeps the system alive for the few minutes necessary for a clean shutdown.) Is a dirty file system causing the reboots? No. a power prolonged power failure caused the last shutdown. Possibly; wiser heads than mine would have to lay out scearios. But it may also be responsible for other damage, more subtle but equally unpleasant. A fix is available. Use it. I understand this will not be easy, and I sympathize. Balance that pain against the small but non-trivial chance to catastrophic data loss, and choose wisely. Robert Huff Thanks for the reply. I think I will just set the rc.conf variable to answer Y to fsck questions unless there is a better way. A side note, this system has been hard shutdown two times and each time required intervention. We also use several Linux system ( reiserfs and ext3 ) and raely do I have to interact with the systems on reboot. There is a differnce and I am in the fisrt stages trying to understand this. PS. I am confused about why so many people are replying to the list and my personal e-mail. This one was sent to me only. Others were sent to me and the list. Actually, every other reply. Is this normal for the list as I am new as of today? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
