ZendOptimizer - core dump
hi, I need to migrate application which uses ZendOptimizer. The system and packages installed are: 8.1-STABLE, apache-2.2.17_2, ZendOptimizer-3.3.0.a, mysql-client-5.5.10, php52-5.2.17, compat6x-amd64-6.4.604000.200810_3. When I run php -v it dumps core. any hints would be greatly appreciated. Has anybody success story running ZendOptimizer? (I read, the support of ZendOptimizer for FreeBSD has been dropped; therefore I cannot use php 5.3) Regards, lk ___ 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
lockf command
Hi, I'm writing a (very simple) script to avoid concurrent processes to do the same task. Background: After a task is done by a service, it synchronizes it with other(s) server(s). I wish that if a synchronization is not done during one or more tasks are completed, not concurrent synchronization processes are launched. According to the flock manual It seems to be simple: If lockf successfully acquires the lock, it returns the exit status produced by command. Otherwise, it returns one of the exit codes defined in sysexits(3), as follows: So this script should work: #!/bin/sh flock -k /tmp/lockfile command arguments But as far as I tested it doesn't act like this : - Command #1 : flock -k /tmp/lockfile read input, the shell is waiting for an input. - Command #2 : flock -k /tmp/lockfile ls -hal /tmp Launching command #1, then #2. The command #2 is waiting. When command #1 is finished command #2 is executed. I wish that if command #2 can't acquire the lock, lockf exits (exit 0 would be nice). If I set -t 1, lockf is quite what I'm waiting for. But I like to do this in a clear way : if it can't acquire the lock it exits, no timeout wait. Am I misunderstanding something ? What should I change ? Thanks for your help -- Bastien Semene Administrateur Réseau Système Cyanide Studio - FRANCE ___ 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: lockf command
On 4/13/2011 12:08 PM, Bastien Semene wrote: I wish that if command #2 can't acquire the lock, lockf exits (exit 0 would be nice). If I set -t 1, lockf is quite what I'm waiting for. But I like to do this in a clear way : if it can't acquire the lock it exits, no timeout wait. Am I misunderstanding something ? What should I change ? You should use -t0, something like: lab# lockf -t 0 /tmp/lock /bin/csh You have mail. lab# lockf -t 0 /tmp/lock /bin/csh lockf: /tmp/lock: already locked lab# echo $? 75 lab# HTH, Nikos ___ 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: lockf command
Hi Nikos, I was stupid not to think about this... And it is a nice tip to use a new shell as a running process. However, I re-read the lockf man and saw : By default, lockf waits indefinitely to acquire the lock. Everything is clear now. Thanks ! Le 13/04/2011 15:23, Nikos Vassiliadis a écrit : On 4/13/2011 12:08 PM, Bastien Semene wrote: I wish that if command #2 can't acquire the lock, lockf exits (exit 0 would be nice). If I set -t 1, lockf is quite what I'm waiting for. But I like to do this in a clear way : if it can't acquire the lock it exits, no timeout wait. Am I misunderstanding something ? What should I change ? You should use -t0, something like: lab# lockf -t 0 /tmp/lock /bin/csh You have mail. lab# lockf -t 0 /tmp/lock /bin/csh lockf: /tmp/lock: already locked lab# echo $? 75 lab# HTH, Nikos ___ 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 ___ 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
Thanks
Very very thanks I was facing very serious problem. ___ 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
Remote access to Freebsd server
Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the open template, tried to disable the packet filter in rc.conf (pf_enable=NO), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ 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: Remote access to Freebsd server
/var/log/security and ipfw list ftw afiddler10 afiddle...@yahoo.com wrote: Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the open template, tried to disable the packet filter in rc.conf (pf_enable=NO), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ 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 ___ 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: Remote access to Freebsd server
/var/log/security and ipfw list ftw. .. if a rule maches your configuration atm afiddler10 afiddle...@yahoo.com wrote: Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the open template, tried to disable the packet filter in rc.conf (pf_enable=NO), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ 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 ___ 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: Remote access to Freebsd server
On 13/04/2011 16:37, afiddler10 wrote: Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. Verb. Sap. Don't confuse FreeBSD with Linux. Especially on FreeBSD mailing lists. It's like mistaking a Scotsman for an Englishman. Tends to cause a lot of red faces and shouting, if not actual fisticuffs... Hmmm... with the firewall config set to 'open', ping should work. Are you behind a NAT gateway? Anyhow, your problem is this: you need to turn /on/ a daemon process to enable remote access. Unlike many widely used OSes, FreeBSD ships with just about everything available in the OS turned off. Which might seem perverse to the uninitiated, but trust me; it's a real blessing over all. Edit the file /etc/rc.conf and add the line: sshd_enable=YES Then run this command as root: # /etc/rc.d/sshd start (you only need to do that as a one-off -- adding the line to rc.conf means the daemon will be started automatically on reboot from now on) Then you can use a SSH client from windows to remote login to your FreeBSD box. If you need a client, try putty from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Nb. by default, you won't be able to SSH in as root -- so set yourself up a normal user account, add it to the wheel group and then use su(1) once you've logged in. As ever, the Handbook is your friend for instructions on how to do this sort of stuff. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Remote access to Freebsd server
Hello 2011/4/13 afiddler10 afiddle...@yahoo.com: Hi, I am new to the Linux environment. FreeBsd its not Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. Try, on the wmware settings network adapter set to bridged. Regards. ___ 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: Remote access to Freebsd server
On Wed, Apr 13, 2011 at 09:40, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 13/04/2011 16:37, afiddler10 wrote: snip problem description and sage advice Edit the file /etc/rc.conf and add the line: sshd_enable=YES Then run this command as root: # /etc/rc.d/sshd start (you only need to do that as a one-off -- adding the line to rc.conf means the daemon will be started automatically on reboot from now on) Then you can use a SSH client from windows to remote login to your FreeBSD box. If you need a client, try putty from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Nb. by default, you won't be able to SSH in as root -- so set yourself up a normal user account, add it to the wheel group and then use su(1) once you've logged in. As ever, the Handbook is your friend for instructions on how to do this sort of stuff. In the interest of preventing newb pain: Please note that the entry for /etc/rc.conf must be exact. In particular, *do not* miss either of the quote marks, or your machine will hang at next boot, and force you to boot into single user mode to recover from it by adding the missing quote mark and booting again. This is not the end of the world, but until you figure it out, it can induce feelings of fear, nausea, helplessness and acute embarrassment. However, about the third time you've done it, and recovered from it by your own efforts, it's no longer a big thing. Kurt ___ 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: Remote access to Freebsd server
2011/4/13 afiddler10 afiddle...@yahoo.com Thank you very much. What I did was set up two interfaces on the VMware server, one bridged and one routed. I was able to access the routed interface from my Windows 7 host. Thanks for your help! You are welcome. Regards. ___ 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
