Installing Emacs22 on Debian Etch
When I looked for an Emacs22 package for Debian Etch, I found that the regular Debian backports Web site at http://www.backports.org/ does not include a backport of this package. (The reason I looked for this version of Emacs was because of its network connection support by means of ELISP functions like make-network-process and open-network-stream. It also has a cua mode, which allows you to use the now-standard C-x, C-c and C-v key combinations for the standard operations.) Today I found that the Emacs Wiki Web site has a page about exactly this subject: http://www.emacswiki.org/cgi-bin/emacs-en/OnDebianEtch Following directions, Emacs22 was successfully installed and made the default. Details are as follows. 1. I worked as root, so I used the following to authenticate the package source hype.sourceforge.jp/f: # wget http://hype.sourceforge.jp/f/A7F20B7E.gpg -O- | apt-key add - 2. As directed, I added the following lines to /etc/apt/sources.list: deb http://hype.sourceforge.jp/f etch backports deb-src http://hype.sourceforge.jp/f etch backports 3. I used aptitude (rather than the various apt-get commands recommended by the aforementioned Web page). As usual, it complains when activated for the first time after adding another source. I restarted it, and the complaint went away. When running update, aptitude recommended that several packages (for example, PHP5 related ones) be upgraded. I blocked everything by the F command (Forbid Upgrade), and selected the Emacs22 packages. aptitude informed about a buffer overflow error, which was already fixed in the Debian Lenny version of Emacs22. I allowed it to be installed. Installation proceeded without further incidents. 4. After installation, I checked which version of emacs is in effect using: # update-alternatives --display emacs Since I found it to be pointing at /usr/bin/emacs22-x rather than /usr/bin/emacs21-x, no further action was needed. --- Omer -- MCSE - acronym for Minesweeper Consultant & Solitaire Expert. (Unknown) My own blog is at http://www.zak.co.il/tddpirate/ My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
RE: ban IP from ssh after X numbr of times of bad login
FYI
> Date: Fri, 28 Dec 2007 12:15:41 +0200> From: [EMAIL PROTECTED]> To: [EMAIL
> PROTECTED]> CC: linux-il@cs.huji.ac.il> Subject: Re: ban IP from ssh after X
> numbr of times of bad login> > Hi Hetz,> > Look no further than denyhosts
> (http://denyhosts.sourceforge.net). This daemon > monitors your logs and
> updates your /etc/hosts.deny file.> > baruch> > On Fri, Dec 28, 2007 at
> 11:46:07AM +0200, Hetz Ben Hamo wrote:> > Hi,> > > > I'm looking at my daily
> logwatch mail and I find something like this:> > > > sshd:> > Authentication
> Failures:> > unknown (200.110.185.21): 129 Time(s)> > > > Of course, I can
> move the SSH port to something else, but I'm looking> > for a more elegant
> solution.> > > > I want to have my Linux machine an ability to let ssh login
> at the> > same port, but only allow an IP to test login 3 times.> > After
> that, if it fails, this IP should be banned from SSH to this machine..> > > >
> Is there such a PAM module or any program/library/config which can do> >
> this, or do I need to "roll my own"?> > > > Thanks,> > Hetz> > > > -- > >
> Skepticism is the lazy person's default position.> > my blog (hebrew):
> http://benhamo.org> > > >
> => > To
> unsubscribe, send mail to [EMAIL PROTECTED] with> > the word "unsubscribe" in
> the message body, e.g., run the command> > echo unsubscribe | mail [EMAIL
> PROTECTED]> > > > -- > ~. .~ Tk Open Systems>
> =}ooO--U--Ooo{=>
> - [EMAIL PROTECTED] - tel: +972.2.679.5364, http://www.tkos.co.il -> >
> => To
> unsubscribe, send mail to [EMAIL PROTECTED] with> the word "unsubscribe" in
> the message body, e.g., run the command> echo unsubscribe | mail [EMAIL
> PROTECTED]>
_
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Re: Find process id of background ssh?
On Dec 26, 2007 5:13 PM, linux. il <[EMAIL PROTECTED]> wrote: > > > > > > > Hi List. > > > > > > I'm writing a script to automate some system maintenance tasks, and I > > > want to connect over SSH to several remote computers and do stuff on > > > them. I'm using ssh -f to background ssh so I can run the same operation > > > on multiple machines in parallel, otherwise it will be too slow - the > > > maintenance job may take up to a few minutes to run and the script is > > > not supposed to be fully automatic: a human is to monitor the process. > > > > > > But I don't want just to fire and forget the SSH processes - I want to > > > exit from the script only when all the SSH processes have completed. I > > > can do that by monitoring the process ids of the background SSH > > > processes, if I could know them - which I'm having a difficult time > > > detecting. > > > > > > I'm writing in bash, and optimally it would be something like this: > > > > > > for server in 1 2 ...; do > > >ssh -f [EMAIL PROTECTED] 'run maintenance task' > > >pids="$pids $(getSSHpid)" > > > done > > > > > > while kill -0 $pids 2>/dev/null; do echo "Waiting.."; sleep 1; done > > > > > > but I didn't manage to find a way to get the process id of the ssh > > > process after it goes to background, other the 'ps'ing for it. > > > > > > How can I go about doing this? > > > > > > -- > > > > > > Oded > > > > > Sorry for OT, but some kind of distributed shell seems me more > suitable for this task - > http://www.linux-mag.com/microsites.php?site=business-class-hpc&sid=build&p=4658 > > You might as well check http://www.csm.ornl.gov/torc/C3/ -- Cheers, Maxim Veksler "Free as in Freedom" - Do u GNU ? = To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
