are you piping /dev/null to STDIn in the commands, I
can see you did
that on the commands line, but not clear if you did
it in the script or not.
For every command in the script?
The script is:
http://cvs.opensolaris.org/source/xref/jds/spec-files/trunk/cron-script.sh
I would like to get my
Damien Carbery wrote:
are you piping /dev/null to STDIn in the commands, I
can see you did
that on the commands line, but not clear if you did
it in the script or not.
For every command in the script?
The script is:
http://cvs.opensolaris.org/source/xref/jds/spec-files/trunk/cron-script.sh
Sadly we don't have a 'zlogin -n' because I haven't had time to do
one. Let us know if this helps.
But inside cron, stdin is /dev/null (or an empty file); cron does
allow you to specify one or more lines of input in a crontab entry,
but in general the application is not supplied with any input.
Damien Carbery writes:
If someone inside Sun would like to poke around the machine (it's in Dublin),
I can provide the login details.
This is a zlogin bug (actually, several bugs). I'm writing up the CR
now.
--
James Carlson, Solaris Networking [EMAIL PROTECTED]
Sun
On 10/23/07, Damien Carbery [EMAIL PROTECTED] wrote:
Any thoughts? Suggestions? Is there a bug here?
We currently use a chroot environment to build JDS but a zones setup would be
preferred as it is a supported feature.
When I was first implementing Solaris 10 (before the first S10 kernel
Damien Carbery wrote:
Using snv_73 sparc. Trying to build JDS inside a whole root zone (because we
install packages under /usr, /etc during the build).
I have a cron script that uninstalls the current build, does a svn update,
does a full build and then sends report mails. I noticed that it
