Hi
I have seen a weird behaviour from bash both under Solaris and Linux, most
likely it is a feature but I can't seem to find the answer with google :-\
I have two scripts
test.sh:
#!/usr/bin/bash
echo parent
./child.sh
sleep 120
child.sh:
echo child
sleep 120
If I run the two scripts like
e...@xyz(/export/home/eee) ps -afe|grep 10204
root 10204 9962 0 Dec 10 ? 3114:26 /opt/SMAW/SMAWjdk/1 .5/jre/bin/java -cp
.:./ssdgrptd.jar sscs_daemon
eee 4442 13700 0 15:18:22 pts/2 0:00 grep 10204
Output from top: load averages: 1.93, 1.93, 2.04
15:15:50 981 processes: 979 sleeping, 2 on cpu
hello all,
i've os20xx.yy b130 on my dell laptop M4400. There is a SD card reader.
If i try to use it, the kernel crashes:
Jan 30 19:30:14 tara genunix: [ID 408114 kern.info]
/p...@0,0/pci8086,2...@1e/pci1028,2...@1,2/sdc...@0 (sdcard0) online
Jan 30 19:30:14 tara scsi: [ID 583861 kern.info]
test.sh:
#!/usr/bin/bash
echo parent
./child.sh
sleep 120
child.sh:
echo child
sleep 120
If you omit the #!/bin/bash from child.sh, I suspect the original bash will
look at the file, recognize it's executable, but since the file doesn't
specify a new command interpreter, it's
Has any one gone to http://www.sun.com today?
You get http://www.oracle.com
Very quick change
Yeah, and now we got Oracle logos on opensolaris.org website also. This is
depressing.
Goodbye Sun! Things will never be the same again. A big part of the computer
history just died. Not
If you omit the #!/bin/bash from child.sh, I suspect
the original bash will
look at the file, recognize it's executable, but
since the file doesn't
specify a new command interpreter, it's equivalent to
. ./child.sh meaning
the parent script simply sources the child script.
Not in a new
Is it possible to run GDM inside a zone on b131 ? I would like to have a zone I
can use to run stuff like netbeans etc in, and
I don’t want to use the global zone for that.
As far as I can tell the gdm smf service depends on dbus and that is marked as
global zone only.
One more complication is
On 01/25/10 02:33 PM, Brian Ruthven - Sun UK wrote:
This sounds like the /contrib dependency bug noted in the email
announcing build 131 (and previous builds too):
http://defect.opensolaris.org/bz/show_bug.cgi?id=13233
If you have packages from the /contrib repo, then check the list
attached
On 02/ 1/10 10:22 AM, solarg wrote:
so i tried the same workaround on my machine:
he...@tara:~# pkg image-update -nvf
...
reboot-needed: true
I don't understand the last lines, because it doesn't create a new BE!?
anyone can help?
You used -n which means dry-run essentially. It won't
Gary g_patri...@yahoo.com wrote:
Why didn't Sun use the engineering path of FreeBSD and OpenBSD, namely the
-release, -stable, -current branches instead of doing the OpenSolaris thing
to pry it into the next Solaris 10 successor?
As long as the motto Every enginering release is a stable
I've no luck with that (which I of course tried
first)...
don't just look at the name of the boot environment,
it's simply counted upwards and after 129 comes 130
;)
boot the new BE and run uname -a to see which build
you're actually running - I bet it will show snv_131.
You're quite
Having gone back to check the research*, I think there are some
misunderstandings, some of which may contribute substantially
incorrect conclusions and recommendations. Let's try to correct these.
Reading some of your other posts to this thread (e.g. Windows is for
games, and if you can
Thommy M. Malmström wrote:
You're quite right. ;) Thanks. However, b131 is just as good at running X as
b130, i.e. not at all.
Depends on your hardware - there are some known bugs on some hardware,
but it works fine on many systems (unfortunately, that includes all of
mine, so I'm not sure
Thommy M. Malmström wrote:
You're quite right. ;) Thanks. However, b131 is
just as good at running X as b130, i.e. not at all.
Depends on your hardware - there are some known bugs
on some hardware,
but it works fine on many systems (unfortunately,
that includes all of
mine, so I'm not
Henrik wrote:
If you omit the #!/bin/bash from child.sh, I suspect
the original bash will
look at the file, recognize it's executable, but
since the file doesn't
specify a new command interpreter, it's equivalent to
. ./child.sh meaning
the parent script simply sources the child script.
Not in
Paul:
Is it possible to run GDM inside a zone on b131 ? I would like to have a zone I
can use to run stuff like netbeans etc in, and
I don’t want to use the global zone for that.
It would think that it should be possible, though I have not tried it
myself.
As far as I can tell the gdm smf
Since Asterisk is such a heavily multi-threaded application, I have a client
who is actually interested in trying it out on UltraSPARC Niagara to see if
open source Asterisk running on Solaris on Sun's Niagara hardware can get
better performance than the very costly proprietary solutions that
i've never tried this, but i'd recommend figuring out if gdm can be run
as an xdmcp server.
optionally, you could also run Xvnc within the zone.
or you could ssh -X to the zone and remote display your apps.
if you're tring to run gdm in the zone to access local hardware
(graphics card,
Edward Pilatowicz wrote:
if you're tring to run gdm in the zone to access local hardware
(graphics card, keyboard, mouse, etc) that will be a difficult, since X
now uses hal (which depends on dbus) to discover hardware. i'm not sure
how you could work around this (my X foo is not that
I tried to upgrade from the official build 111b to the dev repo (131) on my
SunFire v20z. The result is that after I log in, it reboots the machine.
Rarely it gets as far as briefly displaying my desktop, but most of the time it
reboots immediately. The v20z is pretty much stock with the
Since it happens randomly on on any disk, I would doubt that all 5 disks
suddenly failed.
When checksum errors happen randomly on any disk it usually either means that
your server has bad RAM or a bad powersupply. Check out this link below:
Having a reboot loop is also a pretty good sign that one of your sticks of
RAM is bad. Go to the command line and type in this command:
gnome-system-monitor
and you'll notice that it is probably rebooting whenever it hits that same
exact certain bad spot in the RAM.
--
This message posted
On 02/ 1/10 05:25 PM, Shawn Walker wrote:
You used -n which means dry-run essentially. It won't create a new BE
or make package changes if you use -n. The -v makes it print what
*would* happen if you ran image-update.
Were you saying that even without -n that it doesn't do anything?
wow, i feel really stupid, i just posted this same question againi post on
so many forums/lists i got confused so i'm really sorry for the double post
anyways, you mean cron can't use $USER but it can use $LOGNAME
ok, i will change this and see if it helps
--
This message posted from
24 matches
Mail list logo
