On 7 July 2014 13:32, jason matthews wrote:
> i normally make a VNIC and assign to a VLAN such as:
>
> dladm create-vnic -l aggr0 -v 300 net0
>
> this totally breaks iftop and tcpdump - however, snoop works. should i be
> creating my VLANs “the other way?" or is there some other sort of work arou
i am rather found of solving problems with tcpdump but i have discovered that
crossbow VLANs break ether sniffering.
i normally make a VNIC and assign to a VLAN such as:
dladm create-vnic -l aggr0 -v 300 net0
this totally breaks iftop and tcpdump - however, snoop works. should i be
creating
Ok. Thank you.
I’ll turn off "svc:/network/location:default”.
The UPS daemon failed because it was disconnected from the LAN, and could not
communicate with the NUT master server. No big deal.
I’ll turn off automatic snapshots, too. I never used them anyway. I think I
just started them bec
On 07/07/14 15:52, dormitionsk...@hotmail.com wrote:
> Then I thought, well, maybe something in the zones are causing this, so I
> booted them back up and ran dmesg again.
>
> "# dmesg” — with the non-global zones running — shows this:
The first thing that really stands out to me is this:
> Jul
On Jul 7, 2014, at 1:13 PM, James Carlson wrote:
>
> I don't know if things have changed in the 5 years or so since I
> actively worked on that code, but at least back then it wasn't possible
> to do a "restart" on the network/physical:default service. It was just
> a no-op.
James,
we have h
On 07/07/14 15:55, Michelle Knight wrote:
>
>
> On Mon, 07 Jul 2014 15:47:26 -0400
> James Carlson wrote:
>
>> That probably should have been:
>>
>> route -p add default 192.168.0.1
>
> Yup, that took and putting the interface back in again .. it has now
> survived two reboots.
>
> Any idea w
On Mon, 07 Jul 2014 15:47:26 -0400
James Carlson wrote:
> That probably should have been:
>
> route -p add default 192.168.0.1
Yup, that took and putting the interface back in again .. it has now
survived two reboots.
Any idea where I originally went wrong please?
__
In message <20140707204055.603483d9@fitpc3>, Michelle Knight writes:
>However, I do now have ...
>
>bge0/_a static ok 192.168.0.25/24
Perhaps a remnant from your NWAM configuration.
Delete it.
# ipadm delete-addr bge0/_a
>...and the box can talk!
>
>Running the route command again without th
Well, I did the following to clear up space, from the “Open Solaris Bible":
zoneadm -z myzone2 uninstall -F
zonecfg -z myzone2 delete -F
That cleared up some space.
At first, it didn’t boot. It kicked me into maintenance mode. I don’t
remember what I did, exactly, but I booted it again, and i
On 07/07/14 15:40, Michelle Knight wrote:
>> route add -p default 192.168.0.1
> route: botched keyword p
That probably should have been:
route -p add default 192.168.0.1
The "-p" option makes the change "permanent" so that it survives a
reboot. It does so by writing the rest of the command line
On Mon, 7 Jul 2014 12:20:56 +0100
Jonathan Adams wrote:
> svcadm disable svc:/network/physical:nwam
> svcadm enable svc:/network/physical:default
>
> ipadm delete-addr bge0/v4
>
> ifconfig bge0 plumb
ifconfig: cannot plumb bge0: Interface already exists
> ifconfig bge0 192.168.0.2 netmask 25
On Mon, 07 Jul 2014 09:35:30 -0400
John D Groenveld wrote:
> # ipadm show-if bge0
bge0 disabled --- -46
> # ipadm enable-addr -t bge0/v4
ipadm: could not enable address: Object not found
___
openindiana-discuss mailing list
openindiana-discu
On 07/07/14 15:01, dormitionsk...@hotmail.com wrote:
>
> On Jul 7, 2014, at 12:29 PM, James Carlson wrote:
>>
>> At a guess, you've got several snapshots that are tying up a lot of
>> valuable resources.
>
>
> Thanks, Mr. Carlson.
>
> And that is something that I’d been wondering about for q
On Jul 7, 2014, at 12:29 PM, James Carlson wrote:
>
> At a guess, you've got several snapshots that are tying up a lot of
> valuable resources.
Thanks, Mr. Carlson.
And that is something that I’d been wondering about for quite some time — “Do
snapshots take additional space?”
I think your
Hello.
Sai Prajeeth писал 07.07.2014 20:00:
Hi list,
I am not able to compile filebench and iozone (file system benchmarks)
on
openindiana. I get the following error messages for filebench.
Assembler: eventgen.c
"/var/tmp//ccrzaq70.s" line 3 : Invalid section attribute
"/var/tmp//ccrzaq70.s" l
On 07/07/14 13:58, dormitionsk...@hotmail.com wrote:
> Additional Info.
>
> It just occurred to me that I should give you the output of zfslist:
This doesn't show an allocation problem; it shows a usage problem. Note:
> rpool 133G 481M46K /rpool
Total
Ok. Never mind. I did the math. It makes sense to me now.
NAME USED AVAIL REFER MOUNTPOINT
rpool/ROOT 26.6G 481M31K legacy
rpool/dump 8.00G 481M 8.00G -
rpool/export
I’m real confused.
I’m investigating why our main server died last week. When I look at some of
the old logs of our nightly admin routines, I found that I might have had a
disk free problem. A “df -h” command on the server that died gave me this
output on June 25th:
*
In message
, Sai Prajeeth writes:
>I am not able to compile filebench and iozone (file system benchmarks) on
Build for me with illumos-gcc:
http://pkg.openindiana.org/dev/manifest/0/developer%2Fillumos-gcc%404.4.4%2C5.11-0.151.1.9%3A20140117T204600Z>
$ env
PATH=/opt/gcc/4.4.4/bin:/usr/bin:/usr/
Additional Info.
It just occurred to me that I should give you the output of zfslist:
Additional Info.
It just occurred to me that I should give you the output of zfslist:
myad...@tryphon.ds:~# zfs list
NAME USED AVAIL REFER MOUNTPOINT
rpool
Has anyone tried to cheat AWS OS choice limitations and import a
vmware disk image with Illumos installed into the AWS cloud? Did it
work? Which problems did you encounter?
Ced
--
Cedric Blancher
Institute Pasteur
___
openindiana-discuss mailing list
Hi list,
I am not able to compile filebench and iozone (file system benchmarks) on
openindiana. I get the following error messages for filebench.
Assembler: eventgen.c
"/var/tmp//ccrzaq70.s" line 3 : Invalid section attribute
"/var/tmp//ccrzaq70.s" line 3 : Invalid section attribute
"/var/tmp//ccrz
and the failing gnome-panel produces also a high CPU load...
Am 07.07.14 schrieb "Udo Grabowski (IMK)" :
> On 07/07/2014 16:00, Udo Grabowski (IMK) wrote:
> >On 07/07/2014 15:12, Carsten Grzemba wrote:
> >>I see that if the panels not appear the gnome-panel stack looks a little
> >>bit lost:
> >
On 07/07/2014 16:00, Udo Grabowski (IMK) wrote:
On 07/07/2014 15:12, Carsten Grzemba wrote:
I see that if the panels not appear the gnome-panel stack looks a little bit
lost:
root@gnom:~# pstack 28547
28547: gnome-panel
- lwp# 1 / thread# 1
feef4695 poll
On 07/07/2014 15:12, Carsten Grzemba wrote:
I see that if the panels not appear the gnome-panel stack looks a little bit
lost:
root@gnom:~# pstack 28547
28547: gnome-panel
- lwp# 1 / thread# 1
feef4695 pollsys (8333b08, 11, 0, 0)
fee853a6 poll (8333b08,
In message <20140707050628.127c9abc@fitpc3>, Michelle Knight writes:
>> # ipadm show-addr bge0/v4
>static disabled 192.168.0.25/24
# ipadm show-if bge0
# ipadm enable-addr -t bge0/v4
John
groenv...@acm.org
___
openindiana-discuss mailing list
openindi
I see that if the panels not appear the gnome-panel stack looks a little bit
lost:
root@gnom:~# pstack 28547
28547: gnome-panel
- lwp# 1 / thread# 1
feef4695 pollsys (8333b08, 11, 0, 0)
fee853a6 poll (8333b08, 11, , fe73162c) + 4c
fe731644 g_poll (8
okay, I'm sure you've tried all this ...
Falling back to old "ifconfig" commands.
svcadm disable svc:/network/physical:nwam
svcadm enable svc:/network/physical:default
ipadm delete-addr bge0/v4
ifconfig bge0 plumb
ifconfig bge0 192.168.0.2 netmask 255.255.255.0 up
route add -p default 192.168.
28 matches
Mail list logo
