how to cleanup mail
migurus
synchronizing directories on several 5.0.7 servers, Everything works
just perfect, except one small nuisance - every connection results in
one mail message
NOTICE: Unregistered SCO software ...
I can't think of any smart configuration of rsync which would prevent
that. I can't make users to register their systems, so I am thinking
of a safe ways to remove these pesky messages on the regular basis.
Would it be save to run this:
cat << EOF > /usr/spool/mail/the_login_name_here
EOF
Or is there any other way to do it safely?
Regards,
Brian K. White
One thing you could do is don't use SCO's supplied ssh or rsh as the
transport layer for rsync.
This can be done at least a few different ways but the simplest is just
don't use any ssh or rsh but use native rsync directly instead.
If you must run rsync over ssh then you could compile your own ssh. This
sidesteps a few nasty license manager hooks SCO puts into their build.
In fact, you can even use the pre-digested source from the sco ftp site
to build. It's tweaked to build cleanly on SCO, yet doesn't include the
license manager stuff (since, that would be telling the world too much
about how the licence manager works).
I use native rsync myself just about exclusively, and leave the stock
ssh installed most of the time.
Other than that, if the message is in fact being sent to the
application's stdout or stderr and not directly to syslog or some other
interface, then as with all cron jobs, you suppress emails by capturing
stdout & stderr.
30 4 * * * /path/to/script >/dev/null 2>&1
I use native rsync all the time on sco, in cron, and never saw that
message being generated in that context.
I only ever saw it on the system console where no one ever cared.
--
bkw
Tony Lawrence (pcunix)
Bill Campbell
>Or you could just register the software :-)
Who registers it? I remember walking around the support area in
Santa Cruz, seeing most of the machines with the warning message
about unregistered software. The only thing I've seen
registration do is give SCO demographic information they can use
for their sales and marketing.
On the other hand, for things like backups, we generally use
native rsync without ssh which provides complete control of the
destination directories, limiting access by IP address. I'm not
too concerned with encryption of local LANs, and when doing
remote backups, they work nicely through OpenVPN tunnels (via
Linux gateway machines as I don't have OpenVPN running on
OpenServer).
Bill
--
INTERNET: bi...@celestial.com Bill Campbell; Celestial Software LLC
URL: http://www.celestial.com/ PO Box 820; 6641 E. Mercer Way
Voice: (206) 236-1676 Mercer Island, WA 98040-0820
Fax: (206) 232-9186 Skype: jwccsllc (206) 855-5792
the purpose of government is to reign in the rights of the people
-Bill Clinton during an interview on MTV in 1993
Nico Kadel-Garcia
Hmm. If you use rsync over SSH as a *pull* operation, with tools like
rsnapshot run from another, registered or non-SCO server, I wonder if
this occurs?
Rsyncing securely is tricky: it's often far too easy for unauthorizd
users to access bare rsync materials, and proper handling of SSH keys
and keychains can provide some hooks for this.
Brian K. White
Nico Kadel-Garcia wrote:
> On Jun 22, 3:07 pm, "Brian K. White" <br...@aljex.com> wrote:
>
>> migurus wrote:
>>
>>> I have several installations with rsync running on the hourly basis
>>> synchronizing directories on several 5.0.7 servers, Everything works
>>> just perfect, except one small nuisance - every connection results in
>>> one mail message
>>>
>>> NOTICE: Unregistered SCO software ...
>>>
>> I use native rsync all the time on sco, in cron, and never saw that
>> message being generated in that context.
>> I only ever saw it on the system console where no one ever cared.
>>
>
> Hmm. If you use rsync over SSH as a *pull* operation, with tools like
> rsnapshot run from another, registered or non-SCO server, I wonder if
> this occurs?
>
Aha there you may have something.
--
bkw