Re: Problem with Bash-4 and $(command) syntax
On 12 Mar 2009 at 10:25, Jerry wrote:
{Problem with Bash-4 and $(command) ...}:
Is this a known problem with Bash-4? I have not been
able to find anything about it on the Bash site.
Jerry
ges...@yahoo.com
I found the same problem, and have reverted to
bash3.2 until it's sorted out.
Like you, I wasn't able to find discussion of this on
the lists I subscribe to - although I'm sure it's going
on. Looking through the diffs in
/usr/ports/distfiles/bash, the bracketed form of
command substitution appears to be a long-
standing problem in bash40-xxx.
The back-tick `command` form works as it should,
but not the Posix-style $(command) form, as of
GNU bash, version 4.0.10(1)-release
Mark
--
--
Mark McConnell
mar...@dataabstractsolutions.com
Data Abstract Solutions - Support
12209 N.E. Fourth Plain Suite DD,
Vancouver WA 98682
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: term: Undefined variable emitted after startup scripts
On 1 Nov 2007 at 22:00, Andy Harrison wrote:
{Re: term: Undefined variable emit...}:
On 11/1/07, Mark McConnell wrote:
On bootup, I see the message repeated several
times, term: Undefined variable.
Were any of the shell rc files change recently? Like root's .profile
or .bashrc, or the ones in /etc/?
- --
Andy Harrison
Thank you Andy - I didn't realize that root's .cshrc file
would be used on bootup. I've changed the file to test
for definedness before checking the value of $term.
Mark
--
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
term: Undefined variable emitted after startup scripts
On bootup, I see the message repeated several times, term: Undefined variable. What is causing this message and what must I change to eliminate it? I want to rule it out as a factor contributing to my difficulty starting jabberd2 on bootup (c2s is the client-to-server component of jabberd). Starting ntpd. Starting usbd. Starting jabberd. term: Undefined variable. Starting proftpd. Removing stale Samba tdb files: . . . . . . . . done Starting nmbd. ERROR: c2s died. Shutting down server. Starting smbd. Starting mysql. term: Undefined variable. Starting webmin. Starting jabberd_users_agent. Starting mu_conference. term: Undefined variable. Performing sanity check on apache2 configuration: Syntax OK Starting apache2. Configuring syscons: blanktime . Starting sshd. Starting cron. Local package initialization: . Starting background file system checks in 60 seconds. FreeBSD 6.2-STABLE #14: Sat Oct 20 15:36:50 PDT 2007 CPU: AMD Opteron(tm) Processor 242 (1593.31- MHz K8-class CPU) Mark -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
term: Undefined variable emitted after startup scripts
On bootup, I see the message repeated several times, term: Undefined variable. What is causing this message and what must I change to eliminate it? I want to rule it out as a factor contributing to my difficulty starting jabberd2 on bootup (c2s is the client-to-server component of jabberd). Starting ntpd. Starting usbd. Starting jabberd. term: Undefined variable. Starting proftpd. Removing stale Samba tdb files: . . . . . . . . done Starting nmbd. ERROR: c2s died. Shutting down server. Starting smbd. Starting mysql. term: Undefined variable. Starting webmin. Starting jabberd_users_agent. Starting mu_conference. term: Undefined variable. Performing sanity check on apache2 configuration: Syntax OK Starting apache2. Configuring syscons: blanktime . Starting sshd. Starting cron. Local package initialization: . Starting background file system checks in 60 seconds. FreeBSD 6.2-STABLE #14: Sat Oct 20 15:36:50 PDT 2007 CPU: AMD Opteron(tm) Processor 242 (1593.31- MHz K8-class CPU) Mark -- [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: build packages recursively from ports collection
On 5 Feb 2004 at 14:49, Didier WIROTH wrote:
{build packages recursively from por...}:
Hi,
I want to use some of our freebsd servers to build .tgz binaries from the
ports collection. Then, I would like to install the packages with pkg_add on
different workstations.
My main problem is how to build packages on servers without installing them!
All i could find or was told, is:
1) make fetch-recursive
2) postinstall -rRp kde
3) portupgrade -frRp kde
All of theses samples installs the ports software!
For example kde:
How do you recursively build .tgz packages of the kde sources and their
dependencies WITHOUT actually installing them on the servers?
On 5 Feb 2004 at 14:49, Didier WIROTH wrote:
{build packages recursively from por...}:
Hi,
I want to use some of our freebsd servers to build .tgz
binaries from the ports collection. Then, I would like to
install the packages with pkg_add on different workstations.
My main problem is how to build packages on servers without
installing them!
All i could find or was told, is:
1) make fetch-recursive
2) postinstall -rRp kde
3) portupgrade -frRp kde
All of theses samples installs the ports software!
For example kde: How do you recursively build .tgz packages
of the kde sources and their dependencies WITHOUT actually
installing them on the servers?
Do you mean, for example:
# cd /usr/port/portname
# make
This creates the ports, plus the dependencies, and does not install
them. To install:
# make install
or better
# make install clean
Mark
--
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
static routes
Where is the best place to put a static route, so that it will renew at bootup? I want to be sure that the interfaces are configured automatically, in case the system is rebooted. Should this go in rc.conf ? Where (the interface? routed?) and with what syntax? Should I place a shell script in /usr/local/etc/rc.d instead? Interactively, for example, I would say at the CLI: route add -net 192.168.2.0 mask 0.0.0.0 192.168.1.1 Where is the best place to put this? Mark -- Mark McConnell - Portland, OR Technical Imaging Systems [EMAIL PROTECTED] 503-546-0517 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: static routes
On 5 Feb 2004 at 16:15, Mark McConnell wrote:
{static routes...}:
(a mistake in my fictitious example)
route add -net 192.168.2.0 mask 0.0.0.0 192.168.1.1
route add -net 192.168.2.0 mask 255.255.255.0 192.168.1.1
Mark
--
Mark McConnell - Portland, OR
Technical Imaging Systems
[EMAIL PROTECTED]
503-546-0517
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bad root shell
su -m only works when you have a bad shell, if your uid is 0
su(1)
-m Leave the environment unmodified. The invoked shell is your
login shell, and no directory changes are made. As a
security
precaution, if the target user's shell is a non-standard
shell
(as defined by getusershell(3)) and the caller's real
uid is non-
zero, su will fail.
But otherwise, yours would be the right answer, I believe.
Mark
--
On 20 Dec 2003 at 23:32, Scott I. Remick wrote:
{Re: bad root shell...}:
On Sat, 20 Dec 2003 09:44:17 -0800, Mark McConnell wrote:
An error in a pw* script inserted a non-existent shell into the password
database, effectively locking out root.
I used a fixit disk to correct the problem, using this procedure:
Unless I'm missing something, seems like the long way to do this. Last
time I did this to myself, I did the following:
1) Log in as a user who can su to root.
2) Use su -m to su to root without changing your current shell
3) As root, use chpass -s to change your shell to a working one.
Of course, this won't work if your only account is root or you don't
have anyone else in the wheel group, so maybe it doesn't apply to you.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Mark McConnell - Portland, OR
Technical Imaging Systems
[EMAIL PROTECTED]
503-546-0517
[EMAIL PROTECTED]
503-257-7591
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
bad root shell
An error in a pw* script inserted a non-existent shell into the password database, effectively locking out root. I used a fixit disk to correct the problem, using this procedure: 1. mount boot drive to /mnt 2. provide myself with a working mkdb and vi (for chpass): # mkdir /usr/sbin /usr/bin # ln -s /mnt/usr/sbin/pwd_mkdb /usr/sbin/pwd_mkdb # ln -s /mnt/usr/bin/vi /usr/bin/vi 3. link pwd.db, spwd.db, group, passwd, master.passwd, ex: # rm /etc/group /etc/spwd.db # for i in `ls /mnt/etc/` ; do ln -s /mnt/etc/$i /etc/$i ; done 4. run mkdb # /usr/sbin/pwd_mkdb master.passwd 5. Using chpass to change root's shell from `badshell' to csh # chpass root :s/badshell/\/bin\/csh/ All of this appears to do work without errors: # pw usershow -u root root:*:0:0::0:0:Charlie :/root:/bin/csh However, when I log in as root, I am still locked out with the message: $ su Password: badshell: No such file or directory I am still stupid. I am still locked out. /etc/passwd and /etc/master.passwd no longer show the badshell. My configuration appears to be deeply broken. Why does my procedure fail? Mark -- Mark McConnell - Portland, OR Technical Imaging Systems [EMAIL PROTECTED] 503-546-0517 [EMAIL PROTECTED] 503-257-7591 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
