Codex.org

Coding, ramblings, and more

Browsing Posts published by jobu

Troubleshooting networking issues in Solaris can be a pain. When compared to most any Linux distrobution, Solaris falls short on easy to use tools and resources. While the tools might not be easy to find, there are a number of tools that can be used to figure out the status of your various network devices. The first simple program that will help determine all the interfaces on your Solaris server is dladm. Dladm is a tool that is used to configure data-link interfaces. I am not going into the full use here, as it would not be beneficial in troubleshooting.  The second tool that can be used is ndd. Often you will not need to touch nddif you have used dladm correctly.

List all of the network devices on the server.

One of the first items of information that is needed when working on Solaris and looking at the network, is the name of the network devices (aka NIC or Network Interface Card). Unlike Linux, solaris does not use an alias to the device, and the names of the devices change depending upon which hardware you are running. The quick way to determine the names of all the interfaces on the server is to use dladm. Ifconfig does not work because if an interface is not plumbed then it will not be displayed.

For all devices

# dladm show-link
nxge0           type: non-vlan  mtu: 1500       device: nxge0
nxge1           type: non-vlan  mtu: 1500       device: nxge1
nxge2           type: non-vlan  mtu: 1500       device: nxge2
nxge3           type: non-vlan  mtu: 1500       device: nxge3

Show connection status of all devices or single device.

The next major piece of information that is needed is the speed, link status, and duplex of the interface. On Linux you could use mii-tool or ethtool, but Solaris had none of these fun tools. Once again you can fall back on dladm to provide you with the necessary information.

For all devices

# dladm show-dev
nxge0           link: up        speed: 1000  Mbps       duplex: full
nxge1           link: up        speed: 1000  Mbps       duplex: full
nxge2           link: up        speed: 1000  Mbps       duplex: full
nxge3           link: up        speed: 100   Mbps       duplex: full

For a single interface

# dladm show-dev nxge0
nxge0           link: up        speed: 1000  Mbps       duplex: full

This will get you to the point where you can check the status of link connection, speed, and duplex.

There are five weeks until the next mountain bike race at Fort Yargo. I am hoping to get in four laps this year instead of 3. 44 miles in 6 hours on my single speed.

So today I went running for 23 minutes. The goal is to do some cross training, and improve my overall health. We will see.The goal for tomorrow is a ride.

Today was the first race  in the 6/12 hour endurance mountain bike  race series by Chain Buster Racing at Heritage Park. These are endurance races where you try to complete as many laps as possible in the time allotted. In this case it happens that there is only a 6 hour option, but the points go to whichever you do in later races, either 6 or 12 hour.

The course this year was 2 miles shorter than last year, and seemed in my opinion to be much improved. The conditions were great considering all the rain, however Heritage Park is quite full of roots so you have to be on your toes.

Race Review.

Something seemed to be in the air today. The energy was almost electric. People that were normally calm and cool before a race were bouncing around. Seems as if the shining sun after days of rain was enough to get people into the mood to ride. I found myself getting antsy before the race started, and normally that is not the case.

Start and Lap 1

Since today was my first time racing with platform pedals and skate shoes, I was not interested in trying to hang with the big boys at the front of the pack. Instead I chose a spot near the middle to rear of the pack so that I would not burn out to quickly. They skipped the lamans style start, and just had us all on our bikes. As the number of riders was lower than that of last year, this was fine with everyone that I was with. At 10:00 AM on the dot, they started the race. Take note, my first lap is almost always my fastest. One of these days I need to learn to pace myself better.

The first lap included the parade lap which takes you out on the finishing gravel road back to the start, and as usual it was the normal chaos. I ended up passing a good number of people before we got to the trail head, and was having a great time. Turns out I should have moved myself up a bit further in the group. It took almost 2 miles to pass a guy that would come to a crawl at any bump, turn, or obstacle. Once I passed him, the first lap proved to be fun and quick. My legs warmed up and I felt good. There were a few climbs that I jumped off and pushed my bike up, but for the most part I was feeling good.

Lap 2.

Once I made it back to the Gwinnett Area Trail Riders (G.A.T.R.) tent, I stopped to drink half a bottle of Cliff Energy Mix and a Gu gel. I felt great on the second lap as well. While on the second lap, I met up with Fred, a fellow G.A.T.R, and we finished the lap together. Overall I was feeling good, but riding on platform pedals did require more muscle than with clipless.

Lap 3.

