On 08/17/2014 05:06 PM, Philip Guenther wrote:
Heh, good thing I had that 5% hedge when making a guess based on
fading memory of an email thread and the possibility that you were
running an old snapshot. :-/
If no one else speaks up, the next step for tracking this down may be
to ktrace the cron invocation of the daily script by changing its root
crontab entry to say "ktrace -i -f /root/daily.ktrace.out /bin/sh
/etc/daily" and then matching up the output there with the scripting
to figure out what is triggering that warning.
Philip Guenther
When I run (as root), env SHELL=/bin/sh /usr/libexec/security,
I see the same error message.
root@ksh:[/]# env SHELL=/bin/sh /usr/libexec/security
/bin/sh: /.cshrc[8]: syntax error: `(' unexpected
So, I think you are right, the error message is triggered from
/usr/libexec/security,
if I run "env SHELL=/bin/ksh /usr/libexec/security", there is no error
message.
but my /usr/libexec/security is up-to-date(1.31).
I noticed another problem, when I run "env SHELL=/bin/sh ktrace -i -f
/tmp/k.out /usr/libexec/security".
then run kdump < /tmp/k.out, kdump show the error message
kdump: ktrace.out: No such file or directory
I need to rename k.out to ktrace.out to make kdump work.
(ktrace filesize is 3xxMB, so I can not post here)
Thank you.
