In <[log in to unmask]> [log in to unmask] writes:

> X-no-Archive:yes
> Thanks, Chris and Lars, for suggesting smbclient and providing details
> instructions. Works well. Interesting that in spite of the "Type your
> message, ending it with a Control-D" message, :EOD is what does the trick.

I believe you can also get by with writing the message to a file, and redirect
ing the input (for smbclient) to the file...

> For me, this idea raises some questions. The first is how to work this out
> dynamically, so that for any user who for instance streams a particular job,
> that job could resolve !HPSTREAMEDBY to a host name for -M. Even more
> generically, what might be a good means to, for instance, send out "two
> minute warning" messages (using smbclient, and from the 3000) only to users
> who are currently connected when quiescing the system for backups? Since
> DHCP is available, hardcoding some logic for IP addresses and host names
> will not work.

Well, using some combinations of the :NSUSERS command files (showconn stuff?)
you can get a list of users signed onto the system and the 'node name' their
PC reports itself as. A quick grep of that list for the user name you're
looking for should yield a computer name.

> Finally, our 3000 is on another network segment. So we have to use the
> remote announce setting in smb.conf with our WINS server as its argument, to
> have our 3000s show up in Network Neighborhood. The reverse is also a
> problem - to send a message, smbclient seems to require both the host name
> and the IP address. Can SAMBA use our WINS server for host name lookups?

Not my area of expertise, but I suspect you need to tweak nmbd. That guy
handles the name resolution (and advertising) stuff for smbd (not DNS
resolution - but WINS stuff). There are settings in the config file for
various WINS server thingys...

  Happy hunting,
    Chris (remove nospam) Bartram