From: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Tcl in your system...
Date: Tue, 29 Nov 2011 10:21:20 +0100 [thread overview]
Message-ID: <4ED4A410.3050001@alstadheim.priv.no> (raw)
In-Reply-To: <CA+czFiB-vo17b7XoaKX2b+Xycb9_vXCvUz3X-pTDx1Of+uZPMQ@mail.gmail.com>
Den 29. nov. 2011 06:03, skrev Michael Mol:
> On Mon, Nov 28, 2011 at 11:33 PM, Pandu Poluan<pandu@poluan.info> wrote:
>> Just wondering if anyone here ever use Tcl for scripting (i.e., automating
>> repetitive procedures) or even *gasp* serious programming.
> Not me, but Tcl is one of the best-represented langauges on the site I run.
>
I use it for small stuff (with expect) regarding keeping my cheap
consumer-grade routers/switches running. Those things usually have
either a telnet or ssh interface that allows me to
monitor/configure/reboot, but they are usually too ficle to be
programmed in any predictable way. Muddle through a problem manually,
and record the solution in an expect script to keep until next time.
Over the years I have accumulated several that are stable enough to run
unattended. Last couple of times that my most troublesome wifi-box got
alzheimers, it got rebooted automatically. Dynamic DNS (10+ hostnames)
and ADSL rebooting happens within 5 minutes of my ISP deciding to do
something weird. expectk brings a semblance of sanity.
No serious programming though. Did use exmh as my main mailclient until
~9 years ago. It is still being developed, look into that if you want an
example of Tcl in a largeish project.
next prev parent reply other threads:[~2011-11-29 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 4:33 [gentoo-user] Tcl in your system Pandu Poluan
2011-11-29 5:03 ` Michael Mol
2011-11-29 9:21 ` Håkon Alstadheim [this message]
2011-11-29 18:22 ` Paul Hartman
2011-11-29 16:10 ` Paul Hartman
2011-11-29 16:32 ` Albert W. Hopkins
2011-11-29 22:09 ` [gentoo-user] " Jörg Schaible
2011-11-29 23:43 ` Albert W. Hopkins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ED4A410.3050001@alstadheim.priv.no \
--to=hakon@alstadheim.priv.no \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox