Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 25 Apr 2016 12:16:34 +0000 (UTC)
From:      Mikhail Zakharov <zmey20000@yahoo.com>
To:        Matthias Apitz <guru@unixarea.de>,  "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org>
Subject:   =?UTF-8?Q?=D0=9E=D1=82=D0=B2:_talking_with_chat(1)_like_tool_to_a_socket?=
Message-ID:  <1886835680.795096.1461586594633.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <20160425100944.GA3789@c720-r292778-amd64>
References:  <20160425100944.GA3789@c720-r292778-amd64>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi Matthias,
Why don't you think about tcl-expect or empty.sourceforge.net tool to do th=
is interaction?

--
Mikhail Zakharov=20

    =D0=BF=D0=BE=D0=BD=D0=B5=D0=B4=D0=B5=D0=BB=D1=8C=D0=BD=D0=B8=D0=BA, 25 =
=D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2016 12:10 Matthias Apitz <guru@unixar=
ea.de> =D0=BF=D0=B8=D1=81=D0=B0=D0=BB(=D0=B0):
=20

=20


Hello,

In the GOD of modems and PPP I was used to use chat to talk and
initialize modems based on some send/expect scripts...

I would like to use the same logic of such script to talk to a remote
server (IP+port) which understands commands in text and does respond
with text.

Any idea before hacking the C-code of chat(1)?

Thanks

=C2=A0=C2=A0=C2=A0 matthias
--=20
Matthias Apitz, =E2=9C=89 guru@unixarea.de, =E2=8C=82 http://www.unixarea.d=
e/  =E2=98=8E +49-176-38902045
_______________________________________________
freebsd-questions@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org=
"

  
From owner-freebsd-questions@freebsd.org  Mon Apr 25 12:49:24 2016
Return-Path: <owner-freebsd-questions@freebsd.org>
Delivered-To: freebsd-questions@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 75693B1BD96
 for <freebsd-questions@mailman.ysv.freebsd.org>;
 Mon, 25 Apr 2016 12:49:24 +0000 (UTC)
 (envelope-from wattersm@watters.ws)
Received: from bsd1.tor1.watters.ws (bsd1.tor1.watters.ws [159.203.45.15])
 by mx1.freebsd.org (Postfix) with ESMTP id 59C9C13E6
 for <freebsd-questions@freebsd.org>; Mon, 25 Apr 2016 12:49:23 +0000 (UTC)
 (envelope-from wattersm@watters.ws)
Received: from mdct-dev27.dartcontainer.com (unknown [12.48.88.1])
 by bsd1.tor1.watters.ws (Postfix) with ESMTP id A40B245E8AE
 for <freebsd-questions@freebsd.org>; Mon, 25 Apr 2016 12:40:02 +0000 (UTC)
Subject: Re: Storage cluster advise, anybody?
To: freebsd-questions@freebsd.org
References: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu>
From: Michael Watters <wattersm@watters.ws>
Message-ID: <571E1022.3090004@watters.ws>
Date: Mon, 25 Apr 2016 08:40:02 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.7.1
MIME-Version: 1.0
In-Reply-To: <29462.128.135.52.6.1461352625.squirrel@cosmo.uchicago.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>;
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
 <mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Apr 2016 12:49:24 -0000

Have you looked at Lustre at all?  I've used it in the past and found it 
to be a stable, high performance file system.


