Re: Newbie question about freebsd-update: single user mode is not needed anymore?
El lunes 31 de diciembre a las 16:27:44 CET, ASV escribió: > Hi Jose, > > with the freebsd-update method you don't need to pass through the "make > installworld" as it's a binary patch/upgrade system. > Using "freebsd-update upgrade -r 9.1-RELEASE" for example allows you to > get your system patched directly without recompiling the kernel and the > userland but getting binary patches from the repo and applying these > directly on your system. > Check the following page for a more detailed explanation and be aware > that upgrading your ports/packages is required every time you upgrade > your kernel to a major version (which would be your case). > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading-freebsdupdate.html > > Happy new year. Thanks for your response. The freebsd-update upgrade method is: 1- freebsd-update install # will install a new kernel and modules 2- reboot in multi user 3- freebsd-update install # will install new userland 4- reboot in multi user The src upgrade method is: 1- make installkernel # will install a new kernel 2- reboot in single user 3- make installworld # will install a new userland 4- reboot in multiuser I think that the third step is essentially the same in both methods: it will install a new userland. But the second one require to be ran in single user, and the first one does not. Why? My unique concern is that step 2 in "freebsd-update" method goes smootly: it will boot kernel in 9.1-RELEASE but userland in 9.0-RELEASE. If the system hangs giving up the net or other essential service, I will not be able to reach the computer via ssh. Regards pgpbaloy3DIlu.pgp Description: PGP signature
Newbie question about freebsd-update: single user mode is not needed anymore?
Hi, I am planning to upgrade from FreeBSD 9.0-RELEASE to FreeBSD-9.1-RELEASE. With upgrade source method, it is always needed to do the "make installworld" step in single user mode. But it seems to be that single user is not required with freebsd-update method, in the second "freebsd-update install". Someone could explain the reason? Am I misunderstanding something? Can I run the upgrade enterely by mean a ssh connection in a safe way, or will I need a serial console? Best regards, and excuse my poor english. pgpswn9DndVD_.pgp Description: PGP signature
Panic in FreeBSD 9.0-RELEASE after reload mountd to export for NFS an UFS snapshot
Hi, Today I have got a panic under the following scenario: * FreeBSD 9.0-RELEASE in VMWare ESXi virtualized host * Very busy host (java compilers, NFS server, lot of UFS snapshots) * apache web server * pgsql and mysql databases * GENERIC kernel The panic happened after: 1- to umount a UFS snapshot mount point 2- to mount other similar UFS snapshot (with snapshot mount /fs:tag /mountpoint) 3- Update /etc/exports to include the previous /mountpoint 4- service mountd reload The crash dump is here: http://www.mipaginapersonal.movistar.es/web3/jjuanino/core.txt.0 Please keep me in CC: Best regards pgpiVcXYsiM8R.pgp Description: PGP signature
Libreoffice daemon in rc script does not work (shell expansion problem)
Hi, I am trying to make an rc script to start libreoffice daemon. The aim is convert Open Document files to PDF, HTML and TXT. The script is the following: #!/bin/sh # # PROVIDE: libreoffice # REQUIRE: LOGIN cleanvar usr # KEYWORD: shutdown . /etc/rc.subr soffice_path="/usr/local/lib/libreoffice/program" name="soffice" #soffice_user="svn" procname="${soffice_path}/oosplash.bin" rcvar=`set_rcvar` pidfile="/var/run/${name}.pid" command="/usr/sbin/daemon" command_args="-p $pidfile" command_args="$command_args ${soffice_path}/${name}" command_args="$command_args '--accept=socket,host=golem,port=8100,tcpNoDelay=1;urp'" command_args="$command_args --nologo --headless --nofirststartwizard --invisible" command_args="$command_args --nolockcheck --norestore" stop_precmd="${name}_prestop" soffice_prestop(){ # kill first child process pkill -P `cat $pidfile` } load_rc_config $name run_rc_command "$1" This script works nicely, and starts libreoffice as a root daemon. But I need to start it as another user (svn), thus I comment out the line #soffice_user="svn" After that, something weird happens with then internal expasion in rc functions, and I get: # service soffice restart Starting soffice. Syntax error: Unterminated quoted string eval: urp --nologo --headless --nofirststartwizard --invisible --nolockcheck --norestore": not found /usr/local/etc/rc.d/soffice: WARNING: failed to start soffice I am unable to fix this... I am trying escaping quotes, using backslashes, etc. Any advice will be wellcome. Best regards pgpT8hmIyuZVF.pgp Description: PGP signature
Re: FreeBSD 7.2 - iwi error
El domingo 28 de junio a las 20:25:51 CEST, Siyan Sabinov Hadzhiev escribió: > > Hello List , > > I am new in this list , so if these is an old topic forgive me.I have > successfully installed FreeBSD 7.2 to IBM T43 Laptop.I am using wireless > network with WPA key.My Laptop has Intel Pro Wireless 2200.I installed > iwi driver and firmware successfully. > > I am successfully connecting to my home and ofis wireless networks with > wpa supplicant.However every 4 or 5 minutes my connection gets down and > i got "iwi0: firmware stuck in state 4 , resetting " and then "iwi0 > device timeout " errors.These drops my connection , after that it take > 30 seconds to my connection come back up.Then after 5 minutes again same > errors and these goes on. > > I search a little bit on Google however find nothing usefull. > > Is there anybody who faced with same problem? > And is there any solutions or upgrades for that issue. I have such wireless interface on a Dell Latitude D505, and I have experienced that annoying problem many times. Enable debug.iwi sysctl and tell us what messages you see in /var/log/messages log file. In my own laptop, I saw these messages before the disconnection: X kernel: Beacon miss: XX >= YY After that I increased bmissthreshold parameter of ifconfig in rc.conf, and the problem went away. Hope this helps, and sorry for my poor english. Best regards pgppxp8Zi1uS2.pgp Description: PGP signature
Re: Can One Query an Oracle 10 Data Base under FreeBSD?
El miércoles 03 de junio a las 00:41:16 CEST, Michael L. Squires escribió: > > There is a port of the Oracle instant client which runs under Linux > emulation in > /usr/ports/databases/linux-oracle-instantclient- > > This appears to use the 10.2.0.3 Oracle Linux instant client. > > I used them some time ago to query an Oracle 10g server, but I didn't test > them extensively. I use sqlplus with instantclient every day and every hour in my FreeBSD desktop, and works perfectly. I had some issues in FreeBSD 7.0: http://lists.freebsd.org/pipermail/freebsd-emulation/2008-September/005247.html but they were fixed in FreeBSD 7.1. Apart from sqlplus with instantcliente, you can give a try to databases/sqldeveloper. It works with java, which has addvantages and dissanvantages. Regards pgpI5W458I0hp.pgp Description: PGP signature
Re: Disabling ssh timeouts?
El miércoles 13 de mayo a las 17:26:10 CEST, Steve Kargl escribió: > On Wed, May 13, 2009 at 04:54:33PM +0200, Jose Garcia Juanino wrote: > > El miércoles 13 de mayo a las 07:03:33 CEST, Steve Kargl escribió: > > > Is there anyway to disable sshd from timing out a connection? > > > I've tried setting ClientAliveCountMax and ClientAliveInterval > > > and TCPKeepAlive in sshd.conf, but no combination that I've > > > tried has worked. > > > > > > > > > Running /usr/home/sgk/gcc/gcc4x/gcc/testsuite/gfortran.dg/dg.exp ... > > > > > > Read from remote host troutmask.apl.washington.edu: Connection reset by > > > peer > > > Connection to troutmask.apl.washington.edu closed. > > > > > > The only way I'v efound to complete a run of the GCC testsuite > > > is to sit at the terminal and hit enter every so often. Also > > > note, nohup and backgrounding the job does not inhibit sshd > > > dropping the connection and losing all testsuite results. > > > > I have fixed that problems with ServerAliveInterval option. Give it a > > try: > > > > ssh -o "ServerAliveInterval 60" -l > > > > (screen is a goog idea, as other people have pointed out, but sometimes > > it is not posible to install programs on the server) > > > > Thanks for the tip about ServerAliveInterval. > > Also, thanks, everyone for the tip about screen. A last tip, if ServerAliveInterval does not work as expected: $ ssh -l $ gccCompilation > /tmp/gccCompilation.log 2>&1 < /dev/null At this point, it would be possible to exit from the ssh session with "exit" or CTRL+D. Yo only must to guaranteed this process will not output anything to stdout, and will not read anything from stdin. Best regards pgp9yBjH0PkMU.pgp Description: PGP signature
Re: Disabling ssh timeouts?
El miércoles 13 de mayo a las 07:03:33 CEST, Steve Kargl escribió: > Is there anyway to disable sshd from timing out a connection? > I've tried setting ClientAliveCountMax and ClientAliveInterval > and TCPKeepAlive in sshd.conf, but no combination that I've > tried has worked. > > [ ... ] > > Running /usr/home/sgk/gcc/gcc4x/gcc/testsuite/gfortran.dg/dg.exp ... > > Read from remote host troutmask.apl.washington.edu: Connection reset by peer > Connection to troutmask.apl.washington.edu closed. > > The only way I'v efound to complete a run of the GCC testsuite > is to sit at the terminal and hit enter every so often. Also > note, nohup and backgrounding the job does not inhibit sshd > dropping the connection and losing all testsuite results. I have fixed that problems with ServerAliveInterval option. Give it a try: ssh -o "ServerAliveInterval 60" -l (screen is a goog idea, as other people have pointed out, but sometimes it is not posible to install programs on the server) Best regards pgpbisLSG699F.pgp Description: PGP signature
Re: How to move vi to /bin
El miércoles 13 de mayo a las 09:21:46 CEST, manish jain escribió: > Hi, > > I want to move vi to /bin so that I have an editor available in > single-user mode. This sounds simple (and should be if all you have is > a single partition), but there are problems. For starters, terminfo > can't locate its database in single-user mode. > > Could anyone please tell me how to go about this on a 7.x system ? I > am also curious to know why FreeBSD doesn't place vi under /bin in the > first place. Try /rescue/vi in single user mode. Before that, you must copy /usr/share/misc/termcap.db to /root/.termcap.db (/root is the HOME of user root). Best regards. pgp1W7b5kEWf4.pgp Description: PGP signature
Re: FreeBSD 6.3 xl0: watchdog timeout
El sábado 29 de marzo a las 19:07:37 CET > Hi > > I have a problen with FreeBSD 6.3. When I boot, I get the message > xl0: watchdog timeout > and I have no networking. I have 3com ethernet card. > > If i make ping on localhost it works good. But if i try to ping anything > else it didn't work. When I plug the 3com ethernet card into other > systemblock with FreeBSD 6.2, and activeted it. All worked good. > > Help to solve this problem. Maby it is problem with BIOS? Have you ACPI enabled? If so, disable ACPI and try again. Regards pgp6kEcccshZA.pgp Description: PGP signature
It is safe to build ports for 7.0 from a 6.3 chroot?
Hi everybody Actually, I do the following in order to update from 6.3 to 7.0: 1) dump my actual 6.3 filesystems /, /var and /usr into three new ones: /rel70, /rel70/usr and /rel70/var (I use the dump command, of course) 2) chroot /rel70 and mergemaster -p + buildkernel + buildworld + installkernel + installworld + mergemaster -i and such stuff 3) Inside the chroot, rebuild the ports 4) Reboot the new release Will I go into problems following this approach? The step 3) is the most dangerous, I believe, as I have executing 7.0 commands on a 6.3 kernel (even though only for compilation). Best regards pgp47kcDn5bMv.pgp Description: PGP signature
Re: Still having problems burning DVDs
El sábado 29 de diciembre a las 23:41:34 CET, Andrew Falanga escribió: > Ok, > > Thanks to the help of earlier posts (a couple of weeks ago), using > "kldload atapicam" now allows for the scsi ioctls on my IDE CD/DVD > burner. > > However, when I do the following: > > growisofs -Z /dev/cd0 -dvd-video /usr/local/dvds/whereisGod1.iso > > I get this output: > Executing 'mkisofs -dvd-video /usr/local/dvds/whereisGod1.iso | builtin_dd > of=/dev/pass0 obs=32k seek=0' > mkisofs: Value too large to be stored in data type. > File /usr/local/dvds/whereisGod1.iso is too large - ignoring > mkisofs: Unable to make a DVD-Video image. > :-( write failed: Input/output error > > > Now, what is causing this? The command I'm using is right off of the > handbook > for creating DVD video: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/creating-dvds.html > > And the size of this file is: > > -rw-r--r-- 1 root wheel 4317872128 Nov 21 16:30 whereisGod1.iso > > > That's slightly smaller than the 4.7 gb that the DVD+R says it will hold. > Please keep in mind that this iso file I've made is from doing: > > cp /dev/acd0 /usr/local/dvds/whereisGod1.iso I think it should be: dd if=/dev/acd0 of=/usr/local/dvds/whereisGod1.iso bs=2048 Check whether the output of "file whereisGod1.iso" is "ISO 9660 CD-ROM filesystem data" or similar. Regards pgpQ4VXeAU7KR.pgp Description: PGP signature