Re: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Wed, 29 Jul 2009, Doug Barton wrote: Dan Mahoney, System Admin wrote: The fact that the error occurs AT ALL is the bug and what is counterintuitive, and many people would not think to try typing make again, and instead would just assume the thing's broken. Ok, I actually misunderstood the problem that you were reporting. I thought that the reference to .build_done.bind96._usr_local indicated that the port had already been built once, but that is not the case. To reproduce the bug, you need to do the following: 1. Make sure there is nothing in /var/db/ports/bind96 2. cd /usr/ports/dns/bind96 3. make 4. Enable the replace base option 5. Save the config You will then see the following error: make: don't know how to make /usr/local/tmp/usr/local/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 I think Mel is right that the problem is changing PREFIX, but that's the whole purpose of the option. Could you please open a PR about this with a subject something to the effect of OPTIONS that change PREFIX cause an error after 'make config' and describe how to reproduce this? Done, just got the mail from gnats: 137250. -Dan -- Pika Pika Pika! -Pikachu, of Pokemon fame. Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.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
Don't know how to make /usr/ports/dns/bind96/work/.build....
Hey all, I'm having a problem on multiple systems: With a clean port, in dns/bind96: I get the options screen, I select only overwrite base in addition to the defaults:, and after, I get this: make: don't know how to make /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 Stop in /usr/ports/dns/bind96. s1# Additional builds go fine. Someone else had the same problem, and they also chose overwrite-base: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035.html But it was dismissed because he was using sudo, however the real reason is because this problem goes away a second time. -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.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: Don't know how to make /usr/ports/dns/bind96/work/.build....
On Tuesday 28 July 2009 20:24:27 Dan Mahoney, System Admin wrote: make: don't know how to make /usr/ports/dns/bind96/work/.build_done.bind96._usr_local. Stop *** Error code 2 Someone else had the same problem, and they also chose overwrite-base: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2007-08/msg00035. html But it was dismissed because he was using sudo, however the real reason is because this problem goes away a second time. Most likely because that option changes PREFIX, so the BUILD_COOKIE changed, but the target was already in make's list of targets to make. After options are stored in /var/db/ports, BUILD_COOKIE will end in ._usr. -- Mel ___ 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
Now pkg-config trouble.................Re: startx does not work, startxfce4 does!
Hi, Leslie Try this. Create a file: $HOME/.xinitrc containing: /usr/local/bin/startxfce4 Then give 'startx' another shot. I did all the things suggested here at the list with no success so I decided to clean out and start over. did pkg_delete -f '*' rm -r /usr/ports/distfiles rm -r /usr/local/* Then I installed sysutils/screen ports-mgmt/portupgrade ports-mgmt/portmaster And started installation of x11/xorg But it fails rather quickly with the message below: I've attached the log file and output suggested in the message. One thing that I see is the path to pkg-config is :whereis pkg-config pkg-config: /usr/ports/devel/pkg-config where as on my other machine I've got whereis pkg-config pkg-config: /usr/local/bin/pkg-config /usr/local/man/man1/pkg-config.1.gz /usr/ports/devel/pkg-config I tried /usr/ports/devel/pkg-config:make install clean === Cleaning for gmake-3.81_3 === Cleaning for gettext-0.17_1 === Cleaning for libtool-1.5.26 === Cleaning for libiconv-1.13 === Cleaning for pkg-config-0.23_1 /usr/ports/devel/pkg-config:rehash /usr/ports/devel/pkg-config:whereis pkg-config pkg-config: /usr/ports/devel/pkg-config As you can see in the listing below pkg-config is not listed as installed! That's proberly the source of the install failure, so how do I get pkg-config to install? --- checking dependency style of cc... gcc3 checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel checking for pkg-config... no checking for XSETROOT... configure: error: The pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config. Alternatively, you may set the environment variables XSETROOT_CFLAGS and XSETROOT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. To get pkg-config, see http://www.freedesktop.org/software/pkgconfig. See `config.log' for more details. === Script configure failed unexpectedly. Please report the problem to x...@freebsd.org [maintainer] and attach the /usr/ports/x11/xsetroot/work/xsetroot-1.0.2/config.log including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/x11/xsetroot. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg-apps. *** Error code 1 Stop in /usr/ports/x11/xorg. r...@blj01/usr/ports/x11/xorg: -- - ll /var/db/pkg total 25810 drwxr-xr-x 2 root wheel 512 Jun 19 06:14 db43-4.3.29_1/ -rw-r--r-- 1 root wheel 26382336 Jun 18 20:19 pkgdb.db drwxr-xr-x 2 root wheel 512 Jun 19 06:05 portmaster-2.7/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 portupgrade-2.4.6_2,2/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 ruby-1.8.7.160_2,1/ drwxr-xr-x 2 root wheel 512 Jun 19 06:14 ruby18-bdb43-0.6.5_1/ drwxr-xr-x 2 root wheel 512 Jun 19 06:00 screen-4.0.3_6/ drwxr-xr-x 2 root wheel 512 Jun 19 06:04 sudo-1.6.9.20/ This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by xsetroot configure 1.0.2, which was generated by GNU Autoconf 2.59. Invocation command line was $ ./configure --x-libraries=/usr/local/lib --x-includes=/usr/local/include --prefix=/usr/local --mandir=/usr/local/man --infodir=/usr/local/info/ --build=i386-portbld-freebsd7.2 ## - ## ## Platform. ## ## - ## hostname = uname -m = i386 uname -r = 7.2-RELEASE uname -s = FreeBSD uname -v = FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC /usr/bin/uname -p = i386 /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /sbin PATH: /bin PATH: /usr/sbin PATH: /usr/bin PATH: /usr/games PATH: /usr/local/sbin PATH: /usr/local/bin PATH: /usr/X11R6/bin PATH: /root/bin ## --- ## ## Core tests. ## ## --- ## configure:1340: checking for a BSD-compatible install configure:1395: result: /usr/bin/install -c -o root -g wheel configure:1406: checking whether build environment is sane configure:1449: result: yes configure:1514: checking for gawk configure:1543: result: no configure:1514: checking for mawk configure:1543: result: no configure:1514: checking for nawk configure:1530: found /usr/bin/nawk configure:1540: result: nawk configure:1550: checking whether make sets $(MAKE) configure:1570: result: yes configure:1738: checking
Re: Now pkg-config trouble.................Re: startx does not work, startxfce4 does!
Leslie, The given port dirs (x11/xorg, etc) still probably have their work directory, which have the tokens/markers that particular stages of the port build have been done, such as the installation. rm -rf /usr/ports/*/*/work rehash cd /usr/ports/x11/xorg make install Please try that. First removes the work dir that contains the tokens, second updates root's available application hash, third and forth rebuild xorg Since xorg is so large, and receives very few (in relation to the total number of packages) updates, a quick-n-dirty way to get running is to add the package, and then update the outdated ones. pkg_add -r xorg portmaster -a I follow this same pattern on all BIG ports.. gnome2, kde3/4, xorg, and then let the portmaster update the old outdated ports that got installed. There is no functional difference between a package installed and a port installed with no options/config tweaked. Please try this. Write to us if you keep having problems ___ 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
startx does not work, startxfce4 does!
On a newly installed 7.2-RELEASE system with all ports upgraded and cvsup'ed I have a problem. Both root and user has .xsession linked to .xinitrc and contains #!/bin/sh exec /usr/local/bin/startxfce4 If I execute startx as root TWM is started! If I execute startxfce4 as root XFCE4 is started If I execute startx as user I get a black screen that after some minutes returns to the prompt. If I execute startxfce4 as user XFCE4 is started I've checked the rights on startx and startxfce4 plus .xsession and .xinitrc and they are the same as I have on another 7.2 system that works. I could need some help to find the problem. Thanks Leslie ___ 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: startx does not work, startxfce4 does!
On Wed, Jun 17, 2009 at 12:27 PM, Leslie Jensenles...@eskk.nu wrote: On a newly installed 7.2-RELEASE system with all ports upgraded and cvsup'ed I have a problem. Both root and user has .xsession linked to .xinitrc and contains #!/bin/sh exec /usr/local/bin/startxfce4 If I execute startx as root TWM is started! If I execute startxfce4 as root XFCE4 is started If I execute startx as user I get a black screen that after some minutes returns to the prompt. If I execute startxfce4 as user XFCE4 is started I've checked the rights on startx and startxfce4 plus .xsession and .xinitrc and they are the same as I have on another 7.2 system that works. I could need some help to find the problem. Hi, Leslie Try this. Create a file: $HOME/.xinitrc containing: /usr/local/bin/startxfce4 Then give 'startx' another shot. -- Glen Barber ___ 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: startx does not work, startxfce4 does!
On Wednesday 17 June 2009 08:27:41 Leslie Jensen wrote: On a newly installed 7.2-RELEASE system with all ports upgraded and cvsup'ed I have a problem. Both root and user has .xsession linked to .xinitrc and contains #!/bin/sh Remove the she-bang and make sure .xinitrc is in $HOME. If this still don't work, check /var/log/Xorg.0.log for anything (EE). -- Mel ___ 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
Any chance to get the SANE epkowa backend to work on Freebsd?
I got a good deal on a Epson Perfection 4490 PHOTO scanner, but it's not supported by the SANE Epson backend. One needs the epkowa external backend. Any chance to make it work? /Leslie ___ 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
glabel(8) a gmirror(8) doesn't work
Hello community, Yesterday I have installed FBSD 7.2-RELEASE. I have installed on a mirror created with gmirror(8). All I have modified on this system is that I have updated the sources, rebuild the world and kernel and of course install. I have named the mirror system0 and all worked well. Now the problem is that i want to glabel the partitions on the mirror so i have followed the following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. After reading the man of gmirrror(8) and glabel(8) i have noticed that both of them store metadata on the last sector of the provider. From this results that what I want to do is not possible, at least my logic tells me that. Since gmirror wrote metadata to the last sector of the provider, glabel tries to rewrite it and the system stops the process to protect the filesystem. But then again for gmirror the providers are the two hdd i use for mirroring and for glabel the provider is the mirror itself. That's again what my logic tells me. So i think there is some kind of separation between the two modules and things should work. I have searched a bit but couldn't find any relevant info on labeling a mirror. I just want to know if this is possible and if it's not I'd like to understand why. Labeling a partition is not a must-have but it's sure nice :). thanks, v -- network warrior since 2005 ___ 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: glabel(8) a gmirror(8) doesn't work
following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. replace mount -a with mount / you can't write directly to partition which is mounted mounted ___ 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: glabel(8) a gmirror(8) doesn't work
On Wed, Jun 10, 2009 at 9:58 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. replace mount -a with mount / you can't write directly to partition which is mounted mounted Thanks this time it worked. I am almost sure (99%) I've tried that already yesterday but the 1% wins. One more question can i label the / partition. I have the same error when i try to label it. v -- network warrior since 2005 ___ 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: glabel(8) a gmirror(8) doesn't work
Valentin Bud wrote: On Wed, Jun 10, 2009 at 9:58 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. replace mount -a with mount / you can't write directly to partition which is mounted mounted Thanks this time it worked. I am almost sure (99%) I've tried that already yesterday but the 1% wins. One more question can i label the / partition. I have the same error when i try to label it. v You should be able to. Just reboot into single user mode and *do not* enter any mount commands. The / partition is mounted read only in this case, and tunefs -L will succeed. ___ 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: glabel(8) a gmirror(8) doesn't work
Thanks this time it worked. I am almost sure (99%) I've tried that already yesterday but the 1% wins. One more question can i label the / partition. I have the same error when i try to label it. don't do mount / or boot from liveCD ___ 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: glabel(8) a gmirror(8) doesn't work
On Wed, Jun 10, 2009 at 12:25 PM, Manolis Kiagias son...@otenet.gr wrote: Valentin Bud wrote: On Wed, Jun 10, 2009 at 9:58 AM, Wojciech Puchar woj...@wojtek.tensor.gdynia.pl wrote: following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. replace mount -a with mount / you can't write directly to partition which is mounted mounted Thanks this time it worked. I am almost sure (99%) I've tried that already yesterday but the 1% wins. One more question can i label the / partition. I have the same error when i try to label it. v You should be able to. Just reboot into single user mode and *do not* enter any mount commands. The / partition is mounted read only in this case, and tunefs -L will succeed. Yes it worked. Thank you very much. The odd thing is that I once tried to label it after mounting / and rw and afterward changed it to ro with the help of mount and it did not work. a great day, v -- network warrior since 2005 ___ 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: glabel(8) a gmirror(8) doesn't work
List members; http://www.freebsd.org/doc/en/books/handbook/geom-glabel.html Starting with FreeBSD 7.2, the glabel(8) class supports a new label type for UFS file systems, based on the unique file system id, ufsid. Is the above clause applicable in this case ? instead of using tunefs -L can we use# glabel status ? and can use the ufsid labels of /dev/ufsid/and edit /etc/fstab entries for the partitions? From: valentin@gmail.com Date: Wed, 10 Jun 2009 09:12:47 +0300 To: freebsd-questions@freebsd.org Subject: glabel(8) a gmirror(8) doesn't work Hello community, Yesterday I have installed FBSD 7.2-RELEASE. I have installed on a mirror created with gmirror(8). All I have modified on this system is that I have updated the sources, rebuild the world and kernel and of course install. I have named the mirror system0 and all worked well. Now the problem is that i want to glabel the partitions on the mirror so i have followed the following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. After reading the man of gmirrror(8) and glabel(8) i have noticed that both of them store metadata on the last sector of the provider. From this results that what I want to do is not possible, at least my logic tells me that. Since gmirror wrote metadata to the last sector of the provider, glabel tries to rewrite it and the system stops the process to protect the filesystem. But then again for gmirror the providers are the two hdd i use for mirroring and for glabel the provider is the mirror itself. That's again what my logic tells me. So i think there is some kind of separation between the two modules and things should work. I have searched a bit but couldn't find any relevant info on labeling a mirror. I just want to know if this is possible and if it's not I'd like to understand why. Labeling a partition is not a must-have but it's sure nice :). thanks, v -- network warrior since 2005 ___ 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 _ cricket and news. Logon to MSN Video for the latest clips http://www.exploremyway.com___ 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: glabel(8) a gmirror(8) doesn't work
On Wed, Jun 10, 2009 at 3:20 PM, dhaneshk k dhanes...@hotmail.com wrote: List members; http://www.freebsd.org/doc/en/books/handbook/geom-glabel.html Starting with FreeBSD 7.2, the glabel(8)http://www.FreeBSD.org/cgi/man.cgi?query=glabelsektion=8class supports a new label type for UFS file systems, based on the unique file system id, ufsid. Is the above clause applicable in this case ? instead of using tunefs -L can we use# glabel status ? and can use the ufsid labels of /dev/ufsid/and edit /etc/fstab entries for the partitions? Well yes you are right. The point of labeling the partitions was/is to make the names more easier to remember IMO. Remembering a string (the ufsid) is not quite my specialty. Anyway thanks for the heads up. v From: valentin@gmail.com Date: Wed, 10 Jun 2009 09:12:47 +0300 To: freebsd-questions@freebsd.org Subject: glabel(8) a gmirror(8) doesn't work Hello community, Yesterday I have installed FBSD 7.2-RELEASE. I have installed on a mirror created with gmirror(8). All I have modified on this system is that I have updated the sources, rebuild the world and kernel and of course install. I have named the mirror system0 and all worked well. Now the problem is that i want to glabel the partitions on the mirror so i have followed the following procedure: 1. reboot to single user 2. mount -a 3. tunefs -L var /dev/mirror/system0s1d This commands exits with Failed to write superblock. After reading the man of gmirrror(8) and glabel(8) i have noticed that both of them store metadata on the last sector of the provider. From this results that what I want to do is not possible, at least my logic tells me that. Since gmirror wrote metadata to the last sector of the provider, glabel tries to rewrite it and the system stops the process to protect the filesystem. But then again for gmirror the providers are the two hdd i use for mirroring and for glabel the provider is the mirror itself. That's again what my logic tells me. So i think there is some kind of separation between the two modules and things should work. I have searched a bit but couldn't find any relevant info on labeling a mirror. I just want to know if this is possible and if it's not I'd like to understand why. Labeling a partition is not a must-have but it's sure nice :). thanks, v -- network warrior since 2005 ___ 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 -- Get easy photo sharing with Windows LiveT Photos. Drag n' drophttp://www.microsoft.com/india/windows/windowslive/photos.aspx -- network warrior since 2005 ___ 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: glabel(8) a gmirror(8) doesn't work
dhaneshk k wrote: List members; http://www.freebsd.org/doc/en/books/handbook/geom-glabel.html Starting with FreeBSD 7.2, the glabel(8) class supports a new label type for UFS file systems, based on the unique file system id, ufsid. Is the above clause applicable in this case ? instead of using tunefs -L can we use# glabel status ? and can use the ufsid labels of /dev/ufsid/and edit /etc/fstab entries for the partitions? Yes, exactly as noted in the Handbook's example. Still ufsid labels are not exactly 'memorable' ___ 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: /etc/hosts - how does that file work?? - was weird nfs issues.
On Saturday 06 June 2009 20:44:38 Tim Judd wrote: On 6/4/09, Peter fb...@peterk.org wrote: I do not think /etc/hosts does round robin, I always assumed first match wins...DNS/bind I would understand... It's the same library call: gethostbyname(3) and friends. Why does ping always return the 172.20.6.1 address, and ftp,nc,ssh,telnet,fetch _always_ uses the 116 address? Again: client implementation is allowed to pick whichever it wants. why are you so hung up on dual IPs for a single host? would dnsmasq provide a solution to dual A records for one resource? Gotta agree with Tim here. I don't see the point for having two nets on one interface. They'll be hard to keep secure with firewall rules if you run the same services on them. I'll help, when I can. but forcing this on /etc/hosts is a dead end. Problem is that nfs and DNS don't work well at all. For nfs best use IP or /etc/hosts. One drawback of using DNS with nfs is that if the hostname cannot be resolved (network down, typo), one can also not get a console when it goes to single user mode [1] and has to reboot via power button. /etc/fstab is supposed to be static to begin with. It's supposed to provide the mountpoints the system can count on, so using IP's for nfs is preferred. For the more dynamic nfs mounts, one can use hostnames and use noauto in the options column. [1] http://www.freebsd.org/cgi/query-pr.cgi?pr=128448 -- Mel ___ 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: /etc/hosts - how does that file work?? - was weird nfs issues.
On 6/4/09, Peter fb...@peterk.org wrote: On Thursday 04 June 2009 20:48:21 Peter wrote: iH, This all started with NFS not mounting at bootso, testing in VMs: snip Why is ping using one IP, and ssh/mount_nfs/showmount using another IP from /etc/hosts? Q: Where is described that name resolution for A or PTR records should be returned in a fixed order and that a consumer should always use the first one returned? A: Nowhere. Name servers are encouraged to do round-robin returns if not specified otherwise. Applications may sort/pick at their own leisure. -- Mel I do not think /etc/hosts does round robin, I always assumed first match wins...DNS/bind I would understand... Why does ping always return the 172.20.6.1 address, and ftp,nc,ssh,telnet,fetch _always_ uses the 116 address? I would assume at least sometimes it would hit the 172 address with anything besides ping - but it only ping hits the 172 address... If so, I'd guess there would be consistency between ping lookups and 'telnet/ssh/etc' lookups... Why if the 116.23.45.3 last octet is bumped up, everything _always_ returns the 172 address? client# grep server /etc/hosts 172.20.6.1 server.test server 116.23.45.5 server.test server client# telnet server Trying 172.20.6.1... telnet: connect to address 172.20.6.1: Connection refused Trying 116.23.45.5... /etc/hosts - 'server' changed to 116.23.45.3: client# telnet server Trying 116.23.45.3... telnet: connect to address 116.23.45.3: Operation timed out Trying 172.20.6.1... telnet: connect to address 172.20.6.1: Connection refused telnet: Unable to connect to remote host if server has ip116.23.45.3, it always uses the 172 address first... but ping always uses the 172... even if third entry is added into /etc/hosts - nothing ever uses it as the first/primary IP. Is there an algorithm based on IP/program being used and the returned IP? I can't sit and watch this thread anymore. Something itchin' to say: DNS, who can handle multiple A records in an optional round-robin design, is perfectly fine to assign multiple A records to a resource. /etc/hosts, which as always existed (back when the Internet was created/new), was a unique record source only. Having oddities in /etc/hosts is expected IMHO when a mistake like multiple resources assigned different records. What's to stop you from creating slightly different records in /etc/hosts? Whats to stop you from hitting 'privserver' and 'pubserver', for private and public IPs respectively. why are you so hung up on dual IPs for a single host? would dnsmasq provide a solution to dual A records for one resource? I'll help, when I can. but forcing this on /etc/hosts is a dead end. ___ 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
/etc/hosts - how does that file work?? - was weird nfs issues.
iH, This all started with NFS not mounting at bootso, testing in VMs: This is a fresh/generic install of 7.2-REL no firewall em1=10.21.20.0/24 network - DHCP for ssh access client# uname -a FreeBSD client.test 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 r...@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 client# cat /etc/rc.conf gateway_enable=YES hostname=client.test ifconfig_em0=inet 172.20.6.2 netmask 255.255.255.0 ifconfig_em0_alias0=inet 116.23.45.2 netmask 255.255.255.0 ifconfig_em1=DHCP nfs_client_enable=YES nfs_server_enable=NO rpcbind_enable=NO sshd_enable=YES client# ifconfig em0|grep inet inet 172.20.6.2 netmask 0xff00 broadcast 172.20.6.255 inet 116.23.45.2 netmask 0xff00 broadcast 116.23.45.255 client# cat /etc/hosts ::1 localhost localhost.test 127.0.0.1 localhost localhost.test 172.20.6.2 client.test client 116.23.45.2 client.test client 172.20.6.1 server.test server 116.23.45.3 server.test server client# ping -c1 server PING server.test (172.20.6.1): 56 data bytes 64 bytes from 172.20.6.1: icmp_seq=0 ttl=64 time=5.811 ms --- server.test ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 5.811/5.811/5.811/0.000 ms client# ssh -vvv server OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to server.test [116.23.45.3] port 22. ^C client# ssh to 'server' always goes to 116.23.45.3 IP there is nothing on '116.23.45.3' IP '116.23.45.3/24' is a made up network for testing BUT... client# ifconfig em0|grep inet inet 172.20.6.2 netmask 0xff00 broadcast 172.20.6.255 inet 116.23.45.2 netmask 0xff00 broadcast 116.23.45.255 client# cat /etc/hosts ::1 localhost localhost.test 127.0.0.1 localhost localhost.test 172.20.6.2 client.test client 116.23.45.2 client.test client 172.20.6.1 server.test server 116.23.45.4 server.test server client# ping -c1 server PING server.test (172.20.6.1): 56 data bytes 64 bytes from 172.20.6.1: icmp_seq=0 ttl=64 time=0.285 ms --- server.test ping statistics --- 1 packets transmitted, 1 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.285/0.285/0.285/0.000 ms client# ssh -vvv server OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug2: ssh_connect: needpriv 0 debug1: Connecting to server.test [172.20.6.1] port 22. debug1: Connection established. ... .. Why if the secondary entry is higher than '116.23.45.3' it always goes to 172/24 network? Why is ping using one IP, and ssh/mount_nfs/showmount using another IP from /etc/hosts? ]confused[ ___ 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: /etc/hosts - how does that file work?? - was weird nfs issues.
On Thursday 04 June 2009 20:48:21 Peter wrote: iH, This all started with NFS not mounting at bootso, testing in VMs: snip Why is ping using one IP, and ssh/mount_nfs/showmount using another IP from /etc/hosts? Q: Where is described that name resolution for A or PTR records should be returned in a fixed order and that a consumer should always use the first one returned? A: Nowhere. Name servers are encouraged to do round-robin returns if not specified otherwise. Applications may sort/pick at their own leisure. -- Mel ___ 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: /etc/hosts - how does that file work?? - was weird nfs issues.
On Thursday 04 June 2009 20:48:21 Peter wrote: iH, This all started with NFS not mounting at bootso, testing in VMs: snip Why is ping using one IP, and ssh/mount_nfs/showmount using another IP from /etc/hosts? Q: Where is described that name resolution for A or PTR records should be returned in a fixed order and that a consumer should always use the first one returned? A: Nowhere. Name servers are encouraged to do round-robin returns if not specified otherwise. Applications may sort/pick at their own leisure. -- Mel I do not think /etc/hosts does round robin, I always assumed first match wins...DNS/bind I would understand... Why does ping always return the 172.20.6.1 address, and ftp,nc,ssh,telnet,fetch _always_ uses the 116 address? I would assume at least sometimes it would hit the 172 address with anything besides ping - but it only ping hits the 172 address... If so, I'd guess there would be consistency between ping lookups and 'telnet/ssh/etc' lookups... Why if the 116.23.45.3 last octet is bumped up, everything _always_ returns the 172 address? client# grep server /etc/hosts 172.20.6.1 server.test server 116.23.45.5 server.test server client# telnet server Trying 172.20.6.1... telnet: connect to address 172.20.6.1: Connection refused Trying 116.23.45.5... /etc/hosts - 'server' changed to 116.23.45.3: client# telnet server Trying 116.23.45.3... telnet: connect to address 116.23.45.3: Operation timed out Trying 172.20.6.1... telnet: connect to address 172.20.6.1: Connection refused telnet: Unable to connect to remote host if server has ip116.23.45.3, it always uses the 172 address first... but ping always uses the 172... even if third entry is added into /etc/hosts - nothing ever uses it as the first/primary IP. Is there an algorithm based on IP/program being used and the returned IP? ___ 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
Debugging multithreaded programs with gdb66 doesn't work
Hi there, I'm trying to debug some multithreaded programs with gdb 6.6, however commands such as info threads or threads apply all bt simply do nothing and show nothing. Am I missing something here? Is this the appropriate list to ask? Thanks, Raphael ___ 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: Why would a kill -2 not work?
The pthread_* calls you are making aren't listed as being safe to run within the context of a signal handler, and could cause a thread waiting on that condition to be unblocked and start running. Please see earlier comments about mixing threads and signal handlers. Okay, fair enough. I'll rework our signal handler logic to avoid using any calls that are not considered signal-safe. Better to be safe than sorry... :-) Thanks for the feedback. ___ 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
Why would a kill -2 not work?
Under what circumstances might a kill -2 nnn not work. I have a Python app with a signal handler configured to catch INT signals. It seems to work fine, but we've recently noticed that after the app has run for a while the kill -2 no longer works. This seems pretty suspicious, perhaps indicating our app is misbehaving in some way. What might cause the signal handler to stop working? Is there a better list for this question? ___ 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: Why would a kill -2 not work?
Hi-- On May 18, 2009, at 9:23 AM, Peter Steele wrote: Under what circumstances might a kill -2 nnn not work. I have a Python app with a signal handler configured to catch INT signals. It seems to work fine, but we've recently noticed that after the app has run for a while the kill -2 no longer works. This seems pretty suspicious, perhaps indicating our app is misbehaving in some way. What might cause the signal handler to stop working? The main reason might be that your process is already in another signal handler or is otherwise blocked in a system call and won't get the new signal until it completes the current situation. The amount of stuff you're allowed to do safely in a signal handler is pretty minimal-- you're better off setting a flag, returning from the signal handler, and having the next run past the main event loop or whatever check for the flag and handle things in a normal app context. If you try to do anything involving malloc() or s/printf, etc, you're running risks. man sigaction is likely to be informative Regards, -- -Chuck ___ 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: Why would a kill -2 not work?
The amount of stuff you're allowed to do safely in a signal handler is pretty minimal-- you're better off setting a flag, returning from the signal handler, and having the next run past the main event loop or whatever check for the flag and handle things in a normal app context. If you try to do anything involving malloc() or s/printf, etc, you're running risks. man sigaction is likely to be informative This is basically what we doing. When the handler is triggered we set a global variable to indicate the system is shutting down. I also signal a condition to wake up a sleeping thread. The lack of log messages indicate that this handler never gets called and the system carries on as if the kill -2 never happened. ___ 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: Why would a kill -2 not work?
Hi-- On May 18, 2009, at 2:45 PM, Peter Steele wrote: This is basically what we doing. When the handler is triggered we set a global variable to indicate the system is shutting down. I also signal a condition to wake up a sleeping thread. The lack of log messages indicate that this handler never gets called and the system carries on as if the kill -2 never happened. You're not trying to send a signal within the signal handler itself, are you? That won't work-- signal delivery is blocked when you're already running in a signal handler. Also, note that trying to mix signals with a multithreaded process is complicated -- -Chuck ___ 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: Why would a kill -2 not work?
What he said. It's better to just stick with -9; it almost always works! ;-) -Original Message- From: owner-freebsd-questi...@freebsd.org [mailto:owner-freebsd-questi...@freebsd.org] On Behalf Of Chuck Swiger Sent: Monday, May 18, 2009 4:49 PM To: Peter Steele Cc: #freebsd-questions Subject: Re: Why would a kill -2 not work? Hi-- On May 18, 2009, at 2:45 PM, Peter Steele wrote: This is basically what we doing. When the handler is triggered we set a global variable to indicate the system is shutting down. I also signal a condition to wake up a sleeping thread. The lack of log messages indicate that this handler never gets called and the system carries on as if the kill -2 never happened. You're not trying to send a signal within the signal handler itself, are you? That won't work-- signal delivery is blocked when you're already running in a signal handler. Also, note that trying to mix signals with a multithreaded process is complicated -- -Chuck ___ 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 font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ 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: Why would a kill -2 not work?
You're not trying to send a signal within the signal handler itself, are you? That won't work-- signal delivery is blocked when you're already running in a signal handler. Also, note that trying to mix signals with a multithreaded process is complicated No, I'm not sending a signal within a signal. The signal handler is this: pthread_mutex_lock(keep_running_mutex); KEEP_RUNNING = 0; pthread_cond_signal(keep_running_cond); pthread_mutex_unlock(keep_running_mutex); This works fine, but at some point it seems to stop working. The app just continues to run as if it never received the -2 signal. We have to use a kill -9 to kill it, which we want to avoid because this prevents our shutdown code from executing. ___ 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: Why would a kill -2 not work?
On May 18, 2009, at 5:32 PM, Peter Steele wrote: No, I'm not sending a signal within a signal. The signal handler is this: pthread_mutex_lock(keep_running_mutex); KEEP_RUNNING = 0; pthread_cond_signal(keep_running_cond); pthread_mutex_unlock(keep_running_mutex); This works fine, but at some point it seems to stop working. The app just continues to run as if it never received the -2 signal. We have to use a kill -9 to kill it, which we want to avoid because this prevents our shutdown code from executing. The pthread_* calls you are making aren't listed as being safe to run within the context of a signal handler, and could cause a thread waiting on that condition to be unblocked and start running. Please see earlier comments about mixing threads and signal handlers. -- -Chuck ___ 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
netstat doesn't work
Hi all, I've used FreeBSD 8.0-CURRENT for a month. My kernel is: ( FreeBSD localhost 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Mon Apr 13 23:56:04 CST 2009 r...@localhost:/usr/obj/usr/src/sys/FB8 i386 ) Most things work fine, but the netstat command shows nothing for me. Could someone help me ? Thanks, Dsewnr Lu -- // dsewnr ___ 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: netstat doesn't work
On Tue, 28 Apr 2009 01:24:58 +0800, Dsewnr Lu wrote: DL I've used FreeBSD 8.0-CURRENT for a month. DL My kernel is: ( FreeBSD localhost 8.0-CURRENT FreeBSD 8.0-CURRENT #6: DL Mon Apr 13 23:56:04 CST 2009 DL r...@localhost:/usr/obj/usr/src/sys/FB8 i386 ) DL Most things work fine, but the netstat command shows nothing for me. DL Could someone help me ? Probably you rebuild only kernel or only world. Try to rebuild both: kernel and world from same source. -- Anton Yuzhaninov ___ 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
does isoqlog work in amd64?
just wanted to ask if anyone has the mail/isoqlog program working on an amd64 box. We have it working on i386 FreeBSD 7.x but it sig11's on amd64. looking to have it filter exim logs fwiw. I have sent emails to enderunix and not heard back.. and if it does not work, has anyone actually made awstats work with exim? ___ 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: does ndisgen work with(mini) pci-E cards?
On 4/13/09, Steve Franks bahamasfra...@gmail.com wrote: My new laptop is the fist I've seen with mini-pci-express. Major PITA. I get ndis0 after ndisgen/kldload/etc, but I can see any AP's, and I'm wondering if it's due to the new bus? I suspect I'm barking up the wrong tree since the driver does get loaded, it's probably finding the card...other thoughts I'm having is alot of QA I've googled makes reference to the speficic rev of ndis (4.0, 5.0, 5.1)...maybe that's an issue... You really did not provide any useful information. When you load module what is displayed on console? What is displayed if you change debug.ndis sysctl to 1? What is your pciconf -lv output for ndis0? nd...@pci0:16:0:0: class=0x028000 card=0x1364103c chip=0x431114e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Dell Wireless 1390 WLAN Mini-PCI Card' class = network -- Paul ___ 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
does ndisgen work with(mini) pci-E cards?
My new laptop is the fist I've seen with mini-pci-express. Major PITA. I get ndis0 after ndisgen/kldload/etc, but I can see any AP's, and I'm wondering if it's due to the new bus? I suspect I'm barking up the wrong tree since the driver does get loaded, it's probably finding the card...other thoughts I'm having is alot of QA I've googled makes reference to the speficic rev of ndis (4.0, 5.0, 5.1)...maybe that's an issue... Best, Steve ___ 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: does ndisgen work with(mini) pci-E cards?
On Mon, Apr 13, 2009 at 2:54 PM, Steve Franks bahamasfra...@gmail.com wrote: My new laptop is the fist I've seen with mini-pci-express. Major PITA. I get ndis0 after ndisgen/kldload/etc, but I can see any AP's, and I'm wondering if it's due to the new bus? I suspect I'm barking up the wrong tree since the driver does get loaded, it's probably finding the card...other thoughts I'm having is alot of QA I've googled makes reference to the speficic rev of ndis (4.0, 5.0, 5.1)...maybe that's an issue... Best, Steve ___ 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 This isn't going to be much help, but it may add to your relief/dismay . . . I hope it's the former. I had enough problems trying to get my Broadcom card (mini-pci - BCM94306MP) to work that i gave up and just plug it in. I would get it installed and it would panic. You seem to have avoided that . . . good. What .sys and .inf files are you using? From what I understand, you need/should try a bunch 'til one works. I wish you the best of luck! -Neal -- www.nealhogan.net www.lambdaserver.com ___ 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
Can't work out which disk we are booting from
Hi, I have installed freebsd 7.1 on a 8GB usb flash drive. Now, it seems that the freebsd loader is unable to identify the usb disk where is booting from(da0s1a). The loader runs fine from the stick but gets confused on the drive it runs from, and the kernel it's not loaded. Here is what the loader prints out: [...] Bios drive A: is disk0 [...] Can't work out which disk we are booting from. Guessed BIOS device 0x80 not found by probes, defaulting to disk0: can't load 'kernel' I installed grub too and grub is loading the freebsd loader just fine, but the freebsd loader still get confused. Unfortunately I wasn't able to load the kernel (/boot/kernel/kernel) directly from grub. Best regards, Dragos ___ 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
Mentenance work for mirrors.evolva.ro 04.03.2008 16 - 19 PM GMT+2
Hello, Today mirrors.evolva.ro will be down 2-3 hours for mentenance work. The actual server will be replaced with a new one, more powerfull. We thank you for understanding. Have a great day. -- Daniel TOMUTA Junior System Administrator Evolva Telecom t: +4-021-9394 t: +4-021-200.93.94 t: +4-073-112.38.85 t: +4-074-616.06.05 f: +4-021-200.94.01 e: daniel.tom...@evolva.ro GPG: http://www.evolva.ro/g/dt.gpg ___ 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
KDE4: How to make Home/End keys to work properly in the kde4-console?
I chose Linux in Settings-Edit Current Profile-Input. But Home/End keys bring the cursor to the beginning/end of line either only in 'vim', or only for commands typed into console. But not for both. If Home=\E[1~ and End=\E[4~ keys work in vim, but for the console commands instead of moving cursor they type '~'. If Home=\E[H and End=\E[F keys work for the console commands but not in vim. I believe the first combination is correct and should work for both vim and console. But why it doesn't work in console? Yuri ___ 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
wildcards don't work in sh shell for FAT32 filesystem
Why do pathnames containing a wildcard work in the tcsh shell regardless of the target filesystem, but do not work in the sh shell if the target filesystem is FAT32? The following sequence begins in the tcsh shell by mounting a FAT32 partition from a USB thumb drive. /tmp is in a UFS2 partition. There are no files with fish in their names in either location. This is happening in FreeBSD 7.0-RELEASE. Why do the last four commands not have the same result? tcsh# mount_msdosfs /dev/da0s1 /mnt tcsh# rm -f /tmp/fish* rm: No match. tcsh# rm -f /tmp/*fish rm: No match. tcsh# rm -f /mnt/fish* rm: No match. tcsh# rm -f /mnt/*fish rm: No match. tcsh# sh sh# rm -f /tmp/fish* sh# rm -f /tmp/*fish sh# rm -f /mnt/fish* rm: /mnt/fish*: Invalid argument sh# rm -f /mnt/*fish rm: /mnt/*fish: Invalid argument FWIW, the context of this discovery was trying to use the grub-install script from the GRUB port to install its boot loader on a FAT32 thumb drive. The script aborts when it attempts something like rm -f /mnt/boot/grub/*stage1_5 Carl / K0802647 ___ 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
fixed: firefox3 plugins (flash) don't work [was: Re: swfdec-plugin]
On Wed, Jan 21, 2009 at 1:43 PM, Chad Perrin per...@apotheon.com wrote: On Wed, Jan 21, 2009 at 01:08:35PM -0700, Steve Franks wrote: Anyone get swfdec-plugin to work? Doesn't show up in firefox3's list of plugins (neither does mplayer-plugin or gnash). Does port installation order matter? Do I have to delete .firefox or some other slight-of-hand? Oh, one other thing: Do you have a symlink to: /usr/local/lib/browser_plugins/libswfdecmozilla.so . . . in your $HOME/.mozilla/plugins/ directory? -- Chad Perrin [ content licensed OWL: http://owl.apotheon.org ] Quoth Steve McConnell: Good code is its own best documentation. As you're about to add a comment, ask yourself, 'How can I improve the code so that this comment isn't needed?' Ok, so here's the correct way to fix this, I'm pretty sure: 1) You install firefox as root. When you log in as user, there is no ~/.mozilla/plugins; instead of making that folder and symlinking to swfdec in it, you should symlink: ln -s /usr/local/lib/browser_plugins ~/.mozilla/plugins 2) You are halfway there. I submitted a change-request to the swfdec-plugin port to do this, but until then, sudo ln -s /usr/local/lib/browser_plugins/swfdec-plugin/libswfdecmozilla.so /usr/local/lib/browser_plugins/swfdec No idea how firefox would automatically make the plugin link in your home folder, so there's no fix for that. The swfdec source has just been updated (12/20/2008) and purportedly works with the likes of youtube, so it seems like a good flash solution for FreeBSD at the moment. It worked on the flash site I was trying to visit, and the adobe flash test page. Hope this helps some newbie(s) in the future... Best, Steve ___ 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 7.1, skype not work
Hi people. Im'm use skype-2.0.0.72,1 on my FreeBSD FreeBSD user 7.0 FreeBSD 7.0 r...@user:/usr/src/sys/i386/compile/user i386 with linux linux_base-fc6 /compat/linux/bin/uname -a Linux user 2.6.16 FreeBSD 7.0 i686 i686 i386 GNU/Linux sysctl compat.linux.osrelease=2.6.16 just because skype2 not work with linux_base-fc4 because it have 2.4.x kernel and skype need 2.6.x. I'm update FreeBSD to 7.1-RELEASE-p1 freebsd-update fetch, install FreeBSD user 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 r...@user:/usr/src/sys/i386/compile/user i386 After update I run skype and nothing happen. user# skype user# Thanks! ___ 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: FreeBSD 7.1, skype not work
On Tuesday 20 January 2009 01:21:43 Горбатовский Дмитрий wrote: Hi people. Im'm use skype-2.0.0.72,1 on my FreeBSD FreeBSD user 7.0 FreeBSD 7.0 r...@user:/usr/src/sys/i386/compile/user i386 with linux linux_base-fc6 /compat/linux/bin/uname -a Linux user 2.6.16 FreeBSD 7.0 i686 i686 i386 GNU/Linux sysctl compat.linux.osrelease=2.6.16 just because skype2 not work with linux_base-fc4 because it have 2.4.x kernel and skype need 2.6.x. I'm update FreeBSD to 7.1-RELEASE-p1 freebsd-update fetch, install FreeBSD user 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 r...@user:/usr/src/sys/i386/compile/user i386 After update I run skype and nothing happen. user# skype user# Thanks! Try rebuilding your linux_base by following the instructions in UPDATING 20080318 and make sure you have linprocfs mounted. Beech -- --- Beech Rintoul - FreeBSD Developer - be...@freebsd.org /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://people.freebsd.org/~beech X - NO Word docs in e-mail | Skype: akbeech / \ - http://www.FreeBSD.org/releases/7.1R/announce.html --- ___ 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 7.1, skype not work
Hi people. Im'm use skype-2.0.0.72,1 on my FreeBSD FreeBSD user 7.0 FreeBSD 7.0 r...@user:/usr/src/sys/i386/compile/user i386 with linux linux_base-fc6 /compat/linux/bin/uname -a Linux user 2.6.16 FreeBSD 7.0 i686 i686 i386 GNU/Linux sysctl compat.linux.osrelease=2.6.16 just because skype2 not work with linux_base-fc4 because it have 2.4.x kernel and skype need 2.6.x. I'm update FreeBSD to 7.1-RELEASE-p1 freebsd-update fetch, install FreeBSD user 7.1-RELEASE-p1 FreeBSD 7.1-RELEASE-p1 r...@user:/usr/src/sys/i386/compile/user i386 After update I run skype and nothing happen. user# skype user# Thanks! ___ 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
can't work with a file starting with dash space '- ' ?
By mistake I saved an email attachmed as it was called, probably from MS world: - Reviewer Comments - FFEMS - Closure paper.pdf Now I cannot delete, or rename it. % cp -\ Reviewer\ Comments\ -\ FFEMS\ -\ Closure\ paper.pdf z cp: illegal option -- usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-lpv] source_file target_file cp [-R [-H | -L | -P]] [-f | -i | -n] [-lpv] source_file ... target_directory % rm -\ Reviewer\ Comments\ -\ FFEMS\ -\ Closure\ paper.pdf rm: illegal option -- usage: rm [-f | -i] [-dIPRrvW] file ... unlink file % I can view it with xpdf, but that's about all. I tried wildcards and quotes, sh, csh, bash, tcsh and superuser but no luck. How can I delete or rename this file? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ 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: can't work with a file starting with dash space '- ' ?
On Fri, Jan 16, 2009 at 10:33:13AM +, Anton Shterenlikht wrote: By mistake I saved an email attachmed as it was called, probably from MS world: - Reviewer Comments - FFEMS - Closure paper.pdf Now I cannot delete, or rename it. % cp -\ Reviewer\ Comments\ -\ FFEMS\ -\ Closure\ paper.pdf z cp: illegal option -- usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-lpv] source_file target_file cp [-R [-H | -L | -P]] [-f | -i | -n] [-lpv] source_file ... target_directory % rm -\ Reviewer\ Comments\ -\ FFEMS\ -\ Closure\ paper.pdf rm: illegal option -- usage: rm [-f | -i] [-dIPRrvW] file ... unlink file % I can view it with xpdf, but that's about all. I tried wildcards and quotes, sh, csh, bash, tcsh and superuser but no luck. How can I delete or rename this file? many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 Try cp/rm -- filename-with-dashes -- here denotes the end of command options. HTH, Yuri ___ 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: FIXED: vpnc connects, but does not work
... I do have a Linux OS that I have access to that strangely does use vpnc successfully. That may help quite a bit. You can use something like tcpdump or wireshark on the FreeBSD system to monitor the traffic between the Linux system and the Cisco while connecting and doing something simple like pinging the inside nameserver, then reverse roles and use the Linux system to monitor the traffic between FreeBSD and the Cisco while connecting and attempting to do the same simple thing. You won't be able to see what's inside the IPSEC-encrypted packets, but you can at least see how many of what size are sent in each direction. This may provide some clues as to what is going wrong. ___ 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: FIXED: vpnc connects, but does not work
Hi perryh! On Mon, 12 Jan 2009, per...@pluto.rain.com wrote: ... I do have a Linux OS that I have access to that strangely does use vpnc successfully. That may help quite a bit. You can use something like tcpdump or wireshark on the FreeBSD system to monitor the traffic between the Linux system and the Cisco while connecting and doing something simple like pinging the inside nameserver, then reverse roles and use the Linux system to monitor the traffic between FreeBSD and the Cisco while connecting and attempting to do the same simple thing. You won't be able to see what's inside the IPSEC-encrypted packets, but you can at least see how many of what size are sent in each direction. This may provide some clues as to what is going wrong. Alas, this is a multi-boot system where the Linux OS is installed - so no chance of that :-( I've just determined that it might not be a problem with vpnc..,as such. I got an ethernet connection to work just now, so it looks as if its just down to now vpnc is handling my wifi interface, for some reason. As I said originally, this **was** working, and now its stopped for some reason. I'm now fairly certain that its not got anything to do with vpnc natively, as I used the same vpnc conf file to successfully access the office over ethernet. I'll keep at it.., Thanks for your assistance! Regards, S Roberts ___ 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: FIXED: vpnc connects, but does not work
Hi perryh! Glad to hear that you managed to get your problem fixed.., I also have this problem, the difference being that mine **USED to** work, but now it suddenly stoped working. I tried adding the line to my conf file as you did, but for me, the problem remains: Appears to connect and authenticate successfully to my office's VPN concentrator Once (apparently) connected, I can't access any resources on the company network (mail / servers, etc), nor can I ping anything.., Wondering if you can point me to where you found the info on the various options I can try to continue debugging this problem, please. The FW guys at the office aren't exactly forthcoming where non-MS windows is concerned, you see.., Thanks. Regards, S Roberts On Sun, 04 Jan 2009, per...@pluto.rain.com wrote: I have installed vpnc to connect to an employer's Cisco VPN system, and it seems to make the connection, but after connecting I can't ping the gateway nor anything beyond it ... It turned out the only problem was the absence of NAT Traversal Mode cisco-udp in vpnc.conf. (Presumably not all configurations of the Cisco 3000 will need that, else it would be the default, but it seems to be correct for the one involved here.) I never did figure out why that kept the interface from responding to a ping of its own address :( ___ 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: FIXED: vpnc connects, but does not work
I also have this problem, the difference being that mine **USED to** work, but now it suddenly stoped working. I tried adding the line to my conf file as you did, but for me, the problem remains: Appears to connect and authenticate successfully to my office's VPN concentrator Once (apparently) connected, I can't access any resources on the company network (mail / servers, etc), nor can I ping anything.., Including the IP address of your tun0 interface? (If you can ping that, but nothing beyond, you have a different problem than I had.) Wondering if you can point me to where you found the info on the various options I can try to continue debugging this problem, please. That line came from the output of vpnc --long-help. Other things to look at are the vpnc(8) manpage, the /usr/local/share/doc/vpnc/README file, and the TODO file in /usr/ports/security/vpnc/work/vpnc-0.4.0. There's more detail of what I think is going on in this thread: http://lists.freebsd.org/pipermail/freebsd-net/2009-January/020638.html By the time you get it working again, you will probably have learned more about the workings of vpnc than you really cared to know :) The FW guys at the office aren't exactly forthcoming where non-MS windows is concerned, you see.., Not surprising :( Too many security types act as if obscurity helped security, not realizing that it inconveniences only their customers and not their enemies. Any chance they would be willing to say what config change they made on their end about the time it stopped working, without reference to what is running on your end? Another thing to check is whether your ISP changed something. ___ 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: FIXED: vpnc connects, but does not work
Hi perryh! Thanks for the reply.., On Sun, 11 Jan 2009, per...@pluto.rain.com wrote: I also have this problem, the difference being that mine **USED to** work, but now it suddenly stoped working. I tried adding the line to my conf file as you did, but for me, the problem remains: Appears to connect and authenticate successfully to my office's VPN concentrator Once (apparently) connected, I can't access any resources on the company network (mail / servers, etc), nor can I ping anything.., Including the IP address of your tun0 interface? (If you can ping that, but nothing beyond, you have a different problem than I had.) Nope - same as yours.., Wondering if you can point me to where you found the info on the various options I can try to continue debugging this problem, please. That line came from the output of vpnc --long-help. Other things to look at are the vpnc(8) manpage, the /usr/local/share/doc/vpnc/README file, and the TODO file in /usr/ports/security/vpnc/work/vpnc-0.4.0. There's more detail of what I think is going on in this thread: http://lists.freebsd.org/pipermail/freebsd-net/2009-January/020638.html By the time you get it working again, you will probably have learned more about the workings of vpnc than you really cared to know :) The FW guys at the office aren't exactly forthcoming where non-MS windows is concerned, you see.., This is great - I had a peek, so will pour over these and see how I get on with further debugging.., Its not TOO bad on my side, as I do have a Linux OS that I have access to that strangely does use vpnc successfully. Will press on with the pointers you've provided here. Thanks for the help! Regards, S Roberts Not surprising :( Too many security types act as if obscurity helped security, not realizing that it inconveniences only their customers and not their enemies. Any chance they would be willing to say what config change they made on their end about the time it stopped working, without reference to what is running on your end? Another thing to check is whether your ISP changed something. ___ 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: newbie: does irq setting in device.hints work?
Zhang Weiwu zhangwe...@realss.com writes: Lowell Gilbert wrote: Have you checked what happens if you disable your APIC? You mean ACPI? No, I meant the APIC, the interrupt controller. But I don't think you can do that without compiling a special kernel for it, so it may not be worth trying. You mean ACPI? When the PC boots, I got a menu looks alike this one: http://www.freebsd.org/doc/en/books/handbook/install/boot-loader-menu.png except my 2nd choice was with ACPI enabled instead of ACPI disabled. I chose 2, result was the same (irq at 11) Sorry, I seem to be beyond my knowledge of PC hardware here. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: newbie: does irq setting in device.hints work?
On 1/10/09, Lowell Gilbert freebsd-questions-lo...@be-well.ilk.org wrote: Zhang Weiwu zhangwe...@realss.com writes: Lowell Gilbert wrote: Have you checked what happens if you disable your APIC? You mean ACPI? No, I meant the APIC, the interrupt controller. But I don't think you can do that without compiling a special kernel for it, so it may not be worth trying. FYI, hint.apic.0.disabled=YES in loader.conf or type it in loader prompt. -- Paul ___ 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: Login accounts don't work after update to 7.1
Bert-Jan i...@bert-jan.com writes: Hi Folks, I just updated one of my servers from 7.0-RC1 to 7.1-RELEASE. During the first freebsd-update install, before rebooting, I was surprised to find that it was going to change my /etc/passwd (deleting all my accounts, keeping only the built-in accounts) and /etc/pwd.db and /etc/spwd.db. I was quite suspicious so I made copies of them. freebsd-update should merge master.passwd, and re-generate all of those files from there. What did you do with master.passwd? I didn't do anything with it. I didn't know about it (linux experience talking here, only been using freebsd for a year or so). Now that I'm looking at it all the accounts are there, so it was successfully merged indeed. Note that backup copies of master.passwd are kept in /var/backup. None of the other files, because they're generated from there. After rebooting the machine came back online perfectly. I checked /etc/passwd but there were no changes yet. Then, as the docs says, I ran freebsd-update install again and it took quite a while. *Then* my /etc/passwd was changed, so I replaced it with the spare copy I made. Of That spare copy doesn't help at all; /etc/passwd is only there as a convenience to users, and isn't consulted by the system for anything. I noticed, but after logging out as root unfortunately. course I had to test it now so I exitted from root back to my own account, and you guessed it: I can't su anymore: $ su - su: who are you? I started up a second session and found my own account doesn't work anymore either. So all I have now is an open session with my own account. I should probably also have copied the two db files back and of course I should have left my running root session open and started another one. Not a very bright moment.. Does the root account itself have a password? If you installed a generic password file, it may be unprotected, and you could log in (but not su, as that requires you first be logged in as a wheel user, of which you may have none left) as root without a password if you have a local terminal (a serial console, for example), and fix things from there. Yes, root has a password. The account I was still logged in with is a wheel user but trying a second session showed I couldn't login with that account anymore either. I really made a mess of it :) Is there a way I can recover the server from this ? Of course I can put in a cd and change some passwords, but the server is in a datacenter and I don't really have the time to go there and fix it. I'm looking for a remote solution. I guess you don't have any out-of-band access to the machine, then. You may be stuck with having to go to it physically, then. Yes, I have been there the day before yesterday, the same day I screwed it up. I logged in as root and didn't even get a password prompt. It was obviously reset to the default password database. I fixed the logins by copying the backups I made of /etc/pwd.db and /etc/spwd.db back. Everything returned to normal. It reminded me that freebsd-update had told me it wanted to change things in both those files, but since they're binary it didn't show me a diff. My error thus was that I logged out as root before restoring those. Very nasty, having to drive to the datacenter (about 100km from my home) just to copy two files. But now I know for sure this won't happen to me again :) I do find it strange though, that freebsd-update replaced those files, even though it tells you it's going to change them. What is the proper way to handle this ? Can I run a command after the update finishes that regenerates the account databases from the master.passwd ? I checked the history and *I* never touched it during the update, so it was merged like it should. It's probably not much help but there's one jail running on it that's still working fine. I can login and su on that one, but I don't know if I can use it to repair the main system. I sure hope that won't help. That would defeat the point of jails, wouldn't it? ;-) Yes indeed ;) Thanks for the explanations. I still have a lot to learn of freebsd, having been a Slackware Linux user for about 7 years, I've started my first freebsd server about a year ago. So far I like it very much. Keeping the whole system updated with freebsd-update and the whole ports system is just a breeze. Sometimes like this things get screwed up, but the same has happened to me several times with Linux, so no hard feelings :) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: Login accounts don't work after update to 7.1
Bert-Jan i...@bert-jan.com writes: I do find it strange though, that freebsd-update replaced those files, even though it tells you it's going to change them. I don't use freebsd-update, so I'm just trying to figure it out from reading the program. [freebsd-update is mostly just a shell script] What is the proper way to handle this ? Can I run a command after the update finishes that regenerates the account databases from the master.passwd ? I checked the history and *I* never touched it during the update, so it was merged like it should. I'm not sure what the proper way is; there's certainly code in there to update the databases automatically, so you *shouldn't* have to do anything. To do the same thing manually, you can use pwd_mkdb(8). When you edit the password database with vipw(8), this is handled for you. I'd recommend trying to reproduce the problem on a spare machine, so we can understand it better. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: Login accounts don't work after update to 7.1
Lowell Gilbert wrote: Bert-Jan i...@bert-jan.com writes: What is the proper way to handle this ? Can I run a command after the update finishes that regenerates the account databases from the master.passwd ? I checked the history and *I* never touched it during the update, so it was merged like it should. I'm not sure what the proper way is; there's certainly code in there to update the databases automatically, so you *shouldn't* have to do anything. To do the same thing manually, you can use pwd_mkdb(8). When you edit the password database with vipw(8), this is handled for you. If freebsd-update installs a new master.passwd file, it will regenerate the databases from it. All I can guess in this case is that freebsd-update couldn't manage to merge updates into master.passwd automatically, and when it opened up the file in an editor for you to fix, you didn't merge things properly. -- Colin Percival Security Officer, FreeBSD | freebsd.org | The power to serve Founder / author, Tarsnap | tarsnap.com | Online backups for the truly paranoid ___ 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: newbie: does irq setting in device.hints work?
Zhang Weiwu zhangwe...@realss.com writes: Hello. I come across device.hints manual which says I can set irq for each device there. I am using 6.1. Kind of old now. I don't know specifically of any reason that would matter, but for several reasons I wouldn't be at all surprised. The settings I made in devices.hints never worked. e.g. hint.uhci.0.at=pci hint.uhci.0.irq=12 I can set whatever value for irq and it always rebooted as irq 11. However 'disabled=1' works. That's strange, I didn't find manual where it say it work in some condition or for some device only. Consult individual device drivers' manual pages for available keywords and their possible values. Is there a way to assign uhci to use an irq differently? seems it is the cause of an interrupt storm problem I am having. I'm not really sure if uhci is set up to do that. You definitely want uhci on its own interrupt if you can, not because it necessarily generates a lot of them, but because it can spend a lot of time handling each one... Have you checked what happens if you disable your APIC? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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: newbie: does irq setting in device.hints work?
Lowell Gilbert wrote: Zhang Weiwu zhangwe...@realss.com writes: That's strange, I didn't find manual where it say it work in some condition or for some device only. Consult individual device drivers' manual pages for available keywords and their possible values. Thanks. I shouldn't have overlooked this. Is there a way to assign uhci to use an irq differently? seems it is the cause of an interrupt storm problem I am having. I'm not really sure if uhci is set up to do that. You definitely want uhci on its own interrupt if you can, not because it necessarily generates a lot of them, but because it can spend a lot of time handling each one... Have you checked what happens if you disable your APIC? You mean ACPI? When the PC boots, I got a menu looks alike this one: http://www.freebsd.org/doc/en/books/handbook/install/boot-loader-menu.png except my 2nd choice was with ACPI enabled instead of ACPI disabled. I chose 2, result was the same (irq at 11) I also tried to move other devices occupying irq 11 away (cbb0 and ed1) by setting so in device.hints and both didn't work. [zhangwe...@quasimodo ~]$ vmstat -i interrupt total rate irq0: clk 92204980 irq1: atkbd0 188 2 irq6: fdc011 0 irq8: rtc 11802125 irq11: cbb0 ed1+ 38 0 irq14: ata0 1699 18 Total 105942 1127 [zhangwe...@quasimodo ~]$ dmesg | grep 'irq 11' uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x9000-0x901f irq 11 at device 6.2 on pci0 ed1: IBM Corp. Ethernet at port 0x100-0x11f iomem 0x8800-0x88003fff irq 11 function 0 config 1 on pccard0 ___ 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: Do UDP broadcasts work in FreeBSD?
On Tuesday 06 January 2009 17:49:49 Peter Steele wrote: Our efforts so far indicate the answer is no, which baffles us. We want to send a limited broadcast to 255.255.255.255 but the message never arrives. The same code works fine under Linux. Is there a trick for doing this kind of thing under FreeBSD? Did you enable SO_BROADCAST and IP_ONESBCAST on the socket? I remember needing this on FreeBSD but not on Linux. I know UDP broadcasting works fine, but is somewhat more involved: addr.sin_family = AF_INET; addr.sin_addr.s_addr = inet_addr(130.89.191.255); addr.sin_port = htons(UDP_PORT_ET); optval = 1; if(setsockopt(sock, SOL_SOCKET, SO_BROADCAST, optval, sizeof optval) == -1) err(1, setsockopt); optval = 1; if(setsockopt(sock, IPPROTO_IP, IP_ONESBCAST, optval, sizeof optval) == -1) err(1, setsockopt); const char data[] = report; if(sendto(sock, data, sizeof data, 0, (struct sockaddr*)addr, addrlen) == -1) warn(sendto); This code will send a packet with destination address 255.255.255.255, on the interface with broadcast address 130.89.191.255. netintro(4) talks about how to discover these addresses. SO_ONESBCAST is documented in ip(4), SO_BROADCAST in getsockopt(4). -- Pieter de Goeje ___ 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: Do UDP broadcasts work in FreeBSD?
Did you enable SO_BROADCAST and IP_ONESBCAST on the socket? I remember needing this on FreeBSD but not on Linux. Yes we did, but... I know UDP broadcasting works fine, but is somewhat more involved: addr.sin_family = AF_INET; addr.sin_addr.s_addr = inet_addr(130.89.191.255); addr.sin_port = htons(UDP_PORT_ET); You are using a subnet broadcast here. We are dealing with systems that do not have IPs assigned, and as a result we have to send our broadcasts to 255.255.255.255. This works fine on other operating systems but for some reason the implementation is different on FreeBSD. It appears that the only way this kind of broadcast can be sent on FreeBSD is using raw sockets. This is how the FreeBSD DHCP client/server is written, so we're taking that approach as well... ___ 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: Do UDP broadcasts work in FreeBSD?
why 255.255.255.255 not your net broadcast address? Because the systems we are using do not have IPs assigned and you to know your subnet before you can use subnet broadcasting. We're developing our own DHCP-like service to distribute IPs to all of the systems, and we need limited broadcast to 255.255.255.255 to do this. ___ 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: Login accounts don't work after update to 7.1
Bert-Jan i...@bert-jan.com writes: Hi Folks, I just updated one of my servers from 7.0-RC1 to 7.1-RELEASE. During the first freebsd-update install, before rebooting, I was surprised to find that it was going to change my /etc/passwd (deleting all my accounts, keeping only the built-in accounts) and /etc/pwd.db and /etc/spwd.db. I was quite suspicious so I made copies of them. freebsd-update should merge master.passwd, and re-generate all of those files from there. What did you do with master.passwd? Note that backup copies of master.passwd are kept in /var/backup. None of the other files, because they're generated from there. After rebooting the machine came back online perfectly. I checked /etc/passwd but there were no changes yet. Then, as the docs says, I ran freebsd-update install again and it took quite a while. *Then* my /etc/passwd was changed, so I replaced it with the spare copy I made. Of That spare copy doesn't help at all; /etc/passwd is only there as a convenience to users, and isn't consulted by the system for anything. course I had to test it now so I exitted from root back to my own account, and you guessed it: I can't su anymore: $ su - su: who are you? I started up a second session and found my own account doesn't work anymore either. So all I have now is an open session with my own account. I should probably also have copied the two db files back and of course I should have left my running root session open and started another one. Not a very bright moment.. Does the root account itself have a password? If you installed a generic password file, it may be unprotected, and you could log in (but not su, as that requires you first be logged in as a wheel user, of which you may have none left) as root without a password if you have a local terminal (a serial console, for example), and fix things from there. Is there a way I can recover the server from this ? Of course I can put in a cd and change some passwords, but the server is in a datacenter and I don't really have the time to go there and fix it. I'm looking for a remote solution. I guess you don't have any out-of-band access to the machine, then. You may be stuck with having to go to it physically, then. It's probably not much help but there's one jail running on it that's still working fine. I can login and su on that one, but I don't know if I can use it to repair the main system. I sure hope that won't help. That would defeat the point of jails, wouldn't it? ;-) -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ 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
newbie: does irq setting in device.hints work?
Hello. I come across device.hints manual which says I can set irq for each device there. I am using 6.1. The settings I made in devices.hints never worked. e.g. hint.uhci.0.at=pci hint.uhci.0.irq=12 I can set whatever value for irq and it always rebooted as irq 11. However 'disabled=1' works. That's strange, I didn't find manual where it say it work in some condition or for some device only. Is there a way to assign uhci to use an irq differently? seems it is the cause of an interrupt storm problem I am having. ___ 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
Login accounts don't work after update to 7.1
Hi Folks, I just updated one of my servers from 7.0-RC1 to 7.1-RELEASE. During the first freebsd-update install, before rebooting, I was surprised to find that it was going to change my /etc/passwd (deleting all my accounts, keeping only the built-in accounts) and /etc/pwd.db and /etc/spwd.db. I was quite suspicious so I made copies of them. After rebooting the machine came back online perfectly. I checked /etc/passwd but there were no changes yet. Then, as the docs says, I ran freebsd-update install again and it took quite a while. *Then* my /etc/passwd was changed, so I replaced it with the spare copy I made. Of course I had to test it now so I exitted from root back to my own account, and you guessed it: I can't su anymore: $ su - su: who are you? I started up a second session and found my own account doesn't work anymore either. So all I have now is an open session with my own account. I should probably also have copied the two db files back and of course I should have left my running root session open and started another one. Not a very bright moment.. Is there a way I can recover the server from this ? Of course I can put in a cd and change some passwords, but the server is in a datacenter and I don't really have the time to go there and fix it. I'm looking for a remote solution. It's probably not much help but there's one jail running on it that's still working fine. I can login and su on that one, but I don't know if I can use it to repair the main system. Please, help ! Thanks, Bert-Jan ___ 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
Do UDP broadcasts work in FreeBSD?
Our efforts so far indicate the answer is no, which baffles us. We want to send a limited broadcast to 255.255.255.255 but the message never arrives. The same code works fine under Linux. Is there a trick for doing this kind of thing under FreeBSD? ___ 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: Do UDP broadcasts work in FreeBSD?
why 255.255.255.255 not your net broadcast address? On Tue, 6 Jan 2009, Peter Steele wrote: Our efforts so far indicate the answer is no, which baffles us. We want to send a limited broadcast to 255.255.255.255 but the message never arrives. The same code works fine under Linux. Is there a trick for doing this kind of thing under FreeBSD? ___ 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: Do UDP broadcasts work in FreeBSD?
On Jan 6, 2009, at 8:49 AM, Peter Steele wrote: Our efforts so far indicate the answer is no, which baffles us. We want to send a limited broadcast to 255.255.255.255 but the message never arrives. The same code works fine under Linux. Is there a trick for doing this kind of thing under FreeBSD? What you're trying to do with sending to the all-ones broadcast address is known as sending a link-local packet. On some systems, sending a UDP packet to 255.255.255.255 will actually cause a packet with that destination to be generated from all network interfaces which are UP. That seems to be the behavior you are expecting. On FreeBSD, IIRC, the behavior you get is that it will send to the local network broadcast address for each interface [1] using the network broadcast address (ie, if an interface is configured for 10.1.1.1 with /16 netmask, the packet will have destination 10.1.255.255). If an interface is UP but not configured with an IP +netmask, I don't believe a packet will be sent. (In fact, it might depend upon whether the BROADCAST flag is enabled, which gets set when an inet-enabled interface is setup with a netmask...) Arguably, this is a bug in FreeBSD, but you can work around it by using the BPF interface to send the traffic directly rather than using the network stack via socket()+send()/write(). I believe the ISC DHCP server software provides examples of how to do this, as dhclient is commonly used to send DHCP requests to the all-ones broadcast addr, without needing an interface being configured with an IP -- -Chuck [1]: And I could be mis-remembering that part; it might do a routing table lookup and use only the interface which matches the destination IP, which is probably the default route. ___ 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: Do UDP broadcasts work in FreeBSD?
What you're trying to do with sending to the all-ones broadcast address is known as sending a link-local packet. On some systems, sending a UDP packet to 255.255.255.255 will actually cause a packet with that destination to be generated from all network interfaces which are UP. That seems to be the behavior you are expecting. Yes it is. This is the behavior I've seen on every system I've used for 20+ years, except for FreeBSD. On FreeBSD, IIRC, the behavior you get is that it will send to the local network broadcast address for each interface [1] using the network broadcast address (ie, if an interface is configured for 10.1.1.1 with /16 netmask, the packet will have destination 10.1.255.255). If an interface is UP but not configured with an IP +netmask, I don't believe a packet will be sent. (In fact, it might depend upon whether the BROADCAST flag is enabled, which gets set when an inet-enabled interface is setup with a netmask...) In our case our systems have no IP identity of any kind, and we don't want to have to rely on whether or not our customers have a DHCP server available. So we've come up with our own light DHCP. It works fine for Linux and Windows. Not FreeBSD though. Arguably, this is a bug in FreeBSD I don't think there is any doubt about that. And from what I understand it even used to work under FreeBSD a few years ago. but you can work around it by using the BPF interface to send the traffic directly rather than using the network stack via socket()+send()/write(). I believe the ISC DHCP server software provides examples of how to do this, as dhclient is commonly used to send DHCP requests to the all-ones broadcast addr, without needing an interface being configured with an IP I've already looked at the ISC DHCP source code. They use raw sockets to send their broadcasts, which seems to us to be a convoluted way of sending a simple broadcast. I've seen examples of DHCP client/server code written in Java using standard UDP. Unfortunately, our own system is already largely implemented in Java/Python, so we'll need to provide a JNI interface to support raw sockets. Alternatively we may patch the kernel to fix the bug at its source. ___ 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: Do UDP broadcasts work in FreeBSD?
I've already looked at the ISC DHCP source code. They use raw sockets to send their broadcasts, which seems to us to be a convoluted way of sending a simple broadcast. I've seen examples of DHCP client/server code written in Java using standard UDP. Unfortunately, our own system is already largely implemented in Java/Python, so we'll need to provide a JNI interface to support raw sockets. Alternatively we may patch the kernel to fix the bug at its source. Another option we're considering is to use the firewall to detect broadcasts and rewrite the MAC addresses in the outgoing packets. In looking at tcpdump output of broadcasts, the IP address is set to 255.255.255.255 and the MAC address is set to the MAC address of the gateway. On Linux boxes the MAC address is ff:ff:ff:ff:ff:ff, and that's the only significant difference in the packet. We thought we might be able to come up with a firewall rule to detect broadcasts and change the MAC address to the same as what Linux uses. I'm still in the process of researching this, but if someone can tell me this is impossible, I'll move on. ___ 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: why printf() don't work?
trying putting newlines in the strings like this:
receive overflow\n
- Original Message -
From: Edward King zhan...@neusoft.com
To: freebsd-questions@freebsd.org
Sent: Monday, January 5, 2009 2:29:23 AM GMT -05:00 US/Canada Eastern
Subject: why printf() don't work?
I use FreeBSD7.0,and use signal,like follows: signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io); when I run call following code,it can run,but I find a
puzzled question,it should print some information,such as printf(execute
main()) will print execute main(),but in fact,printf fuction print none!!! Why
printf function do not go work? my code is follows: #include sys/ioctl.h
#include unp.h static int sockfd; #define QSIZE 8 #define MAXDG 4096 typedef
struct{ void *dg_data; size_t dg_len; struct sockaddr *dg_sa; socklen_t
dg_salen; }DG; static DG dg[QSIZE]; static long cntread[QSIZE+1]; static int
iget; static int iput; static int nqueue; static socklen_t clilen; static void
sig_io(int); static void sig_hup(int); int main(int argc,char **argv){
printf(execute main()); int sockfd; struct sockaddr_in servaddr,cliaddr;
sockfd=socket(AF_INET,SOCK_DGRAM,0); bzero(servaddr,sizeof(servaddr));
servaddr.sin_family=AF_INET; servaddr.sin_addr.s_addr=htonl(INADDR_ANY);
servaddr.sin_port=htons(SERV_PORT); bind(sockfd,(SA
*)servaddr,sizeof(servaddr)); dg_echo(sockfd,(SA *)cliaddr,sizeof(cliaddr));
} void dg_echo(int sockfd_arg,SA *pcliaddr,socklen_t clilen_arg){
printf(called dg_echo); int i; const int on=1; sigset_t
zeromask,newmask,oldmask; sockfd=sockfd_arg; clilen=clilen_arg; for(i=0;i
=QSIZE) iget=0; sigprocmask(SIG_BLOCK,newmask,oldmask); nqueue--; } } static
void sig_io(int signo){ printf(sig_io called); ssize_t len; int nread; DG
*ptr; for(nread=0;;){ if(nqueue=QSIZE) err_quit(receive overflow);
ptr=dg[iput]; ptr-dg_salen=clilen;
len=recvfrom(sockfd,ptr-dg_data,MAXDG,0,ptr-dg_sa,ptr-dg_salen); if(len0){
if(errno==EWOULDBLOCK) break; else err_sys(recvfrom error); }
ptr-dg_len=len; nread++; nqueue++; if(++iput=QSIZE) iput=0; }
cntread[nread]++; } static void sig_hup(int signo){ printf(sig_hup called);
int i; for(i=0;i=QSIZE;i++) printf(cntread[%d]=%ld\n,i,cntread[i]); }
---
Confidentiality Notice: The information contained in this e-mail and any
accompanying attachment(s) is intended only for the use of the intended
recipient and may be confidential and/or privileged of Neusoft Corporation, its
subsidiaries and/or its affiliates. If any reader of this communication is not
the intended recipient, unauthorized use, forwarding, printing, storing,
disclosure or copying is strictly prohibited, and may be unlawful.If you have
received this communication in error,please immediately notify the sender by
return e-mail, and delete the original message and all copies from your system.
Thank you.
---
___ 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: why printf() don't work?
On Mon, 5 Jan 2009 15:12:12 + (UTC), Tom Marchand m0rch...@comcast.net wrote: trying putting newlines in the strings like this: receive overflow\n You can add fflush(stdout); to force the output, even if no \n is appended. But as it has been mentioned before, don't forget to #include stdio.h :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: why printf() don't work?
On January 5, 2009 02:29:23 am Edward King wrote:
I use FreeBSD7.0,and use signal,like follows:
signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io);
when I run call following code,it can run,but I find a puzzled question,it
should print some information,such as printf(execute main()) will print
execute main(),but in fact,printf fuction print none!!! Why printf function
do not go work?
my code is follows:
#include sys/ioctl.h
#include unp.h
static int sockfd;
#define QSIZE 8
#define MAXDG 4096
typedef struct{
void *dg_data;
size_t dg_len;
struct sockaddr *dg_sa;
socklen_t dg_salen;
}DG;
static DG dg[QSIZE];
static long cntread[QSIZE+1];
static int iget;
static int iput;
static int nqueue;
static socklen_t clilen;
static void sig_io(int);
static void sig_hup(int);
int main(int argc,char **argv){
printf(execute main());
int sockfd;
struct sockaddr_in servaddr,cliaddr;
sockfd=socket(AF_INET,SOCK_DGRAM,0);
bzero(servaddr,sizeof(servaddr));
servaddr.sin_family=AF_INET;
servaddr.sin_addr.s_addr=htonl(INADDR_ANY);
servaddr.sin_port=htons(SERV_PORT);
bind(sockfd,(SA *)servaddr,sizeof(servaddr));
dg_echo(sockfd,(SA *)cliaddr,sizeof(cliaddr));
}
void dg_echo(int sockfd_arg,SA *pcliaddr,socklen_t clilen_arg){
printf(called dg_echo);
int i;
const int on=1;
sigset_t zeromask,newmask,oldmask;
sockfd=sockfd_arg;
clilen=clilen_arg;
for(i=0;iQSIZE;i++){
dg[i].dg_data=malloc(MAXDG);
dg[i].dg_sa=malloc(clilen);
dg[i].dg_salen=clilen;
}
iget=iput=nqueue=0;
signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io);
fcntl(sockfd,F_SETOWN,getpid());
ioctl(sockfd,FIOASYNC,on);
ioctl(sockfd,FIONBIO,on);
sigemptyset(zeromask);
sigemptyset(oldmask);
sigemptyset(newmask);
sigaddset(newmask,SIGIO);
sigprocmask(SIG_BLOCK,newmask,oldmask);
for(;;){
while(nqueue==0)
sigsuspend(zeromask);
sigprocmask(SIG_SETMASK,oldmask,NULL);
sendto(sockfd,dg[iget].dg_data,dg[iget].dg_len,0,dg[iget].dg_sa,dg[iget].dg
_salen); if(++iget=QSIZE)
iget=0;
sigprocmask(SIG_BLOCK,newmask,oldmask);
nqueue--;
}
}
static void sig_io(int signo){
printf(sig_io called);
ssize_t len;
int nread;
DG *ptr;
for(nread=0;;){
if(nqueue=QSIZE)
err_quit(receive overflow);
ptr=dg[iput];
ptr-dg_salen=clilen;
len=recvfrom(sockfd,ptr-dg_data,MAXDG,0,ptr-dg_sa,ptr-dg_salen);
if(len0){
if(errno==EWOULDBLOCK)
break;
else
err_sys(recvfrom error);
}
ptr-dg_len=len;
nread++;
nqueue++;
if(++iput=QSIZE)
iput=0;
}
cntread[nread]++;
}
static void sig_hup(int signo){
printf(sig_hup called);
int i;
for(i=0;i=QSIZE;i++)
printf(cntread[%d]=%ld\n,i,cntread[i]);
}
---
Confidentiality Notice: The information contained
in this e-mail and any accompanying attachment(s) is intended only for the
use of the intended recipient and may be confidential and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader
of this communication is not the intended recipient, unauthorized use,
forwarding, printing, storing, disclosure or copying is strictly
prohibited, and may be unlawful.If you have received this communication in
error,please immediately notify the sender by return e-mail, and delete the
original message and all copies from your system. Thank you.
---
I think you need #include stdio.h
--
Mike Jeays
http://www.jeays.ca
___
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: why printf() don't work?
Le Mon, 05 Jan 2009 15:29:23 +0800, Edward King zhan...@neusoft.com a écrit : I use FreeBSD7.0,and use signal,like follows: signal(SIGHUP,sig_hup); signal(SIGIO,sig_io); when I run call following code,it can run,but I find a puzzled question,it should print some information,such as printf(execute main()) will print execute main(),but in fact,printf fuction print none!!! Why printf function do not go work? Just to be sure : You should not use printf() in a signal handler, it is not considered 'signal safe'. (See man sigaction) 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
FIXED: vpnc connects, but does not work
I have installed vpnc to connect to an employer's Cisco VPN system, and it seems to make the connection, but after connecting I can't ping the gateway nor anything beyond it ... It turned out the only problem was the absence of NAT Traversal Mode cisco-udp in vpnc.conf. (Presumably not all configurations of the Cisco 3000 will need that, else it would be the default, but it seems to be correct for the one involved here.) I never did figure out why that kept the interface from responding to a ping of its own address :( ___ 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
why printf() don't work?
I use FreeBSD7.0,and use signal,like follows:
signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io);
when I run call following code,it can run,but I find a puzzled question,it
should print some information,such as printf(execute main()) will print
execute main(),but in fact,printf fuction print none!!! Why printf function do
not go work?
my code is follows:
#include sys/ioctl.h
#include unp.h
static int sockfd;
#define QSIZE 8
#define MAXDG 4096
typedef struct{
void *dg_data;
size_t dg_len;
struct sockaddr *dg_sa;
socklen_t dg_salen;
}DG;
static DG dg[QSIZE];
static long cntread[QSIZE+1];
static int iget;
static int iput;
static int nqueue;
static socklen_t clilen;
static void sig_io(int);
static void sig_hup(int);
int main(int argc,char **argv){
printf(execute main());
int sockfd;
struct sockaddr_in servaddr,cliaddr;
sockfd=socket(AF_INET,SOCK_DGRAM,0);
bzero(servaddr,sizeof(servaddr));
servaddr.sin_family=AF_INET;
servaddr.sin_addr.s_addr=htonl(INADDR_ANY);
servaddr.sin_port=htons(SERV_PORT);
bind(sockfd,(SA *)servaddr,sizeof(servaddr));
dg_echo(sockfd,(SA *)cliaddr,sizeof(cliaddr));
}
void dg_echo(int sockfd_arg,SA *pcliaddr,socklen_t clilen_arg){
printf(called dg_echo);
int i;
const int on=1;
sigset_t zeromask,newmask,oldmask;
sockfd=sockfd_arg;
clilen=clilen_arg;
for(i=0;iQSIZE;i++){
dg[i].dg_data=malloc(MAXDG);
dg[i].dg_sa=malloc(clilen);
dg[i].dg_salen=clilen;
}
iget=iput=nqueue=0;
signal(SIGHUP,sig_hup);
signal(SIGIO,sig_io);
fcntl(sockfd,F_SETOWN,getpid());
ioctl(sockfd,FIOASYNC,on);
ioctl(sockfd,FIONBIO,on);
sigemptyset(zeromask);
sigemptyset(oldmask);
sigemptyset(newmask);
sigaddset(newmask,SIGIO);
sigprocmask(SIG_BLOCK,newmask,oldmask);
for(;;){
while(nqueue==0)
sigsuspend(zeromask);
sigprocmask(SIG_SETMASK,oldmask,NULL);
sendto(sockfd,dg[iget].dg_data,dg[iget].dg_len,0,dg[iget].dg_sa,dg[iget].dg_salen);
if(++iget=QSIZE)
iget=0;
sigprocmask(SIG_BLOCK,newmask,oldmask);
nqueue--;
}
}
static void sig_io(int signo){
printf(sig_io called);
ssize_t len;
int nread;
DG *ptr;
for(nread=0;;){
if(nqueue=QSIZE)
err_quit(receive overflow);
ptr=dg[iput];
ptr-dg_salen=clilen;
len=recvfrom(sockfd,ptr-dg_data,MAXDG,0,ptr-dg_sa,ptr-dg_salen);
if(len0){
if(errno==EWOULDBLOCK)
break;
else
err_sys(recvfrom error);
}
ptr-dg_len=len;
nread++;
nqueue++;
if(++iput=QSIZE)
iput=0;
}
cntread[nread]++;
}
static void sig_hup(int signo){
printf(sig_hup called);
int i;
for(i=0;i=QSIZE;i++)
printf(cntread[%d]=%ld\n,i,cntread[i]);
}
---
Confidentiality Notice: The information contained in this e-mail and any
accompanying attachment(s)
is intended only for the use of the intended recipient and may be confidential
and/or privileged of
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of
this communication is
not the intended recipient, unauthorized use, forwarding, printing, storing,
disclosure or copying
is strictly prohibited, and may be unlawful.If you have received this
communication in error,please
immediately notify the sender by return e-mail, and delete the original message
and all copies from
your system. Thank you.
---
___
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
vpnc connects, but does not work
I have installed vpnc to connect to an employer's Cisco VPN system, and it seems to make the connection, but after connecting I can't ping the tun0 interface nor anything beyond it. The symptom seems to resemble what is described in the Routing section of http://www.cs.rpi.edu/~flemej/fbsd-cisco-vpn.pdf, but since that is using a completely different setup on the FreeBSD side I have no idea whether the remedy described there is applicable (nor, if it is, how to determine the addresses to use in this case). Does this look at all familiar, or does anyone have any ideas for how to go about debugging it? I didn't find anything that seemed applicable in recent ports@ or questions@ archives, and an earlier inquiry on ports@ did not produce a solution. (I have XX'd out potentially-sensitive material in the following.) # /usr/local/sbin/vpnc Enter password for x...@xxx.xxx.com: Connect Banner: | *** XXX, Inc. Authorized Use Only *** add host YYY.YYY.127.228: gateway 192.168.200.254 add net ZZZ.ZZZ.0.0: gateway ZZZ.ZZZ.233.42 snipped 56 other add net lines, all with the same gateway address, none to any ZZZ.ZZZ address until: add net ZZZ.ZZZ.57.128: gateway ZZZ.ZZZ.233.42 add net ZZZ.ZZZ.57.133: gateway ZZZ.ZZZ.233.42 VPNC started in background (pid: 24776)... The addresses in those last two add net lines seem to be the nameservers: $ cat /etc/resolv.conf #...@vpnc_generated@ -- this file is generated by vpnc # and will be overwritten by vpnc # as long as the above mark is intact nameserver ZZZ.ZZZ.57.128 nameserver ZZZ.ZZZ.57.133 search XXX.com which leads me to wonder whether they really ought to be add host -- for that matter it's not clear they're needed at all since they should be covered by the add net ZZZ.ZZZ.0.0 -- but I guess that may not make much difference when I can't even ping my own gateway (tun0) address :( $ ping ZZZ.ZZZ.233.42 PING ZZZ.ZZZ.233.42 (ZZZ.ZZZ.233.42): 56 data bytes ^C --- ZZZ.ZZZ.233.42 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss $ ping ZZZ.ZZZ.57.128 PING ZZZ.ZZZ.57.128 (ZZZ.ZZZ.57.128): 56 data bytes ^C --- ZZZ.ZZZ.57.128 ping statistics --- 10 packets transmitted, 0 packets received, 100% packet loss $ ping ZZZ.ZZZ.57.133 PING ZZZ.ZZZ.57.133 (ZZZ.ZZZ.57.133): 56 data bytes ^C --- ZZZ.ZZZ.57.133 ping statistics --- 27 packets transmitted, 0 packets received, 100% packet loss $ ifconfig -a xl0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=9RXCSUM,VLAN_MTU inet6 fe80::2b0:d0ff:fe28:ad4f%xl0 prefixlen 64 scopeid 0x1 inet 192.168.200.61 netmask 0xff00 broadcast 192.168.200.255 ether 00:b0:d0:28:ad:4f media: Ethernet autoselect (10baseT/UTP) status: active plip0: flags=108810POINTOPOINT,SIMPLEX,MULTICAST,NEEDSGIANT mtu 1500 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 inet 127.0.0.1 netmask 0xff00 tun0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1412 inet6 fe80::2b0:d0ff:fe28:ad4f%tun0 prefixlen 64 scopeid 0x4 inet ZZZ.ZZZ.233.42 -- ZZZ.ZZZ.233.42 netmask 0x Opened by PID 24635 Meanwhile I _can_ ping YYY.YYY.127.228, which I guess is the concentrator's public IP address: $ ping YYY.YYY.127.228 PING YYY.YYY.127.228 (YYY.YYY.127.228): 56 data bytes 64 bytes from YYY.YYY.127.228: icmp_seq=0 ttl=116 time=53.226 ms 64 bytes from YYY.YYY.127.228: icmp_seq=1 ttl=116 time=52.982 ms 64 bytes from YYY.YYY.127.228: icmp_seq=2 ttl=116 time=53.130 ms ^C --- YYY.YYY.127.228 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 52.982/53.113/53.226/0.100 ms Traceroute to YYY.YYY.127.228 produces the same 14-hop result whether connected or disconnected (modulo the need to use traceroute -n while connected: since vpnc has replaced /etc/resolv.conf with one specifying only the corporate nameservers, and I can't reach them because the link doesn't work, there is no name service while connected). Just like ping, traceroute to the tun0 IP address, while connected, produced nothing: $ traceroute -n ZZZ.ZZZ.233.42 traceroute to ZZZ.ZZZ.233.42 (ZZZ.ZZZ.233.42), 64 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * ^C What seems truly bizarre is that, as noted above, I couldn't ping the tun0 interface while connected even though ifconfig reported it as up. Shouldn't a local interface, reported as up, *always* respond to a ping of its own IP address? $ netstat -r -n Routing tables Internet: DestinationGatewayFlagsRefs Use Netif Expire default192.168.200.254UGS 0 2209723xl0 snip lines corresponding to snipped add net lines above 127.0.0.1 127.0.0.1
Re: trouble getting x11 xdm to work
Fbsd1 [EMAIL PROTECTED] writes: My /etc/ttys looks like this ttyv6 /usr/libexec/getty Pc cons25 on secure ttyv7 /usr/libexec/getty Pc cons25 on secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure The init: getty repeating too quickly on port /dev/ttyv8 msg has stopped. Right. Because you're no longer trying to run a getty on that port. When I start xdm from root command line nothing happens. NO error log msgs, nothing. Does it return to the command prompt? Respond with xdm: not found? Just hang there? What *does* it do? F1 thru F12 just issue the freebsd console logon prompt. Really? The standard /etc/ttys file doesn't include entries for ttyv9-ttyv12. That means F9-F12 shouldn't let you change to them. Are you sure that you can really change to them, or is it possible that you're still looking at ttyv7 without knowing it? My understanding is when /etc/ttys contains this statement ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure followed by a kill -HUP 1 command to reread tyys file the following should happen. F1 thru F8 virtual consoles work as normal (ie: freebsd console logon prompt). F9 thru F12 virtual consoles will show the xdm logon screen. No. F1 through F7 virtual consoles will be regular consoles, and F8 will be the xdm login screen. To make xdm the system default logon method have to add xdm_enable=YES to /etc/rc.conf and reboot. Then only the xdm logon screen will be seen on all virtual consoles F1 thru F12. A ctrl+alt+backspace key sequence is the only way to force a return to the freebsd console logon prompt for the Fx virtual console being used. No. Not unless you've written your own script to handle the xdm_enable variable, which doesn't seem to exist anywhere else in the system. Unless you've written the script for it as well, I wouldn't expect it to work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Fbsd1 [EMAIL PROTECTED] writes: Mel wrote: On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. Since you're still getting that error message, you obviously didn't succeed at turning off the getty. If you're not getting that message any more, what symptoms *do* you see? -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tue, 11 Nov 2008 19:48:51 +0800, Fbsd1 [EMAIL PROTECTED] wrote: Startx works ok so not xorg problem. Next question is are the xdm configuration files suppose to work as delivered by the port install AS IS? As a default config demo? Ha - xdm configuration files memory flash ahead! :-) Go check them. They are located in /usr/local/lib/X11/xdm. I have two modified files: lrwxr-xr-x 1 root wheel 23 Mar 18 2008 Xresources@ - /etc/X11/xdm/Xresources lrwxr-xr-x 1 root wheel 23 Mar 18 2008 xdm-config@ - /etc/X11/xdm/xdm-config (It's in /etc for custom lazyness, but you can make changes to the files in the original xdm directory if you want.) But I think you didn't change these files, so everything should still be the standard settings... so I need to say, this would not be the source of the problem... If I just knew how I solved the problem you're describing... I really had this once, and I think the solution was very simple, allthough it wasn't obvious, and maybe had nothing to do with X... After all, the obervation indicate that X isn't started correctly for xdm, but what surprises me is that X is started correctly from a regular user's account... Mysterious... VEB Mysteron Merkwürdigkeitenwerk Karl-Marx-Stadt... :-) -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Next question is are the xdm configuration files suppose to work as delivered by the port install AS IS? As a default config demo? Yes. When I said 'range', I did mean range. Not 2 possibilities. Missing libraries, tainted environment, typos, tied up resources, tight security settings, existing pid file, xdm not being xdm but an aliased command or shell script sooner up in the path - that's just from the top of my head. I installed xorg as a package. Then installed xfce package. Made no config changes to xorg or the xdm config files. At this point i suspect the port of xorg as not being configured correctly. That the default xdm config files have statement error causing xdm not to function. So the big question is has anybody installed the release 7.1 package version of xorg and was able to get xdm to function without any config file changes? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Mel wrote: On Tuesday 11 November 2008 00:56:29 Fbsd1 wrote: Polytropon wrote: On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote: Also created the .xsessions file in the users home directory. The file is ~/.xsession, without an s at the end. I assume that csh is your login shell. Put these in your ~/.xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc This sources your individual user setting from .cshrc and the executes .xinitrc (trivial, isn't it?) to control how the startuo of your xsession will go. Make sure both files (.xinitrc and .xsession) are +x attribute. Keep getting this console error message hundreds of times init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second Hey, I saw this one... but I'm not sure how I solved it. Is your /etc/hosts and hostname set correctly? I think it was something like this, something I would never had put in any combination with X... By the way, in order to try if xdm is working correctly it can be started directly by the command xdm anytime. I had ~/.xsession spelled correctly in the directory. Just typo error in email. Changed the contents of ~/.xsession as you posted. Still no joy. /etc/hosts file is correct. Running release 7.0. When i enter xdm on command line of root nothing happens. ps ax command shows no xdm running. Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second That's why. xdm can't get the display. Set on to off in /etc/ttys for ttyv8, kill -HUP 1 and if the message does not stop, reboot the machine. Then start by running xdm from the command line (as root) and inspect /var/log/Xorg.0.log if no screen comes up. I all ready did that (run xdm from the command line) getting no /var/log/xdm.log. Inspecting Xorg.0.log shows nothing related to xdm. When issuing the xdm command from root and then doing (ps ax command) I do not see xdm listed. What am i to see happen from running xdm from the root command line? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tuesday 11 November 2008 12:48:51 Fbsd1 wrote: Mel wrote: On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote: Mel wrote: On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. What does xdm -debug 1 turn up? You said nothing related to xdm in /var/log/Xorg.0.log, but it would still be helpful to see the last lines of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, check if the last modification time of the file corresponds with the last time you ran the command. This will determine if xdm actually gets to the stage of starting the X server or gives up sooner. You may also want to set the -error option (see man xdm) and check if anything useful is written there. With current information, the possible causes range from errors in a configuration file xdm reads on start up to X display problems. Startx works ok so not xorg problem. And you know this why? This may come as a surprise, but startx does different things then xdm. Even having a DISPLAY environment variable set to a non-existing resource, would stop X from starting. Next question is are the xdm configuration files suppose to work as delivered by the port install AS IS? As a default config demo? Yes. When I said 'range', I did mean range. Not 2 possibilities. Missing libraries, tainted environment, typos, tied up resources, tight security settings, existing pid file, xdm not being xdm but an aliased command or shell script sooner up in the path - that's just from the top of my head. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Mel wrote: On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote: Mel wrote: On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. What does xdm -debug 1 turn up? You said nothing related to xdm in /var/log/Xorg.0.log, but it would still be helpful to see the last lines of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, check if the last modification time of the file corresponds with the last time you ran the command. This will determine if xdm actually gets to the stage of starting the X server or gives up sooner. You may also want to set the -error option (see man xdm) and check if anything useful is written there. With current information, the possible causes range from errors in a configuration file xdm reads on start up to X display problems. Startx works ok so not xorg problem. Next question is are the xdm configuration files suppose to work as delivered by the port install AS IS? As a default config demo? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tuesday 11 November 2008 12:09:01 Fbsd1 wrote: Mel wrote: On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. What does xdm -debug 1 turn up? You said nothing related to xdm in /var/log/Xorg.0.log, but it would still be helpful to see the last lines of the file, so we know why X quit. And since Xorg.0.log isn't timestamped, check if the last modification time of the file corresponds with the last time you ran the command. This will determine if xdm actually gets to the stage of starting the X server or gives up sooner. You may also want to set the -error option (see man xdm) and check if anything useful is written there. With current information, the possible causes range from errors in a configuration file xdm reads on start up to X display problems. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Mel wrote: On Tuesday 11 November 2008 11:35:41 Fbsd1 wrote: Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tue, Nov 11, 2008 at 11:01:44AM -0500, Lowell Gilbert wrote: Fbsd1 [EMAIL PROTECTED] writes: Hello, sorry, but I didn't follow the whole thread. Mel wrote: You first need to get rid of that. xdm can't open /dev/ttyv8 while getty is hammering at it. I turned that off all ready before running xdm from root command line. in /etc/ttys I think, right? By default (in my /etc/ttys) on ttyv8 there is an xdm-Daemon configured I think: ttyv6 /usr/libexec/getty Pc cons25 on secure ttyv7 /usr/libexec/getty Pc cons25 on secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure (I changed it to on because I want to start xdm at boot). Since you're still getting that error message, you obviously didn't succeed at turning off the getty. If you're not getting that message any more, what symptoms *do* you see? Is there a getty (or something else) configured in your /etc/ttys? Ciao, Karsten -- Karsten Rothemund [EMAIL PROTECTED] /\ PGP-Key: 0x7019CAA5 \ / Fingerprint: E752 C759 B9B2 2057 E42F \ ASCII Ribbon Campaign 50EE 47AC A7CE 7019 CAA5 / \ Against HTML Mail and News pgpTRsGz9L0Ds.pgp Description: PGP signature
Re: trouble getting x11 xdm to work
My /etc/ttys looks like this ttyv6 /usr/libexec/getty Pc cons25 on secure ttyv7 /usr/libexec/getty Pc cons25 on secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm off secure #ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure The init: getty repeating too quickly on port /dev/ttyv8 msg has stopped. When I start xdm from root command line nothing happens. NO error log msgs, nothing. F1 thru F12 just issue the freebsd console logon prompt. My understanding is when /etc/ttys contains this statement ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure followed by a kill -HUP 1 command to reread tyys file the following should happen. F1 thru F8 virtual consoles work as normal (ie: freebsd console logon prompt). F9 thru F12 virtual consoles will show the xdm logon screen. To make xdm the system default logon method have to add xdm_enable=YES to /etc/rc.conf and reboot. Then only the xdm logon screen will be seen on all virtual consoles F1 thru F12. A ctrl+alt+backspace key sequence is the only way to force a return to the freebsd console logon prompt for the Fx virtual console being used. Is this the correct interpretation of how xdm is designed to function?? I can not find in man xdm or xorg website or handbook an explanation of how it's suppose work. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
trouble getting x11 xdm to work
logging in at command line works and startx works. Now want to use x11 xdm to control logins for virtual terminals 9+ Followed handbook instructions 5.6.2 Using XDM doing this ttyv8 /usr/local/bin/xdm -nodaemon xterm on secure Then kill -HUP 1 to reread the file. Also created the .xsessions file in the users home directory. Keep getting this console error message hundreds of times init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote: Also created the .xsessions file in the users home directory. The file is ~/.xsession, without an s at the end. I assume that csh is your login shell. Put these in your ~/.xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc This sources your individual user setting from .cshrc and the executes .xinitrc (trivial, isn't it?) to control how the startuo of your xsession will go. Make sure both files (.xinitrc and .xsession) are +x attribute. Keep getting this console error message hundreds of times init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second Hey, I saw this one... but I'm not sure how I solved it. Is your /etc/hosts and hostname set correctly? I think it was something like this, something I would never had put in any combination with X... By the way, in order to try if xdm is working correctly it can be started directly by the command xdm anytime. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
eclipse-cdt debugging doesn't work on FreeBSD 7.0 amd64?
Hello BSD guys, My system information is like this. - FreeBSD 7.0-RELEASE amd64 - gcc 4.2.1 - gdb 6.1.1 - eclipse-cdt-3.1.2_1 I used ports tree to compile and install eclipse-cdt-3.1.2_1. Running eclipse and compiling my C++ project are fine. But, when I try to debug, an error dialog box pops up and says 'Target selection failed'. The verbose console mode of the debugger option prints below. 46-gdb-set confirm off 46^done (gdb) 47-gdb-set width 0 47^done (gdb) 48-gdb-set height 0 48^done (gdb) 49-interpreter-exec console echo 49^done (gdb) 50-gdb-show prompt 50^done,value=(gdb) (gdb) 51-gdb-set auto-solib-add on 51^done (gdb) 52-gdb-set stop-on-solib-events 0 52^done (gdb) 53-gdb-set stop-on-solib-events 1 53^done (gdb) 54-gdb-set remotebaud 115200 54^done (gdb) 55-target-select remote /dev/ttyS0 /dev/ttyS0: No such file or directory.\n /dev/ttyS0: No such file or directory. 55^error,msg=/dev/ttyS0: No such file or directory. (gdb) 56-gdb-exit 56^exit The default debugger option of the eclipse is below. Debugger: gdbserver Debugger GDB debugger: gdb GDB command file: .gdbinit GDB command set: Standard Protocol: mi Connection Type: Serial Device: /dev/ttyS0 Speed: 115200 As the error message says, there is no file or directory at /dev/ttyS0 in my system. I've also tried another debugger connection option like below. Connection Type: TCP Host name or IP address: localhost Port number: 1 It prints message like this. 68-gdb-set confirm off 68^done (gdb) 69-gdb-set width 0 69^done (gdb) 70-gdb-set height 0 70^done (gdb) 71-interpreter-exec console echo 71^done (gdb) 72-gdb-show prompt 72^done,value=(gdb) (gdb) 73-gdb-set auto-solib-add on 73^done (gdb) 74-gdb-set stop-on-solib-events 0 74^done (gdb) 75-gdb-set stop-on-solib-events 1 75^done (gdb) 76-target-select remote localhost:1 localhost:1: Connection refused.\n localhost:1: Connection refused. 76^error,msg=localhost:1: Connection refused. (gdb) 77-gdb-exit 77^exit I'm using PF for a firewall and opened TCP connection for port 1 and I even disabled PF, but it has same error. There is anybody who've had and solved this kind of problem of eclipse? I'll really appreciate your solution. Going back to the command line gdb is quite miserable. I really wanna use eclipse for C++ debugging. Thanks. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dump/restore don't work, handbook lies
On Tue Sep 2 14:01:06 UTC 2008 Kirk Strauser wrote: On Sunday 31 August 2008 18:03:53 Lloyd M Caldwell wrote: I needed to increase the size of my freebsd root (/). I booted, single user, attached a large usb freebsd formatted file system to receive the backup image. And you're sure that the large usb freebsd formatted file system is intact and that your dump is uncorrupted? I have just been bitten by a very similar problem as Lloyd Caldwell. - restore complains about '/' not being writable (it is but what should happen there??) - restore extracts a few files but leaves most of the dump unrestored with 'expecting YY got ZZ' I have checked the dump several times with restore -rNf /dev/cd0 (yes, it's to a series of DVD-RAMs) plus have extracted a few samples from the first disk apparently from the area which works. Like Lloyd, I am extremely ... delighted ... about the situation but well. Like Lloyd, I have been using FreeBSD for several years with little to complain. Like Lloyd, any help appreciated... Meanwhile I think I will reinstall the box from scratch with 7.0-RELEASE and return to 7-STABLE but I do miss my backup I must say... Oh well. All the best regards, Peter. --- pcc at gmx dot net. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
Polytropon wrote: On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote: Also created the .xsessions file in the users home directory. The file is ~/.xsession, without an s at the end. I assume that csh is your login shell. Put these in your ~/.xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc This sources your individual user setting from .cshrc and the executes .xinitrc (trivial, isn't it?) to control how the startuo of your xsession will go. Make sure both files (.xinitrc and .xsession) are +x attribute. Keep getting this console error message hundreds of times init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second Hey, I saw this one... but I'm not sure how I solved it. Is your /etc/hosts and hostname set correctly? I think it was something like this, something I would never had put in any combination with X... By the way, in order to try if xdm is working correctly it can be started directly by the command xdm anytime. I had ~/.xsession spelled correctly in the directory. Just typo error in email. Changed the contents of ~/.xsession as you posted. Still no joy. /etc/hosts file is correct. Running release 7.0. When i enter xdm on command line of root nothing happens. ps ax command shows no xdm running. Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: trouble getting x11 xdm to work
On Tuesday 11 November 2008 00:56:29 Fbsd1 wrote: Polytropon wrote: On Mon, 10 Nov 2008 22:21:38 +0800, Fbsd1 [EMAIL PROTECTED] wrote: Also created the .xsessions file in the users home directory. The file is ~/.xsession, without an s at the end. I assume that csh is your login shell. Put these in your ~/.xsession: #!/bin/csh source ~/.cshrc exec ~/.xinitrc This sources your individual user setting from .cshrc and the executes .xinitrc (trivial, isn't it?) to control how the startuo of your xsession will go. Make sure both files (.xinitrc and .xsession) are +x attribute. Keep getting this console error message hundreds of times init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second Hey, I saw this one... but I'm not sure how I solved it. Is your /etc/hosts and hostname set correctly? I think it was something like this, something I would never had put in any combination with X... By the way, in order to try if xdm is working correctly it can be started directly by the command xdm anytime. I had ~/.xsession spelled correctly in the directory. Just typo error in email. Changed the contents of ~/.xsession as you posted. Still no joy. /etc/hosts file is correct. Running release 7.0. When i enter xdm on command line of root nothing happens. ps ax command shows no xdm running. Still getting error msg init: getty repeating too quickly on port /dev/ttyv8, sleeping 30 second That's why. xdm can't get the display. Set on to off in /etc/ttys for ttyv8, kill -HUP 1 and if the message does not stop, reboot the machine. Then start by running xdm from the command line (as root) and inspect /var/log/Xorg.0.log if no screen comes up. -- Mel Problem with today's modular software: they start with the modules and never get to the software part. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
El Jue 23 Oct 2008, Jeremy Chadwick escribió: On Thu, Oct 23, 2008 at 09:42:41PM -0700, Martin Alejandro Paredes Sanchez wrote: El Jue 16 Oct 2008, Jeremy Chadwick escribió: If this printer is hooked up on the network (e.g. via Ethernet), I believe you need to set the lp variable to the hostname or IP address of the printer, e.g.: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=192.168.1.100\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: Negative, leave the lp capability blank, explicitly (:lp=:). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-advanc ed.html#PRINTING-ADVANCED-NETWORK-RM Then the printcap(5) man page should reflect this; the existing explanations for both fields are painfully terse. lp str /dev/lpdevice name to open for output, or [EMAIL PROTECTED] to open a TCP socket rm str NULL machine name for remote printer I can file a PR (to doc) on this if recommended. if you are printing to a remote LPD system, you should use: :lp=:\ :rm=hostname-or-ip:\ :rp=printer-name:\ If you use [EMAIL PROTECTED], then you should not use rp and rm, but in the port of the machine should be a program that undestand LPD/LPR protocol. The printcap(5) man page has a section REMOTE PRINTING. maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
- Warren Block [EMAIL PROTECTED] wrote: On Fri, 17 Oct 2008, [EMAIL PROTECTED] wrote: I have tried the reccomendations that you guys have suggested with no luck. Here is my current printcap. admincolor|LANIER LD160c RPCS:\ :lp=\ :mx#0:\ :sd=/var/spool/output/admincolor:\ :rm=admincolor:\ :lf=/var/log/lpd-errs:\ :if=/usr/local/libexec/crfilter:\ :sh:\ :tr=\f: Please trim your responses and don't top-post, as it makes responding to your messages difficult. The printcap still has no :rp=lp: line. HP printers aren't picky about that, but other brands sometimes are. You've also added a filter and kept the multiple printer names. Things like that make more complexity to debug. Wait until you have basic communication working. The exact suggested printcap entry: admincolor:\ :lp=:\ :sh:\ :mx#0:\ :rm=admincolor:\ :rp=lp:\ :sd=/var/spool/output/admincolor:\ :lf=/var/log/lpd-errs: Note: one printer name (who needs more than one, really?). rm= and rp= entries. No filter; I think that printer can handle PostScript and PCL. Put that printcap entry in /etc/printcap, then send a PostScript test to the printer (all one line): printf %%\!PS\n/Courier findfont 20 scalefont setfont 72 72 moveto (Test!) show showpage\f | lpr -P admincolor -Warren Block * Rapid City, South Dakota USA I tried to reply to this email, but it never got posted. After doing some more troubleshooting I found out the generic error message was indicating an authentication error. By default the printer assumes color print, but the printer was setup to require a userid from the driver to allow color printing. When the autherntication feature is disabled the printer now works. My next step is to see what and how I can supply that info in the printcap. Thanks for all the suggestions and guidance. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
El Mar 21 Oct 2008, [EMAIL PROTECTED] escribió: I took your block above and replaced my block in the printcap, then sent the exact command above with the same failure. The queue is drained and the printer's log has a generic message The job was reset. message. My current printcap file. admincolor:\ :lp=:\ :sh:\ :mx#0:\ :rm=admincolor:\ :rp=lp:\ :sd=/var/spool/output/admincolor:\ :lf=/var/log/lpd-errs: it sounds like LPD is working OK (send the job to the printer), the problem is the print job (the language PS/PCL) or in the printer (no configured). how do you configure this printer in windows (LPR port)? can you print to a file in windows, bring that file to FreeBSD and send it with lpr -P admincolor FileInWindows.bin did you check the next URL? http://www.linuxprinting.org/show_printer.cgi?recnum=Lanier-LD160c maps ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Printing to a Lanier LD160c does not work
El Jue 16 Oct 2008, Jeremy Chadwick escribió: On Thu, Oct 16, 2008 at 08:36:42PM +, [EMAIL PROTECTED] wrote: I am trying to setup a Lanier LD160c (admincolor) that has a network interface. I am new to FreeBSD and tried to follow the handbook. I am able to print to a HP 5SI (corp-admin) with no problems. There are no errors in the lpd-errs and the file is drained from the queue, but the printer does not print anything. And this is a working printer to Windows. lpr -P admincolor testfile.txt printcap: corp-admin|hp|laserjet|Hewlett Packard LaserJet 5Si:\ :lp=\ :sd=/var/spool/output/corp-admin:rm=corp-admin:\ :lf=/var/log/lpd-errs:\ :if=/usr/local/libexec/crlfilter:sh:tr=\f:mx#0: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: If this printer is hooked up on the network (e.g. via Ethernet), I believe you need to set the lp variable to the hostname or IP address of the printer, e.g.: admincolor|hp|laserjet|LANIER LD160c RPCS:\ :lp=192.168.1.100\ :sd=/var/spool/output/admincolor:rm=admincolor:\ :lf=/var/log/lpd-errs: Negative, leave the lp capability blank, explicitly (:lp=:). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-advanced.html#PRINTING-ADVANCED-NETWORK-RM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
