12-06-2007
As you told I added in rc.local .
Here is my rc.local
#!/bin/sh -e
#
# rc.local
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
/opt/inadyn/bin/linux/inadyn
exit 0
But not working.What to do?
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hey !
I am running EWS-UX/V (Rel 4.2) on NEC EWS/4800/330 station and I am having problems rebooting my station : I am getting the following message on display : BOOT : PANIC : File size out of range.
According to user guide, this error is occuring when a file exceeding the limit and/or... (2 Replies)
Discussion started by: fredo
2 Replies
2. Solaris
When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error.
cannot find mis/krtld
boot error loading... (0 Replies)
Discussion started by: johncy_j
0 Replies
3. UNIX for Dummies Questions & Answers
Hi ,
I have some problems with my library when the sytem boot :
When HPUX is booting, HPUX and STAPE claim the drive initially. HPUX assigns an instance
number. The instance number is tied to the hardware path. Near the end of the boot, the ATDD driver claims the drive from
STAPE based... (1 Reply)
Discussion started by: delphine
1 Replies
4. Solaris
Hi I'd like to add a start up script to run at boot time.I think that pre solaris 10 you'd add it to /etc/init.d. But I'm using Solaris 10 now and it has this SMF config thing which I'm not sure whether I have to add a service to it or not.
Does anyone know how add a script at boot time on... (2 Replies)
Discussion started by: fishman2001
2 Replies
5. Ubuntu
Hello,
I'm writing a simple boot script that uses etc/init/script to run a called file from the .xinitrc file.
So the script goes as such.
{
start on runlevel
stop on runlevel
exec xinit
}
then that executes the .xinitrc content which then reads.
/usr/bin/python ... (2 Replies)
Discussion started by: hizzle
2 Replies
6. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
7. Solaris
I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD... (9 Replies)
Discussion started by: hemalsid
9 Replies
8. Red Hat
Hi, there is an incompatibility between my NIC and my Western Digital Powerline adapters which appears to cause autonegotiation to fail intermittently, most often following a reboot. Running the following Ethtool script will establish a connection immediately:
#!/bin/sh
# chkconfig: 345 85... (12 Replies)
Discussion started by: torley
12 Replies
9. Shell Programming and Scripting
Looking to automate some commands to run at boot and poweroff in a startup/shutdown script.
How do I place it on the system so that it will be run automatically?
I don't want to use cron, not quite specific enough, random times when I may boot or shutdown.
---------- Post updated at 10:47 PM... (8 Replies)
Discussion started by: 3therk1ll
8 Replies
10. Shell Programming and Scripting
Due to a bug in Debian Sid I'm currently having to run "alsactl init" at the command-line to start my sound card. This wasn't a big issue, but I though automating this simple task at boot would be more efficient. I made the following script in /etc/init.d/ and ran chmod +x on it:
... (5 Replies)
Discussion started by: Azrael
5 Replies
exit(1) User Commands exit(1)
NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps
SYNOPSIS
sh
exit [n]
return [n]
csh
exit [ ( expr )]
goto label
ksh
*exit [n]
*return [n]
DESCRIPTION
sh
exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of
the last command executed (an EOF will also cause the shell to exit.)
return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe-
cuted.
csh
exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the
expression expr.
The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches
for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to
jump to a label that occurs between a while or for built-in command and its corresponding end.
ksh
exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8
bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing
a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit
except for a shell which has the ignoreeof option (See set below) turned on.
return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the
least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return
is invoked while not in a function or a '.' script, then it is the same as an exit.
On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways:
1. Variable assignment lists preceding the command remain in effect when the command completes.
2. I/O redirections are processed after variable assignments.
3. Errors cause a script that contains them to abort.
4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari-
able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not
performed.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5)
SunOS 5.10 15 Apr 1994 exit(1)