Shell Programming and Scripting

Aliste, Thank you very much for reply.. previously this was not the case when the code was used on solaris..

now when we are using in HP UX we are getting this issue.

One strange thing is that when i run useradd seperataly there is no issue..

Code:

sudo /usr/sbin/useradd -c "ricky" -m -d /home/y012653 -g dac -G oclsascr -s '/bin/ksh' y012653

Can you please help me to understand the how to avoid or where to look to print user name not the hash value in passwd file

---------- Post updated 04-09-13 at 09:08 AM ---------- Previous update was 04-08-13 at 10:51 AM ----------

No reply from any body... it seems very few Perl expert

I think there is a bug in the HP-UX perl.
Either contact HP support for a Perl patch,
or try to find a work around in the Perl code:
the error happens with lc($pUserID) in the code you posted.
So add an assignment to a new variable

Code:

$lcUserID=lc($pUserID);

after the previous assignment of $pUserID, and replace the following references lc($pUserID) by $lcUserID
Hopefully the simpler reference will avoid the error.

On a good day, you can avoid host-specific code by using the right tools where there is a redundant set, including commands you can spawn from perl.

In fact, if you find something that is very different, you might be able to script it differently on each machine, and not have the difference invade code that needs that answer or service. Think of how much simpler: main script xxxx calls yyyy, and there are two yyyy scripts, one for each os. None of the three scripts has code for the other host, nor any host type checking. Now, the variant file yyyy could be a perl lib or some sort of executable.

Please forget my previous proposal.
I think Alister was very close; the \@CmdArgs does not work.
What happens if you omit the \ i.e.

Code:

                ,program_args => @CmdArgs

?

After using as this.. The result is same

Code:

,program_args => @CmdArgs

it is creating the entry in passwd file with array(hash)

Have you tried using perl's tracing and debugging features? They can be extremely helpful in determining where the train is going off the rails.

If you're not familiar with them, start reading the perlrun man page where it documents the -d switch.

Regards,
Alister

You can also watch PERL from the outside using truss/tusc/strace to see what error started the failure.