At this point there was a fair bit of mud on the bike, and my shirt was starting to get soaked with sweat. A quick change out of the clothes, and then Fred and I headed over to the bike wash to do a quick clean of the bikes before heading out. The third lap was going well till about 2/3′s of the way through. At this point when I went to stand up to climb my quadriceps twinged. Not sure if I had pushed them beyond their limits or if they were about to cramp on me. As a result, I had to be careful standing up to climb, and resulted in walking the bike up most of the longer/steeper climbs. Fred left me behind as he was keeping a faster pace on the climbs.

The next issue that I had was on the last fast downhill section of the course. I took a berm to high, and the top washed out on me. My front wheel and bike went one way, I went the other. Luckily, I only bruised my arm, scratched up my knee and leg, and my hip a bit. It could have been much worse. Not being stuck to the pedals can be a real godsend sometimes. I did find out that I bent my rear rotor, but that was fixed well enough by bending it. Even with the wreck I finished the lap in decent time.

Lap 4

Before heading out on lap four, it was time to refuel. Peanut butter and jelly, snickers bar, Cliff drink, and some nuts. I thought that I felt ok, and Fred agreed to head out with me on yet another lap. Five minutes into it I was miserable. My triceps were sore from breaking, my legs felt gassed, and I was ready to throw in the towel. Fred took off, and I just kept plodding along. Before he headed out, I told him I was done. There was no way that I planned on going on a fifth lap. Somewhere during that loop though the food kicked in. I felt better, and decided that a fifth lap was in the works.

Lap 5

I came into the pits feeling like a million dollars. Now don’t get me wrong, I was sore, bruised, and tired, but I was going to get in my 5 laps. I had almost 2 hours to do it in, and even if I had to push my bike around the course I was going to make 5 laps. I tried to talk Fred into going with me, but he was done for the day. Lap 5 was my victory lap. I had done what I set out to do, and enjoyed the ride. My last lap took just under an hour, and was fun.

Overall it was a great day and a great race. The weather held out and the trail was in great shape for all the rain we had received. I raced in “expert class” and came in 14th out of 15 people. At least I was not last. The next race will be May 1st at Ft. Yargo. Had a good time hanging out with the other riders, could not have asked for a better day.

Well, I had thought that I was going to go with JSF due to popularity and such, but I have had a change of heart. Partly due to my own devices, but mainly cause I am not worried about what is popular, but what works best. Instead I am going to go with Wicket.

Wicket may not be the most popular framework, but it melds with the way I think, and since this is code that I am going to write and maintain, well I am going to go with something that I like. If I wanted to get it done super quickly I would go with PHP, but then when it comes to maintainability I would be lost. There are people out there that might disagree, but for me and my way of thinking Java works better. This is not to bash Microsoft’s .NET implementation, but I do not have those tools or services at my disposal.

So far, I have not even had the chance to get started on this fun little project. Hopefully here soon I will begin. The main problem is that I have to get other projects done prior to beginning work on this one. The funny thing is that none of those other projects are Java projects. Instead they are all in Perl, Bash, sh, or ksh. In addition to my regular work, I also have a fun little Power Point Presentation that I need to pull out of thin air. Hopefully soon something will get going.

I have a project at work that I have to implement. It is a web based site that I have to put together. Technically, I could use almost any technology that I want, provided that it will run on a Linux/Solaris platform. So I could write this app using PHP, perl, Python, or Java. For reasons that would take to long to explain at this moment, the option was chosen to go with Java.

Now like PHP there are about 9342 different frameworks that could be chosen for developing a web application in Java. Of all the technologies out there wee are mainly looking at JSF 2.0 using JFaces or some other tech to add AJAX support. From the looks of it there are both pluses and minuses to using JSF. One main factor in the decision was dealing with the popularity of JSF. Once the prototyping starts we will see.

The other framework that I was looking at was Wicket. While this is not as popular in the mainstream, it seems to embrace the way that I approach stuff more. I am sure that either will meet the needs of the project. However, I am working with another developer other than just myself so compromises had to be made. One of those compromises was JSF.

So as of yet I am not sure what I am getting into with JSF. About 4 years ago I messed with it when they were still working on the 2.0 spec. From what I remember it was not that bad to work with. At the time I was not working on an application as complex as the one that I have planned. This time the project is a bit more involved and will be used by more than just myself and a few other people.

So I am going to dive in head first, and see where I land. That is of course unless I review wicket, and decide that this is the better project. I must be insane.