On 04/22/2016 03:17 PM, Valeri Galtsev wrote:
> Dear Experts,
>
> I would like to ask everybody: what would you advise to use as a storage
> cluster, or as a distributed filesystem.
>
> I made my own research of what I can do, but I hit a snag with my
> seemingly best choice, so I decided to stay away from it finally, and ask
> clever people what they would use.
>
> My requirements are:
>
> 1. I would like to have one big (say, comparable to petabyte) filesystem,
> accessible on more than one machine, composed of disk space leftovers on a
> bunch of machines having 1 gigabit per second ethernet connections
>
> 2. It can be a bit slow, as filesystem one would need for backups onto it
> (say, using bacula or bareos), and/or for long term storage of large
> datasets, portions of which can be copied over to faster storage for
> processing if necessary. I would be thinking in 1-2 TB of data written to
> it daily.
>
> 3. It would be great to have it single machine failure/reboot resilient
>
> 4. metadata machines should be redundant (or at least backup medatada host
> should be manually convertible into master metadata host if fatal failure
> to master or corruption of its data happens)
>
>
> What I would like to avoid/exclude:
>
> 1. Proprietary commercial solutions, as:
>
> a. I would like to stay on as minimal budget as possible
> b. I want to be able to predict that it will exist for long time, and I
> have better experience with my predictions of this sort about open source
> projects as opposed to proprietary ones
>
> 2. Open source solutions using portions of proprietary closed source
> binaries/libraries (e.g., I would like to stay away from google
> proprietary code/binaries/libraries/modules)
>
> 3. Kernel level modifications. I really would like to have this
> independent of OS as much as I can, or rather available on multiple OSes
> (though I do not like Java based things - just my personal experience with
> some of them). I have a bunch of Linux boxes and a bunch of FreeBSD boxes,
> and I do not want to exclude neither of them if possible. Also, the need
> to have custom Linux kernel specifically scares me: Linux kernels get
> critical updates often, and having customizations lagging behind the need
> of critical update is as unpleasant as rebooting the machine because of
> kernel update is.
>
> I'm not too scared of a "split nature" projects: proprietary projects
> having open source satellite. I have mixed experience with those, using
> open source satellite I mean. Some of them are indeed not neglected, and
> even though you may be missing some features commercial counterpart has,
> some are really great ones: they are just missing commercial support, and
> maybe having a bit sparse documentation, thus making you to invest more
> effort into making it work, which I don't mind: I can earn my sysadmin's
> salary here. I would say I more often had good experience with those than
> bad one (and I have a list of early indications of potential bad outcome,
> so I can more or less predict my future with this kind of projects).
>
> <rant>
> I really didn't mean to write this, but I figure it probably will surface
> once I start getting your advices, so here it is. I did my research having
> my requirements in mind and came up with the solution: moosefs. It is not
> reviewed much, no reviews with criticism at all, and not much you can ("I
> could" I should say) find howtos about customizations, performance tuning
> etc. It installs without a hitch. It runs well, until you start stress
> writing a lot to it in parallel, then it started performing exponentially
> badly for me. Here is where extensive attempts to find performance tuning
> documentation faces lack of success. What made my decision to never ever
> use it in a future was the following. I started migrating data back from
> moosefs to local UFS (that is FreeBSD box) filesystem using rsync command.
> What I observed was: source files after they have been touched by rsync
> changed their timestamps. As if instead of creation timestamp it is an
> access timestamp on moosefs. This renders rsync from moosefs useless, as
> you can not re-run failed rsync, and you obliterate some of metadata of
> the source ("creation" timestamp). I wrote e-mail to sourceforge moosefs
> mail list, mentioning all this and the fact that I am using open source
> moosefs. Next day they replied asking whether I use version 3."this" or
> version 3."that", as they want to know in which of them they have a bug.
> Whereas latest open source version they have everywhere, including
> sourceforge is older version: 2.0.88.
> Basically, my decision was made. Sorry for venting it out here, but I
> figured, it will happen some moment when I will get your advises.
> </rant>
>
> Thanks a lot for all your advises!
>
> Valeri
>
> ++++++++++++++++++++++++++++++++++++++++
> Valeri Galtsev
> Sr System Administrator
> Department of Astronomy and Astrophysics
> Kavli Institute for Cosmological Physics
> University of Chicago
> Phone: 773-702-4247
> ++++++++++++++++++++++++++++++++++++++++
>
>
>
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1886835680.795096.1461586594633.JavaMail.yahoo>