Re: running script files.
Thanks everyone for helping me out! Another quick question, when i boot, i see all kinds of cdrom drives being probed at. like mcd, aztcd, sony, gscd etc. I have looked at my /lib/modules, and the only cdrom module avail. is sbpcd.o. The probing of the cdroms delays the booting of debian to 2 to 3 min. Does it mean i have recompile the kernel to remove these things? Any help is deeply appreciated. Andre
Re: Script Files
At 06:29 PM 3/5/97 -0600, Pete Poff wrote: Hi, I have installed just base of Debian. I have not added any extra software. But I have added Envy 1.0 which is a type of mud. I'm trying to run it and to start it, I have to run the startup script. I'm getting all kinds of errors when I running it. Just to make sure I'm doing it right, I type '. startup' right? Also if someone could take a look at the startup file I have attached and maybe tell me whats is wrong, it would really make my day. Hi Pete :) Gosh, this question almost belongs in rec.mud.admin, doesn't it? :) I run a modified Rom2.4 on a Debian box and they are similar, as you know :) I'm not sure if tcsh is in the base package, but I'm thinking that it is. Your (and my) startup files are c-shell files and if you try to run it from a bash shell it will not work. Try typing tcsh from the prompt and see if you get a new shell. If not, then you may want to get the csh-x.x.etc.deb file from the ftp site and run it. I'm pretty sure you don't have to, though. Hell, let me check... Ok, tcsh works. So you want to tcsh, then go to where your startup is and type ./startup --- the ampersand runs the mud as a background process, which is what you want to do. A ps- ax will show you both the startup script and the envy running at all times. Once began, the startup script actually controls the mud environment, including reboots, shutdowns, etc. Hope this helps :) I might drop by your mud once you get it up... Regards, Kendrick Ataraxia of Planet Zero 205.219.244.25 9000 -- Kendrick Myatt mailto:[EMAIL PROTECTED]
Re: Script Files
Kendrick, thanks for you help, but before I got your message, I found and installed the csh shell. I got rid of the error message when trying to run it, but when I do, it just dumps a core and doesn't work. I don't know why but, could be because I compiled it on a different system then moved it over compiled. I'm going to get the gcc compiler on my computer then recompile it and try again. I have the mud on-line now, it's on an account I pay for, it's telnet.cyberconinc.com 4000. Thanks and if I don't get it working, I may ask a few more questions. Pete Poff P.S. To all that have helped and answered my questions that you. You have gotten me on-line from my unix not my MS-DOS. Thanks again. Pete Poff---AKA---BlackJack Personal E-Mail Address: [EMAIL PROTECTED] Kyron E-Mail Address:[EMAIL PROTECTED] ___ ||Blackjack|| | | |Kyron God, | |Coder and Builder. | | | | telnet.cyberconinc.com| | 4000| |___|
Script Files
Hi, I have installed just base of Debian. I have not added any extra software. But I have added Envy 1.0 which is a type of mud. I'm trying to run it and to start it, I have to run the startup script. I'm getting all kinds of errors when I running it. Just to make sure I'm doing it right, I type '. startup' right? Also if someone could take a look at the startup file I have attached and maybe tell me whats is wrong, it would really make my day. Thanks for helping me, Pete Poff Pete Poff---AKA---BlackJack Personal E-Mail Address: [EMAIL PROTECTED] Kyron E-Mail Address:[EMAIL PROTECTED] ___ ||Blackjack|| | | |Kyron God, | |Coder and Builder. | | | | telnet.cyberconinc.com| | 4000| |___| #! /bin/csh -f # Written by Furey. # With additions from Tony. # With changes from Kahn. # Set the port number. set port = 6001 if ( $1 != ) set port=$1 # Change to area directory. cd ../area # Set limits. nohup nice +6 limit stack 1024k if ( -e shutdown.txt ) rm -f shutdown.txt while ( 1 ) # If you want to have logs in a different directory, # change the 'set logfile' line to reflect the directory name. set index = 1000 while ( 1 ) set logfile = ../log/$index.log if ( ! -e $logfile ) break @ index++ end # Run envy. ../src/envy $port ! $logfile if ( -e core ) then mv core ../src/$index.core endif # Restart, giving old connections a chance to die. if ( -e shutdown.txt ) then rm -f shutdown.txt exit 0 endif sleep 15 end
Re: Script Files
I have installed just base of Debian. I have not added any extra software. But I have added Envy 1.0 which is a type of mud. I'm trying to run it and to start it, I have to run the startup script. I'm getting all kinds of errors when I running it. Just to make sure I'm doing it right, I type '. startup' right? Also if someone could take a look at the startup file I have attached and maybe tell me whats is wrong, it would really make my day. You can run a script with '. startup' if the shell you are using is a Bourne shell derivative (sh, bash, ksh, ash) and the script is also written in a Bourne shell derivative. But this runs the script in the current environment, which might no be what you want. Your script, though is written in csh and can only be run by csh or tcsh, which are not in base, but in the section called 'shells'. Get either the csh or tcsh debian package and install it on your system with dpkg -i csh_5.26-8.deb or dpkg -i tcsh_6.06-10.deb Then, you can just run the script by typing its name on the command line. -- Michel Beland [EMAIL PROTECTED] professionnel de recherchetel: (514)369-5223 fax: (514)369-3880 CERCA (CEntre de Recherche en Calcul Applique) 5160, boul. Decarie, bureau 400(423), Montreal (Quebec), Canada, H3X 2H9
Re: running script files.
On Thu, 7 Feb 2036, A. M. Varon wrote: Hi to all, It seems that shell scripts i have made in my debian distrib. doesn't run. you need to put ./ in front in order for it to execute. i have chmod the script it to be executable, my bash shell is in /etc/shells, and my first line in my shell script is #!/bin/bash. what seems to be the problem? lshell? Thanks in advance, andre The problem isn't in your scripts at all. It is in the path set up for your shell. Once you log in, type the command ``set''. This will list a number of lines of variables that are defined for your login shell. One will look like, path(/home/sstanley/bin /usr/local/bin /usr/bin /bin /usr/bin/X11 /usr/sbin . /sbin) or like PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11 depending on whether you use tcsh or bash for your login shell. In any case, this is the list of directories that are searched when you type a command. The thing to notice is that you need the ``.'' in the path for it to find commands in the current directory (as in the first example above). Otherwise, you have to type ./Command_Name to specify explicitly where the command is. This can be set by editing the .tcshrc (if you use tcsh) or .bash_profile (for bash) files in your root directory to add ``.'' to your path. There is likely a ``set path= ...)'' command already in this file. Just edit it to add ``.''. Once the file is changed, log out and then log back in. Everything should work fine then If this is not relatively clear, send me email Scott
Re: running script files.
On Feb 7, A. M. Varon wrote It seems that shell scripts i have made in my debian distrib. doesn't run. you need to put ./ in front in order for it to execute. Bash will only execute programs which are specified in your path (to see what your path is, type echo $PATH). If . is not in your path, then it won't execute programs in the current directory. If you want to be able to execute things in the current directory without specifying the ./ before it, then try this (in bash): export PATH=$PATH:. This will add . to the end of your path. To do this every time you log in (without retyping it every time), put that line in ~/.bashrc. This is a script that is run every time a shell is started by you, and in particular, it is run when you log in. -- - John Larkin - [EMAIL PROTECTED] - http://aij.st.hmc.edu/~jlarkin
Re: running script files.
John == John T Larkin [EMAIL PROTECTED] writes: John On Feb 7, A. M. Varon wrote It seems that shell scripts i have made in my debian distrib. doesn't run. you need to put ./ in front in order for it to execute. John Bash will only execute programs which are specified in your John path (to see what your path is, type echo $PATH). If . John is not in your path, then it won't execute programs in the John current directory. If you want to be able to execute things John in the current directory without specifying the ./ before John it, then try this (in bash): export PATH=$PATH:. This will John add . to the end of your path. To do this every time you John log in (without retyping it every time), put that line in John ~/.bashrc. This is a script that is run every time a shell John is started by you, and in particular, it is run when you log John in. -- - John Larkin - [EMAIL PROTECTED] - John http://aij.st.hmc.edu/~jlarkin Bash will, by default, execute /etc/profile then ~/.bash_profile if it is a login shell, but it won't execute .bashrc. That is executed on a non-login invocation. As .bashrc has lots of stuff which one generally wants on logins as well, usually these lines appear in .bash_profile: # Now read from .bashrc, if it exists if [ -f ~/.bashrc ]; then source ~/.bashrc; fi That will ensure that all aliases, etc. are set up correctly. The info node Bash Startup Files contains more information. Cheers, Graeme -- | Graeme A Stewart, pgp public key finger [EMAIL PROTECTED]| | Key fingerprint = AF C7 BF A4 52 D5 3C 3B 17 A5 62 43 DA 15 E8 97 | | Keep a good head, and always carry a lightbulb. Dylan |
running script files.
Hi to all, It seems that shell scripts i have made in my debian distrib. doesn't run. you need to put ./ in front in order for it to execute. i have chmod the script it to be executable, my bash shell is in /etc/shells, and my first line in my shell script is #!/bin/bash. what seems to be the problem? lshell? Thanks in advance, andre
