Hi Michal,
crontab:
declare -x HOME="/root"
declare -x LOGNAME="root"
declare -x OLDPWD
declare -x PATH="/usr/bin:/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/sh"
declare -x SHLVL="2"
declare -x USER="root"
declare -x _="/bin/bash"
shell:
declare -x CCACHE_DIR="/var/cache/ccache"
declare -x CCACHE_UMASK="002"
declare -x CVS_RSH="ssh"
declare -x G_BROKEN_FILENAMES="1"
declare -x HISTSIZE="1000"
declare -x HOME="/root"
declare -x HOSTNAME="nass.vorlon.lan"
declare -x INPUTRC="/etc/inputrc"
declare -x LANG="de_DE.UTF-8"
declare -x LESSOPEN="|/usr/bin/lesspipe.sh %s"
declare -x LOGNAME="root"
declare -x
LS_COLORS="no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:"
declare -x MAIL="/var/spool/mail/root"
declare -x OLDPWD
declare -x
PATH="/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lib/ccache:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin"
declare -x PWD="/root"
declare -x SHELL="/bin/bash"
declare -x SHLVL="1"
declare -x SSH_ASKPASS="/usr/libexec/openssh/gnome-ssh-askpass"
declare -x TERM="xterm-color"
declare -x USER="root"
Needs Perl LANG or something else ?
cu romal
Michal Jaegermann schrieb:
On Thu, Feb 07, 2008 at 09:25:07PM +0100, Robert M. Albrecht wrote:
I use mrtg to monitor some network devices. Running from the cli is fine,
but running from cron I get strange errors (for the last past few weeks).
...
Currently I have no clue if this is a mrtg or a cron problem. Any ideas ?
...
Use of uninitialized value in concatenation (.) or string at /usr/bin/mrtg
line 1366.
.........
Just guessing but it looks like that mrtg expects to see something
in environment, and it gets it when you are running from a command
line. cron, quite deliberately, has that enviroment quite reduced.
Did you try to look at that line 1366? Of course that "something"
would have be initialized somewhere earlier.
If you will identify what that may be then you can always run
mrtg via a wrapper which will provide a missing piece.
Michal
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list
