Visit Our UNIX and Linux User Community

Operating Systems Solaris error in jumpstart while cretaing rules.ok with ./check Post 302357381 by kumarmani on Tuesday 29th of September 2009 03:29:45 PM
Old 09-29-2009
error in jumpstart while cretaing rules.ok with ./check

Hi Gurus,

When i am running the ./check and i am getting below error

Code:
Error in files "rules", line 92 
     hostname sample_host - host_class set_root_pw
Error: Finish script missing: set_root_pw

i do not have any begin or finish define in my rules file it just marked as - , the content of rules file is below

Code:
hostname sun1 - profile1 -

where am i going wrong? Please help
 
Test Your Knowledge in Computers #174
Difficulty: Medium
The Apache 2 'Fancy indexing' directive shows the files plus the date the file was last modified, the size and the user who originally created the files.
True or False?

8 More Discussions You Might Find Interesting

1. Solaris

Jumpstart Error

I 've configured jumpstart and everything is fine but the installation starts asking human intervention and go till NFS conifugration .. Setting up Java. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using... (3 Replies)
Discussion started by: fugitive
3 Replies

2. Solaris

Error after Jumpstart

I have a Solaris 10 U6 flash nothing has changed on my Jumpstart expect for some finish files and profiles. after I jump either a client or a server I always get the same error the following files in / differ from the boot archive changed /kernel/drv/md.conf then I enter in the root... (4 Replies)
Discussion started by: deaconf19
4 Replies

3. Solaris

boot Error for jumpstart

Hi community, I am installing Solaris 10 using a jumpstart installation. Both Server and Client are in the same netmask. When I perform the "boot net - install" command, I receive the following error: Timeout waiting for ARP/RARP packets Timeout waiting for ARP/RARP packets Timeout... (1 Reply)
Discussion started by: Sunb3
1 Replies

4. Solaris

Jumpstart client flash archive error....

Hi , I am facing this issue while restoring flash archive from jumpstart server.The image was aroung 9 gb (5.9 release) and we have restored the other images successfully bigger than this size to other machines we have never faced this issue .Please advice me on this issue . Extracted 100 %... (0 Replies)
Discussion started by: knl.sundeep
0 Replies

5. Solaris

Jumpstart -- Warning: Could not find matching rule in rules.ok

I just setup a new jumpstart server, and I'm having problems with rules.ok errors. I'm coming up blank after many Google searches, forum searches, etc..... This is the error I receive: Skipped interface e1000g1 Attempting to configure interface e1000g0... Configured interface e1000g0... (0 Replies)
Discussion started by: christr
0 Replies

6. Solaris

Jumpstart Error: Unsupported version (3.0).

Hello, The OS version of the ZFS flar is Solaris 10 U9 . Here is the screen output from my attempted jumpstart: System identification is completed. System identification complete. Starting Solaris installation program... Searching for JumpStart directory... Using rules.ok from... (5 Replies)
Discussion started by: Siralos
5 Replies

7. Solaris

help me! jumpstart installation error

Hi actualy my two machines are sun sparc ultra 60. Both are same configuration. I am trying jumpstart Installation in my two machines, i got no errors in server side but in the client side actually it detects the server machine with correct hostname and domainname but after showed that it will... (2 Replies)
Discussion started by: Grovestreet
2 Replies

8. Solaris

Solaris 10 Jumpstart Error

Hey All, I'm trying to jump start a new Sun Server from an existing jump start server, but this last machine is giving me driver errors :s It doesn't make sense as we've built a few of these exact same servers just recently, but this last one displays: "No driver (or driver binding)... (2 Replies)
Discussion started by: UnxAdm1101
2 Replies
RAKE(1) 						 Ruby Programmers Reference Guide						   RAKE(1)

NAME
rake -- Ruby Make SYNOPSIS
rake [--f Rakefile] [--version] [-CGNPgnqstv] [-D [PATTERN]] [-E CODE] [-I LIBDIR] [-R RAKELIBDIR] [-T [PATTERN]] [-e CODE] [-p CODE] [-r MODULE] [--rules] [variable=value] target ... DESCRIPTION
Rake is a simple ruby(1) build program with capabilities similar to the regular make(1) command. Rake has the following features: o Rakefiles (Rake's version of Makefiles) are completely defined in standard Ruby syntax. No XML files to edit. No quirky Makefile syntax to worry about (is that a tab or a space?). o Users can specify tasks with prerequisites. o Rake supports rule patterns to synthesize implicit tasks. o Flexible FileLists that act like arrays but know about manipulating file names and paths. o A library of prepackaged tasks to make building rakefiles easier. OPTIONS
--version Display the program version. -C --classic-namespace Put Task and FileTask in the top level namespace -D [PATTERN] --describe [PATTERN] Describe the tasks (matching optional PATTERN), then exit. -E CODE --execute-continue CODE Execute some Ruby code, then continue with normal task processing. -G --no-system --nosystem Use standard project Rakefile search paths, ignore system wide rakefiles. -I LIBDIR --libdir LIBDIR Include LIBDIR in the search path for required modules. -N --no-search --nosearch Do not search parent directories for the Rakefile. -P --prereqs Display the tasks and dependencies, then exit. -R RAKELIBDIR --rakelib RAKELIBDIR --rakelibdir RAKELIBDIR Auto-import any .rake files in RAKELIBDIR. (default is rakelib ) -T [PATTERN] --tasks [PATTERN] Display the tasks (matching optional PATTERN) with descriptions, then exit. -e CODE --execute CODE Execute some Ruby code and exit. -f FILE --rakefile FILE Use FILE as the rakefile. -h --help Prints a summary of options. -g --system Using system wide (global) rakefiles (usually ~/.rake/*.rake ). -n --dry-run Do a dry run without executing actions. -p CODE --execute-print CODE Execute some Ruby code, print the result, then exit. -q --quiet Do not log messages to standard output. -r MODULE --require MODULE Require MODULE before executing rakefile. -s --silent Like --quiet, but also suppresses the 'in directory' announcement. -t --trace Turn on invoke/execute tracing, enable full backtrace. -v --verbose Log message to standard output (default). --rules Trace the rules resolution. SEE ALSO
ruby(1) make(1) http://rake.rubyforge.org/ REPORTING BUGS
Bugs, features requests and other issues can be logged at <http://onestepback.org/redmine/projects/show/rake>. You will need an account to before you can post issues. Register at <http://onestepback.org/redmine/account/register>. Or you can send an email to the author. AUTHOR
Rake is written by Jim Weirich <jim@weirichhouse.org> UNIX
November 7, 2012 UNIX

Featured Tech Videos

All times are GMT -4. The time now is 11:18 PM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy