Recently, I accidentally found out which of two options Solaris usesfor matching names in NFS exports. As traditional, I did this by stubbing my toe .

Given a name in an /etc/dfs/sharetab line, there are two possible waysof checking if it matches an incoming NFS request: you could resolve the sharetab name to its IP addresses and see if the request's IP addressmatched, or you could take the request's IP address and try to turn itinto a hostname and see if

What are variables?

In many languages, variables are just labels for storage locations,for a spot in memory. This ranges from pure machine level storage, inlanguages like assembler, up through storage locations augmented withsize and type information, such as in C, all the way to Perl, where the'storage locations' are actually fairly abstract. But they're stillthere, even in Perl, partly because it's a comforting way to think aboutit: variables are where you put things .

In

This week, we:

• got 12,120 messages from 254 different IP addresses.
• handled 17,527 sessions from 926 different IP addresses.
• received 119,314 connections from at least 38,574 different IPaddresses.
• hit a highwater of 17 connections being checked at once.

Volume is way down from last week ; in factit's back to the level I consider fairly quiet (although this volumestill has a lot

A commenter on an earlier entry noted that patchadd 's exit codes are apparently not documented because they'reconsidered an internal implementation detail that might change at somepoint. Unfortunately this is bogus logic.

There's a simple rule: once you explicitly expose something to users, itceases to be an internal implementation detail in practice no matterwhat you want (and no matter what you may claim in documentation,although Sun does not explicitly claim this in the patchadd manpage).

Solaris 9 manifestly exposes patchadd 's