export: -broker_env: bad variable name

A

Aminavy

Hello everyone!
I see "export: -broker_env: bad variable name" in system startup messages:
Code: 
Clearing /tmp (X related).
Updating /var/run/os-release done.
Creating and/or trimming log files.
Updating motd:.
Starting syslogd.
No core dumps found.
export: -broker_env: bad variable name
Starting powerd.
Mounting late filesystems:.
Starting cron.
Starting background file system checks in 60 seconds.

I not changed anything in startup related files (/etc/rc* etc.).
This message appeared few weeks after installing freebsd in this machine. and I don't know
 
Hi,

I couldn't find anything that includes broker_env string in all rc.d scripts exist in the ports tree but couldn't find anything that contains it. Maybe you set something accidentally in /etc/rc.conf?

Code: 
# find /usr/ports/ -type f -not -path "*distfiles*" -path "*files*" -name "*.in" -exec grep -Hi ".*broker_env.*" {} +
# find /etc/rc.d -type f -exec grep -Hi ".*broker_env.*" {} +
# find /usr/local/etc/rc.d -type f -exec grep -Hi ".*broker_env.*" {} +
 
It's something that happens between savecore and powerd, on a basic system that's these:
Code: 
/etc/rc.d/savecore               <- is the one printing "No core dumps found."
/etc/rc.d/watchdogd
/etc/rc.d/auditd
/etc/rc.d/power_profile
/etc/rc.d/ntpdate
/etc/rc.d/hastd
/etc/rc.d/auditdistd
/etc/rc.d/SERVERS
/etc/rc.d/rpcbind
/etc/rc.d/nisdomain
/etc/rc.d/nfsclient
/etc/rc.d/ypserv
/etc/rc.d/statd
/etc/rc.d/ypxfrd
/etc/rc.d/ypupdated
/etc/rc.d/ypbind
/etc/rc.d/ypldap
/etc/rc.d/lockd
/etc/rc.d/ypset
/etc/rc.d/keyserv
/etc/rc.d/quota
/etc/rc.d/yppasswdd
/etc/rc.d/automountd
/etc/rc.d/automount
/etc/rc.d/DAEMON
/etc/rc.d/bootparams
/etc/rc.d/sdpd
/etc/rc.d/rtadvd
/etc/rc.d/rwho
/etc/rc.d/powerd                <-- "Starting powerd"
 
nxjoseph said:
Maybe you set something accidentally in /etc/rc.conf?
Click to expand...
Certainly possible, but I would have expected the error popping up several times, rc.conf is sourced many times by all the various rc(8) scripts. But a missing quote here or there can certainly lead to some very interesting errors.
 
Aminavy said:
I don't know why it not fixed yet.
Click to expand...
It's fixed in 'main' (aka 'latest'), not in quarterly. So quarterly packages still have this issue. Quarterly is at 2.5.1_16, latest is at 2.5.1_20.

A new quarterly (2025Q3) will be made very soon, then this (and other fixes) will be in quarterly.
 
You must log in or register to reply here.
Back
Top