Hello Wes!

22 Jun 03 15:10, you wrote to me:

 BS>> Oh that's quite nice, it's in section 1.

 WG> I just checked my linux box to make sure. Getopt in section 1 is some
 WG> kind of freaky Linux getopt for shell scripts. (section 1 is command
 WG> line programs; like section 1M under SVR4). You want the getopt in
 WG> section 3, it's a C function.

DOH!  :)

 BS>> Somekind of semaphore?

 WG> Close enough; the functionaity is atomic across processes (and across
 WG> machines if you are runing nfs.lockd). The version I wrote for
 WG> -lcompat might not be atomic across threads; I'd have to think about
 WG> that for a minute. If you have a moment, you should grep the 'net for
 WG> "advisory file locking".

Hmm.. i'll look at it.

 BS>> Oh ok :) That's real multiuser programming :)

 WG> Remember, under UNIX, *all* programming should be treated as
 WG> multi-user programming: otherwise you *will* eventually get bit in the
 WG> ass -- if not by another user, then by a cron job, runbbs.sh, etc.

Exactly, Single user programming is for DOS/Windows :)

Regards,
Bo

--- GoldED+/LNX 1.1.5