Sponsored Content
Top Forums Shell Programming and Scripting Why `expect -D 1' does not work? Post 302208413 by dearvoid on Monday 23rd of June 2008 09:43:31 PM
Old 06-23-2008
Note that it does not work on my Redhat Linux 9, either
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

strange expect script behavior, or am i misunderstanding expect scripting?

Hello to all...this is my first post (so please go easy). :) I feel pretty solid at expect scripting, but I'm running into an issue that I'm not able to wrap my head around. I wrote a script that is a little advanced for logging into a remote Linux machine and changing text in a file using sed.... (2 Replies)
Discussion started by: v1k0d3n
2 Replies

2. Shell Programming and Scripting

Expect script doesn't work under crontab

Hi All, Using Expect script when I run it manually it works. But when I put the entry in crontab, the job is still running after 15 hours. The script was created as root. I don't think it's a permission issue. Any idea? This is what I have under root crontab... 00 18 * * 1-5... (4 Replies)
Discussion started by: samnyc
4 Replies

3. Shell Programming and Scripting

Expect: Beginner help with spawn and expect

Hello hello, did a quick search and didn't turn up anything helpful. I've got a book I'm sure has the answers, but I don't think I'll have time to finish it before this all has to work, so here goes~ if this isn't a good place to post and someone could direct me to another forum I'd appreciate... (1 Reply)
Discussion started by: Vryali
1 Replies

4. Shell Programming and Scripting

Need help with Expect script for Cisco IPS Sensors, Expect sleep and quoting

This Expect script provides expect with a list of IP addresses to Cisco IPS sensors and commands to configure Cisco IPS sensors. The user, password, IP addresses, prompt regex, etc. have been anonymized. In general this script will log into the sensors and send commands successfully but there are... (1 Reply)
Discussion started by: genewolfe
1 Replies

5. Shell Programming and Scripting

cant get a counter to work in bash scipt, this is calling expect script

I have looked high and low, tryed lots of diffrent things but cant get a simple counter to work right. what i need is to increase a count ever time it finishes the test, pass or fail. example TEST PASS 1, NEXT TEST PASS 2, I curently have set foo o while {$foo <=5} { incr foo puts... (1 Reply)
Discussion started by: melvin
1 Replies

6. Shell Programming and Scripting

Expect - Comparison of expect value and loop selection

Hello All, I am trying to automate an installation process using expect and sh script. My problem is that during the installation process the expected value can change according to the situation. For Example if this is a first time installation then at step 3 I'll get "Do you want to accept... (0 Replies)
Discussion started by: alokrm
0 Replies

7. Programming

Calling expect script inside another expect

Hi, Am very new to expect scripting.. Can You please suggest me how to call an expect script inside another expect script.. I tried with spawn /usr/bin/ksh send "expect main.exp\r" expect $root_prompt and spawn /usr/bin/ksh send "main.exp\r" expect $root_prompt Both... (1 Reply)
Discussion started by: Priya Amaresh
1 Replies

8. IP Networking

Discussion at work, would a router work pluging a cable in wan1 and lan1?

hi all. and sorry for the random question, but this sparkled a raging flame-war at work and i want more points of view situation a router, with linux of some sort, dhcp client requesting for ip in wan1 (as usual with wan ports) dhcp server listening in lan1, and assigning ip (as usual... (9 Replies)
Discussion started by: broli
9 Replies

9. Programming

Expect script returning string following a found expect.

I'm fairly new to scripting so this might not be possible. I am using Expect with Cisco switches and need to capture the string after finding the expect request. For example, when I issue "show version" on a Nexus switch, I'm looking to capture the current firmware version: #show version ... (0 Replies)
Discussion started by: IBGaryA
0 Replies

10. UNIX for Beginners Questions & Answers

Expect scripting issue, works interactively when doing commands in cli, does not work in script

Hi; problem may be obvious, simple but I have to say it is somehow not easy to locate the issue. I am doing some word extracting from multiline text. Interacting in CLI seems to work without issues. First step is to add multiline text to a variable. expect1.1> expect1.1> set... (2 Replies)
Discussion started by: aldowski
2 Replies
PROOFD(1)						      General Commands Manual							 PROOFD(1)

NAME
proofd - PROOF (The Parallel ROOT Facility) DESCRIPTION
Using PROOF (The Parallel ROOT Facility) one can analyze trees in parallel on a cluster of computers. The PROOF system consists of the proofd(1) from-end program which is started via inetd(8). proofd takes care of user authentication and overlays itself then with the desired version of the proofserv(1) executable. The proofserv(1) is a basically the same as the ROOT interactive module root(1), except that it reads its commands from a socket instead of from the terminal. Since it is a remote server it will not do graphics and therefore is not linked with any graphics libraries (Motif, X11, etc.). SETTING UP PROOF
Since you need to handle sensitive system files, you need to have root (the user, not the program!) privileges. Also, it's recommended that you read the appropriate man(1) pages first. These are inetd(8) (the internet daemon), sysklogd(8) and syslog(3) (the system logger dae- mon), and init(8) (the SYSV process control initializer). In other words: Be very VERY carefull when installing proofd There, I said it. And ofcourse, no warrenties what so ever. 1 Make sure every node has ROOT installed. We'll assume you installed the ROOT applications in <bindir> (e.g. /usr/bin) and the PROOF configuration files in files in <proofdir>/etc (e.g. /usr/share/root/etc). 2 The TCP port 1094 was allocated by IANA, ( www.iana.org <Iwww.iana.org> ), to rootd, so add to /etc/services the lines: proofd 1093/tcp rootd 1094/tcp 3 On each node, add to /etc/inetd.conf the lines: proofd stream tcp nowait root <bindir>/proofd proofd <proofdir>/proof rootd stream tcp nowait root <bindir>/rootd rootd -i You can substitute the <proofdir> with any directory that holds your PROOF configuration, for example /etc/root/proof. However, it should be shared among all nodes in the cluster. 4 Restart inetd or force it to re-read the config file: kill -1 <inetd pid> If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/inetd restart or whatever is appropriate for your system. 5 On the master node, add to /etc/syslog.conf the line: local5,local6.debug <proofdir>/log/proof.log and all slave nodes: local5,local6.debug @<master hostname> where <master hostname> is domain name of the master node. All PROOF syslog messages will be collected on the master node. Just make one node in the cluster the master, all others are slaves. 6 On all nodes, change the below lines in /etc/syslog.conf, *.info;mail.none;news.none;authpriv.none /var/log/messages to: *.info;local5,local6,mail.none;news.none;authpriv.none /var/log/messages 7 Create an empty <proofdir>/log/proof.log: echo "" > <proofdir>/log/proof.log 8 Restart syslogd or force it to re-read the config file: kill -1 <syslogd pid>. If you use SYSV init(8) scripts, you can probaly just do /etc/init.d/sysklogd restart or whatever is appropriate for your system. 9 Edit <proofdir>/etc/proof.conf to reflect your cluster configuration. See the example proof.conf file for more information. If you installed ROOT using some precompiled package (for example a Redhat Linux or a Debian GNU/Linux package), steps 2 to 4 may already be done for you. If you're running Linux, Steps 5 to 7 can be somewhat automated using the script proof-facility in <proofdir> of your distribution. This script uses syslog-facility(1), from the Linux syslog(1) distribution, and may run on other platforms as well - but no warrenties mind you! Step 9 is completely up to the user. EXAMPLE
That's it. To test PROOF try the following: root [1] gROOT->Proof("<master hostname>") root [2] gPROOF->Print() <shows information on the master and all active slave servers> root [3] .q FILES
<proofdir> The location of your PROOF data. In binary packages, like for Redhat LinuxI or Debian GNU/Linux, this will probably be /usr/share/root/proof. If you got a binary tar(1)-ball from the ROOT website, or a build it yourself without the static paths option, then this directory could be ROOTSYS/proof. However, you may set it to something else when starting your server. <proofdir>/etc This directory holds all the configuration files for your cluster(s). <proofdir>/etc/<cluster>.conf This is the cluster named <cluster> configuration file. See <proofdir>/etc/<cluster>.conf.sample for an example. <proofdir>/etc/motd This is Message-Of-The-Day file. See <proofdir>/etc/motd.sample for an example. <proofdir>/etc/noproof If this file is present, all PROOF services will be diabled. See <proofdir>/etc/noproof.sample for an example. <proofdir>/etc/proof.conf This is the PROOF configuration file. See <proofdir>/etc/proof.conf.sample for an example. ~/.rootnetrc.conf Configuration file for network access. Here you specify login names and pass word, so it MUST be read/write-able only by the user. See <proofdir>/etc/rootnetrc.conf.sample for an example. <proofdir>/log This directory holds the log files from the master and slaves. <proofdir>/log/proof.log Syslog(1) log file for PROOF. SEE ALSO
proofserv(1) , root(1) , rootd(1) More information can be found at the ROOT website: http://root.cern.ch <http://root.cern.ch> ORIGINAL AUTHORS
The ROOT team (see web page above): Rene Brun and Fons Rademakers COPYRIGHT
This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as pub- lished by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foun- dation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA AUTHOR
This manual page was written by Christian Holm Christensen <cholm@nbi.dk>, for the Debian GNU/Linux system (but may be used by others). ROOT
Version 3 PROOFD(1)
All times are GMT -4. The time now is 02:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy