I've recently installed a FreeBSD 9.0 jail server, and inside each of
my jails I am getting the following errors in my log about every 5
minutes:
cron[7635]: NSSWITCH(_nsdispatch): ldap, group, setgrent, not found,
and no fallback provided
cron[7635]: NSSWITCH(_nsdispatch): ldap, group,
On Sat, Aug 28, 2010 at 01:49:18PM +0200, Bernt Hansson wrote:
Hell Bernt,
I'm having problems with lines like this in cron, works on the command
line, but not in cron.
/sbin/dump -0uan -f - /usr | gzip -2 | ssh -c blowfish \
targetu...@targetmachine.example.com dd
After building a new FreeBSD5.4 system, I have done
something bad to it.
When cron runs jobs in /etc/crontab as operator, it seems
as if that 6TH field in /etc/crontab is being interpreted as a
command rather than the user ID it is supposed to run under. I
keep getting messages
On Tuesday 31 October 2006 12:08, Martin McCormick wrote:
After building a new FreeBSD5.4 system, I have done
something bad to it.
When cron runs jobs in /etc/crontab as operator, it seems
as if that 6TH field in /etc/crontab is being interpreted as a
command rather than the user
In the last episode (Oct 31), Martin McCormick said:
After building a new FreeBSD5.4 system, I have done
something bad to it.
When cron runs jobs in /etc/crontab as operator, it seems
as if that 6TH field in /etc/crontab is being interpreted as a
command rather than the user ID
Dan Nelson writes:
The operator user has no access to /etc/crontab. You have probably
copied entries from the system crontab (i.e. /etc/crontab) into a
user's crontab. The system crontab has the extra user column, where
user crontabs don't (since they always run as the user).
