Re: ssh under attack - sessions in accepted state hogging CPU
Hi Matt, > > I know there's not much I can do about the brute force attacks, but will > upgrading openssh avoid these stuck connections? 1. switch over to using solely RSA keys 2. switch to a non-standard port 3. what version of openssh are you currently using? Best James___ 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: Failed port upgrade
On Dec 25, 2009, at 8:48 PM 12/25/09, Rem P Roberti wrote: > When running portupgrade the process is choking when it comes to > consolekit. Here is the error message: > > gmake[2]: *** [libgirepository_1_0_la-gfield.lo] Error 1 > gmake[2]: Leaving directory > `/usr/tmp/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7/girepository' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory > `/usr/tmp/usr/ports/devel/gobject-introspection/work/gobject-introspection-0.6.7' > gmake: *** [all] Error 2 > *** Error code 1 > > Stop in /usr/ports/devel/gobject-introspection. > *** Error code 1 > > Stop in /usr/ports/sysutils/polkit. > *** Error code 1 > > Stop in /usr/ports/sysutils/consolekit. > ** Command failed [exit code 1]: /usr/bin/script -qa > /tmp/portupgrade20091225-42364-180m9y8-0 env UPGRADE_TOOL=portupgrade > UPGRADE_PORT=consolekit-0.4.1_1 UPGRADE_PORT_VER=0.4.1_1 make > ** Fix the problem and try again. > > > this obviously involves gobject-introspection and polkit, both of which > refuse to make. I could find nothing in UPDATING about this. > > Rem Hey Rem, did you ever get this solved? James___ 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: mrtg broken dependency
On Dec 30, 2009, at 11:22 AM 12/30/09, Sergio de Almeida Lenzi wrote:
> Hello...
>
> mrtg (net-mgmt/mrtg) misses a dependency on perl module===>
> p5-SNMP_Session
>
> in the Makefile:
>
> RUN_DEPENDS+= ${SITE_PERL}/SNMP_util.pm:
> ${PORTSDIR}/net-mgmt/p5-SNMP_Session
>
> fix the problem
>
> what next??? how to contact the mrtg port manager???
From the Makefile:
MAINTAINER= m...@subnets.ru
>
> Thanks for your attention,
>
> Sergio
> ___
> 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: desktop wireless card
gahn wrote: Hello: Could anyone recommend a desktop wireless card for freebsd 6.2? Just moved in new place and only wireless in the house. Thanks in advance I use whatever was the cheapest linksys wireless G card I could find; plugs in to PCI slot and works wonderfully. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Distcc + cross compiling
On Tue, 2008-03-25 at 07:17 +0100, Wael Nasreddine wrote: > Hello, > > I have a FreeBSD x86 server, running FreeBSD 7.0-RELEASE, I'd like to > create a new jail with distcc and gcc to help my laptop compiling > gentoo x86 stuff, I'm using GCC 4.2.3 on my laptop... > > is it possible to use FreeBSD for compiling gentoo's stuff?? I heard > of cross-compiling but I have never tried it... if so, any guide > please ?? > > Thanks :) > Cross compiling refers to the practice of compiling on one hardware architecture for another hardware architecture, typically going from x86 to ARM I'd imagine. In this case, FreeBSD and gentoo put libraries in different places, call libraries by different names, and use an entirely different system of makefiles for packages. As such, I imagine that either you'd be better off making a virtual machine with gentoo installed in it on your FreeBSD box and compiling from there, or it's possible you could compile static binaries and use those. I'm not an expert on jails by any means, but my understanding is that the only OS you can use within a jail is FreeBSD, as all jailees share a common kernel. Best James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: I'd like some help
On Mon, 2008-03-24 at 18:03 +0100, Christian Zachariasen wrote: > On Windows, I can really recommend the freeware burner program CDBurnerXP: > > http://cdburnerxp.se/ > Christian Zachariasen > On Windows XP, I usuall recommend infrarecorder: http://infrarecorder.sourceforge.net/ It's a nice FOSS CD burning application. James > On Mon, Mar 24, 2008 at 5:05 PM, Jerry McAllister <[EMAIL PROTECTED]> wrote: > > > On Sat, Mar 22, 2008 at 02:58:24PM -0700, Matthew Woodson wrote: > > > > > I've been learning about a bunch of the BSD OSes, and i want to try Free > > > BSD, but i can't figure out how to download it and the instructions > > don't > > > make sense. I am running Windows XP OS- can you tell me how to download > > > Free BSD with it? > > > > Well, you generally want an ftp client. Use it to ftp to: > > ftp.freebsd.org > > > > Use 'anonymous' for login id and your email address for password. > > > > >From there cd to pub/FreeBSD/releases (NOTE that case is > > significant) > > > > At this point, you need to know the type of machine. It is most > > likely i386 or amd64. amd64 is for the AMD64 processor. i386 is for > > all of the regular INTEL type processors that regular PCs use and your > > most likely choice. > > > > So, cd to i386and thenISO-IMAGES > > > > Then you have to select the version. > > I would suggest starting with 7.0 > > > > cd cd to 7.0 > > > > So that ends you up in: > > > > pub/FreeBSD/releases/i386/ISO-IMAGES/7.0 > > > > Then download the necessary ISOs. > > > > > > If you have a reasonable internet connection, you can install over > > the net. That is really the best if you can do it. > > > > In that case, you only need the file 7.0-RELEASE-i386-disc1.ISO > > > > If you hav a slow or unreliable network connection, then you may > > also need disc2 and even disc3. They have the ports' source code > > on them. > > > > Presuming disc1 is good enough, > > > > burn the file to a cd. Note that the file is already an ISO and > > doesn't need to be converted. It needs to be burned as a raw file > > to the CD. Some cd burner utilities make this a bit confusing. > > Each is a little different. > > > > > > You now need to decide how to divide the hard disk and if you will be > > putting only FreeBSD on the harddisk or sharing one with some other > > OS such as something from Microsloth (called dual booting). > > > > In any case, you have to have a slice dedicated to FreeBSD. > > Note that FreeBSD UNIX uses the term slice but Microsloth uses the > > term 'primary partition' to refer to a slice. The UNIX slice and > > the MS primary partition are essentially the same and are compatible. > > > > In BSD, a slice is further divided in to 'partitions'. Microsloth uses > > 'extended partitions'. But those MS extended partitions are completely > > different and incompatible with UNIX partitions. > > > > If you are sharing a disk, you will need to use some utility to > > shrink the existing disk allocation to make room for FreeBSD. > > > > Only 4 slices/primary partitions (names 1..4) are allowed on a disk in > > current systems. Typically a major vendor puts some proprietary > > diagnostic > > and hardware utilities in the first [small] slice and marks it hidden. > > Hidden is only meaningful to Microsloth systems. It remains visible to > > UNIX. > > > > Then they put the MS OS (XP or whatever) on slice 2 and make that slice > > contain all the rest of the disk, leaving slice 3 and slice 4 empty > > and unused.So, to fit FreeBSD on the disk, it becomes necessary to > > shrink that slice 2 to free up some space to allocate to another slice - > > most likely slice-3. > > > > I have used a commercial utility called Partition Magic successfully > > in the past to manipulate the slices and make room. That was with > > a version 7.0 of PM which was put out by a company called Power Quest. > > But, it got sold and the new owner put a version 8.0 which has not > > been as successful as far as I can see. I tried to use it to slice a > > USB disk and it would not talk to it, even though its promotional > > literature made a special point of advertising it would. So, I returned > > it for a refund. > > > > In consequence I get a utility called Gparted, made the boot floppy and > > was quite successful with using it to manipulate the disk. Just do a > > little search with google and find it and download it. It works fine. > > There are some other freeware utilities out there, but most will not > > work with the NTFS type Microsloth filesystem which is common nowdays. > > So, check on that. Gparted seems to handle it OK. > > > > Anyway, lets say you carve out a nice 40 GB of disk for FreeBSD and that > > is in slice 3 - a common circumstance.If you have a whole disk to > > decicate to FreeBSD the rest of this applies. You just don't need to > > go through the gyrations to make room on a shared disk and the disk name > > is slightly different - pr
Re: pam problems
http://lists.freebsd.org/pipermail/freebsd-questions/2007-September/159008.html That cover you? On Thu, 2008-03-13 at 14:36 -0400, Chuck Robey wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > My messages file is getting completely blasted by error lines like this: > > Mar 13 11:16:03 april sshd[80704]: in openpam_dispatch(): pam_nologin.so: > no pam_sm_authenticate() > > Anyone got any idea what's causing this? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.4 (FreeBSD) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFH2XQUz62J6PPcoOkRAhcuAJ40wFjLvU+P2UCp6baz7b78Lt36wgCfX8p4 > y5miBxcZ9Da6l1RGvo15v5s= > =qbD5 > -END PGP SIGNATURE- > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD & Linux distro
> > > > > 8. Most extensive collection of third party software (over 18000 ) only > > second to Debian. > > Looking back at it, I'm surprised I didn't mention that. > Gentoo has over 24 thousand ebuilds, where an ebuild is their equivalent of a port: http://en.wikipedia.org/wiki/Ebuild http://packages.gentoo.org/categories/ is the page that lists the current number of ebuilds. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports question
On Wed, 2008-02-20 at 12:02 -0600, Darryl Hoar wrote: > Greetings, > I am looking to install a CMS system (something like postnuke) and want to > have a blog component. > > Anybody have any recommendations ? If it is in the ports, it would be even > better. > > thanks, > Darryl I've been using git a fair bit; it's fast as all hell. It's what the linux kernel guys use, though I'm considering moving over to bazaar because it archives more metadata. http://en.wikipedia.org/wiki/Bazaar_(software) The BSDs traditionally use CVS, so at the very least you know that's good over long term for a lot of files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: wpa_supplicant not starting with /etc/rc.d/netif
On Sat, 2008-02-02 at 00:32 +0200, Reinis Ivanovs wrote: > Hello, > > I have been following these instructions from the manual: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#NETWORK-WIRELESS-WPA-WPA-PSK > However, in the step that requires me to run "/etc/rc.d/netif start", > instead of it starting wpa_supplicant, I see only "ral0: no > link giving up". I've added > "ifconfig_ral0="WPA DHCP" to /etc/rc.conf, and it works just fine if I > start it manually with "wpa_supplicant -B -c /etc/wpa_supplicant.conf > -i ral0". What should I do to get it working? Could it be that there's > some bug in your scripts? > > Regards, > Reinis > I've not done this, but the documentation says: Note: If the /etc/rc.conf is set up with the line ifconfig_ath0="DHCP" then it is no need to run the dhclient command manually, dhclient will be launched after wpa_supplicant plumbs the keys. As such, I don't understand why you're running the ifconfig command in /etc/rc.conf with the extra WPA flag. Try making it read ifconfig_ral0="DHCP" and see if that helps. Best James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: This has begun to annoy me...
On Fri, 2008-02-01 at 22:37 +0100, Wojciech Puchar wrote: > > I have a laptop doing same thing, but even with the occasional spontaneous > > reboot, it is still more reliable than Windows, and as I haven't had time to > > mess with it, it stays in there. Probably will run dban on the drive, see if > > it makes happy. > > what is dban? Darik's Boot and Nuke: http://dban.sourceforge.net/ > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ftp setup - giotissl - ASAP - SOS
On Thu, 2008-01-17 at 23:11 +0200, Giotis Eugen wrote: > hello, > I just bought a dedicated server (unmanaged server) > Can you help me? > I want to install the ftp. > Can you help me step by step ? > I can connect to my server via SSH and I have installed the cpanel/whm. > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Shrinking a partition
On Tue, 2008-01-15 at 07:45 -0500, Aryeh Friedman wrote: > After installing FreeBSD and Vista (463 GB and 30 GB respectivally) I > found out I don't have enough free space on my 500 GB drive on the > vista partition. How do I determine how much I can shrink the > FreeBSD partition by safely (by just moving the end sector in > fdisk(1))? > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" I'd imagine that you could use the output of df -h to see how much you're using on the /usr partition and then shrink appropriately. Best James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: home dir executable (!/bin/sh, chmod+x) shell scripts won't run without "sh
On Mon, 2008-01-07 at 10:50 -0600, Erik Osterholm wrote: > On Mon, Jan 07, 2008 at 09:13:39AM -0700, Steve Franks wrote: > > > This is a sort of 'don't shoot yourself in the foot' design. You > > > cannot run a script or binary simply by name if you're cwd is the > > > directory that contains that script or binary. IIRC, you can't cd / > > > usr/bin and run anything in /usr/bin without explicitly calling that > > > file with the ./ telling the system THIS ONE. > > > > Ah! You'd think any one of the many tutorials I read would have > > mentioned that little detail ;) > > > > Thanks, all > > Steve > > You should search your tutorials for the PATH environment variable. > > In an over-simplified nutshell, when you type a command in your shell, > it checks a number of different locations for the place to find the > command you're trying to execute. Some of those locations are every > directory specified in your PATH variable. My PATH is: > /bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin > > This means that when I type 'ls', the shell looks for an executable > named 'ls' in each of those directories (actually, it probably stops > right after /bin/ls, since that's the correct one.) > It stops at the first instance of an ls binary it finds. This is actually something that's really useful to know in all kinds of circumstances. Your path is search from left to right, and it stops searching at the first instance of the executable that it finds. This has practical applications even when installing ports. One example that comes to mind is the CUPS port. It installs its own version of the lpr binary in /usr/local/bin. However, there's also an instance of lpr, the BSD version, in /usr/bin. So how do you make sure you're using the CUPS version of the binary? The recommended way is a simple path edit, so that /usr/local/bin appears before /usr/bin in the path. This way, your OS will use the /usr/local/bin/lpr binary, leaving the system one untouched and, if you ever want to revert to the system one you can simply switch the path again. You can also accomplish a similar thing with symlinks, but this is one useful idea for using the path. > If the shell does not find a valid executable in the path, it will say > that there is no such file or directory. In this case, you would try > specifying the full path by typing /bin/ls, or /home/user/scriptname. > '.' and '..' have special meanings--current directory and > next-directory-up, specifically--so if your current working directory > is /home/user, typing ./scriptname will be largely equivalent to > typing /home/user/scriptname. ../scriptname would be largely > equivalent to /home/scriptname. This is why some people suggested > trying ./scriptname in other e-mails in this thread. > > The '.' notation for the current working directory enables you to add > the current directory you happen to be in as part of your path (thus > making it searched when executing a command), however this has serious > security implciations, so if you think that it's something you really > want to do, you'll have to find out from someone else how to do it. > > erik > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Partitions size for 80GB HDD and 2GB RAM
On Thu, 2007-12-20 at 11:26 -0800, Alexander Rudyk (Akvelon) wrote: > Nikola, > > Thank you for your extender answer. I have two more comments. > > Did you consider /var as your email db partition. I really don’t > know how big will be my mail db on freebsd, but after half of year > I have about 4GB outlook mail db. So 1GB for /var might be not enough > in my case. > > Having /home as part of /usr is the good point. But in case of backup > it make sense to have /home as separate partition. What you think about this? > > Thx > Alex > > /home is just a symlink to /usr/home, so that wouldn't help. cd / ls -l lrwxr-xr-x 1 root wheel8 Nov 2 05:37 home -> usr/home You might want to put /usr/home on a separate partition, but that's your call. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: tail does not exit
On Wed, 2007-12-19 at 18:22 -0500, Mikhail T. wrote:
> #!/bin/sh
>
> if tail -f /var/log/messages | awk '{print "Exiting"; exit 0}'
> then
> echo Exited
> else
> echo Failed
> fi
>
> exit 0
I assume it has something to do with tail -f being used, rather than
tail. Is there a reason you want the -f flag?
tail -f holds on for dear life until a ctrl-c happens. IT HAS A DEATH
GRIP!
James
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: login.conf password options
On Thu, 2007-12-13 at 19:51 +0100, Peter Boosten wrote: > Quoting Daniel Bye <[EMAIL PROTECTED]>: > > > On Thu, Dec 13, 2007 at 07:30:21PM +0100, Peter Boosten wrote: > >> Quoting James Harrison <[EMAIL PROTECTED]>: > >> > >> >:passwordtime=150d:\ > >> >:warnpassword=150d: > >> > >> Is it me, or did you forget the backslash here? > > > > No, that's correct. It's the last line of a class definition. The backslash > > is used as a line continuation character, and is not necessary on the last > > line. In fact, it must not be included, else it will cause the system to > > interpret the next line as part of the same class definition, rather than > > the start of the next. > > > > Very good answer, *if* it were the last line of the class definition. > I cut the last two lines from the original description from OP. > > So to OP: add a backslash to the warnpassword= line. > > Peter > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Ah! I see! No, I'd already caught that one about a minute after I sent off my original mail. My current default looks like: default:\ :passwd_format=md5:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ :path=/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local/bin ~/bin:\ :nologin=/var/run/nologin:\ :cputime=unlimited:\ :datasize=unlimited:\ :stacksize=unlimited:\ :memorylocked=unlimited:\ :memoryuse=unlimited:\ :filesize=unlimited:\ :coredumpsize=unlimited:\ :openfiles=unlimited:\ :maxproc=unlimited:\ :sbsize=unlimited:\ :vmemoryuse=unlimited:\ :priority=0:\ :ignoretime@:\ :umask=022:\ :passwordtime=150d:\ :warnpassword=150d:\ :sessiontime=1h30m:\ :warntime=1h29m: Good catch! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: login.conf password options
On Thu, 2007-12-13 at 19:30 +0100, Peter Boosten wrote: > Quoting James Harrison <[EMAIL PROTECTED]>: > > > :passwordtime=150d:\ > > :warnpassword=150d: > > Is it me, or did you forget the backslash here? > > Peter It's you; the last option doesn't receive a backslash. Here's one of the prebuilt examples from login.conf: #xuser:\ # :manpath=/usr/share/man /usr/local/man:\ # :cputime=4h:\ # :datasize=12M:\ # :vmemoryuse=infinity:\ # :stacksize=4M:\ # :filesize=8M:\ # :memoryuse=16M:\ # :openfiles=32:\ # :maxproc=48:\ # :tc=standard: It's commented out, but note that the last one doesn't receive a backslash. Well spotted, though! For ten minutes, I was convinced that the problem had to be backslashes, because I noticed I'd mistyped a couple. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
login.conf password options
Hi folks, I've slowly been setting up some options for the default class in login.conf such that passwords will expire after 150 days. To test whether this functionality was working, I have a warning appear on the first day, so that if I set a password and log in , I ought to be warned that my password will expire in 150 days. It doesn't appear to be working. I am not receiving any kind of warning that my password will expire. To see whether I was correctly in the default class, I changed the message of the day file from /etc/motd to /etc/motw, and the message of the day changed appropriately. I then set up a session limit of an hour and a half with a warning appearing after 1 minute, but that isn't working either. The method I'm using is this: I use vi to edit the /etc/login.conf, then run cap_mkdb /etc/login.conf. I then reboot the machine, to make sure that everything that ought to be paying attention does. I suspected that /etc/master.passwd might need updating, so I used vipw, made a trivial change, saved the change, but nothing. My default class reads: default:\ :passwd_format=md5:\ :copyright=/etc/COPYRIGHT:\ :welcome=/etc/motd:\ :setenv=MAIL=/var/mail/$,BLOCKSIZE=K,FTP_PASSIVE_MODE=YES:\ :path=/sbin /bin /usr/sbin /usr/bin /usr/games /usr/local/sbin /usr/local/bin ~/bin:\ :nologin=/var/run/nologin:\ :cputime=unlimited:\ :datasize=unlimited:\ :stacksize=unlimited:\ :memorylocked=unlimited:\ :memoryuse=unlimited:\ :filesize=unlimited:\ :coredumpsize=unlimited:\ :openfiles=unlimited:\ :maxproc=unlimited:\ :sbsize=unlimited:\ :vmemoryuse=unlimited:\ :priority=0:\ :ignoretime@:\ :umask=022:\ :passwordtime=150d:\ :warnpassword=150d: :sessiontime=1h30m:\ :warntime=1h29m: Any ideas? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: copying just / (not /tmp, /usr, etc) (rsync -x failed)
On Wed, 2007-12-05 at 10:41 -0500, Jerry McAllister wrote:
> On Tue, Dec 04, 2007 at 05:38:20PM -0700, Steve Franks wrote:
>
> > I have / on one slice, and [usr,tmp,var] on others. I want to move
> > just / to a new disk, which seemed to be what rsync -x ("do not cross
> > filesystems") was intended for. It failed, however, as df shows 20k
> > blocks in /, and rsync filled up the target slice with 50k blocks, so
> > obviously it blew right past the 'end' of / - did I miss something? Is
> > there no other way except to umount [tmp,usr,var]?
>
> I would use dump/restore.
>
> Build the filesystem in the new disk partition with fdisk, bsdlabel
> and newfs as needed. Then mount the new partition somewhere -
> example:
> mkdir /newpart
> mount /dev/ad1s1a /newpart
> (presuming new disk is ad1, slice is 1, partition is a)
> Doesn't hurt to do an fsck on it here before writing to it, but it
> probably isn't really needed.
>
> Then, run the dump/restore
>
> cd /newpart
> dump 0af - / | restore -rf -
>
> This will get all of / as you want. The other mountpoints for /tmp, /usr
> and /var will be copied, but not the contents of those filesystems. You
> probably want that.
>
> jerry
>
> >
> > Thanks,
> > Steve
Everyone's recommending dump/restore for copying file systems, and
there's something that I've never really been clear on.
The nice thing about rsync is that it's network aware. Can dump dump a
file system across a network?
James
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kpersonalizer: cannot connect to X server
On Thu, 2007-11-29 at 21:25 +0100, Tino Engel wrote: > williamkow schrieb: > > I am newbie, recently I have installed FreeBSD 6.2-Stable, and manage to > > configure and display the x window manager (X11) using command "startx". > > and then i run command "startkde " and I received error message > > (kpersonalizer: cannot connect to X server) > > However, if i run command "kdm", then it prompt for login screen. I am > > wondering the command "startkde" is not correct way to call KDE. please > > advise me. Thank you. > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > > startkde should be fine also... > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" I thought X had to be fully running to start another desktop on top of it, and that was done by xinit. Hence having to put startkde in .xinitrc. I think from the situation you're describing that you're correct, it ought to be running, but try putting startkde in the .xinitrc file and then just running startx. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ls -l takes a forever to finish.
On Wed, 2007-11-28 at 09:44 -0600, Mark Evans wrote: > No we are not using NIS. > > it is a large directory i am listing. actually it is the /usr/home > directory, and is probably the largest on the system. However "ls -l" runs > for close to six minutesand spends the 10 seconds scrolling the screen with > the results. so i wait ls to start showing the results for about 5 and a > half minutes. Even on a older and much slower system i've never seen it > talk more than 15 seconds to complete. > > > Thanks > Mark > How many directories, roughly? I've seen ls take *many* minutes listing the contents of a directory that contained tens of thousands of files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7/OpenLDAP: Howto change passwords
On Mon, 2007-11-26 at 21:23 +0200, Jonathan McKeown wrote: > On Monday 26 November 2007 17:11, O. Hartmann wrote: > > Hello, > > > > trying to change passwords on a client machine for a LDAP authenticated > > user always fails due to the original passwd() command is not capable of > > changing passwords remotely. > > Their is a suggested patch, but is there an "official" way to do? > > Hi Oliver > > I've asked this question several times, here and on -hackers, with no very > helpful response. I checked for PRs and several have been filed at various > times and are in various different states. > > As far as I can tell, the changes necessary to make passwd(1) work with the > PAM infrastructure were made some years ago, but were diked out by a switch > statement which appears to prevent a change to anything but /etc/passwd or > NIS/YP. This switch relies on a set of constants which are themselves > commented in the source as being ``bogus''. > > The answer to our question may well be something like ``historical reasons'' > or ``Principle of Least Astonishment'', but please, someone... > > Is there a sound reason not to remove this guard statement and allow > passwd(1) > to change passwords in accordance with a PAM policy, as it is coded to do? > > I've already offered to submit a patch if necessary: it hardly even needs a > knowledge of C to fix this one - simply remove a switch statement and replace > it with a simple printf. > > Jonathan > ___ My advice would honestly be to write the patch and submit it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: stability of FreeBSD 7 Beta 3?
On Mon, 2007-11-26 at 15:34 +, Chris wrote: > On 26/11/2007, Kris Kennaway <[EMAIL PROTECTED]> wrote: > > Tore Lund wrote: > > > Ivan Voras wrote: > > >> Dave wrote: > > >>> Hello, > > >>>How stable is FreeBSD 7 Beta 3? Is it near production are their any > > >>> outstanding issues? > > >> Probably no major bugs will be fixed between now and 7.0 so you might as > > >> well start using it now. > > >> > > >> It's "stable enough" like all .0 releases, meaning you should throughly > > >> test it for your own workload before using it in production. > > > > > > Just curious, what is the "official" forum for pre-release discussions? > > > I notice there are some threads on the "current" list, but it seems to > > > me that this is really "questions" stuff, since it is an upcoming release. > > > > freebsd-stable is probably best. > > > > > In any case, I tried the boot-only CD, and I was not able to install any > > > packages during the install process. Sysinstall aborted with Signal 11 > > > when trying to read INDEX from the ftp site. Pkg_add from the command > > > line seems to work, however, so it looks like I may get online from > > > 7.0-BETA3 tomorrow. > > > > That is expected, packages are not available until later in the release > > cycle. > > > > > Moreover, wasn't there supposed to be a new install program? I have > > > read some promising remarks about it, but it's certainly not part of > > > 7.0-BETA3. Personally, I would much rather type a long list of commands > > > than use the old, rickety sysinstall. > > > > One is in early development, but not even complete let alone ready to > > replace sysinstall. > > > > Kris > > ___ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > > Kris can I ask what sort of importance bugs that cause crashes (page > faults) are? > I reported 2 bugs before BETA1 both these bugs involved 7.0 getting a > page fault and of course then stop responding requiring a reboot yet > both PRs have had no response and both bugs are still present in BETA3 > I see minor issues been worked on such as responsiveness in desktop > use whilst issues that cause system crashes are left unattended. Is > FreeBSD primarily a desktop os now and thats the new path? > > Try this. > > Login to twice on ssh. > If not root su both to root. > using the 2nd tty do a watch -W on the first tty. > on the first tty type 'killall watch' > you have now crashed freebsd 7 and most probably a auto reboot timer > is counting down. > > Even typing reboot to reboot the server causes page faults. > > This is nothing to do with hardware very repeatable behaviour happens > for me on at least 4 different freebsd 7 servers, if I compile world > with -O not -O2 the default it stops reboot causing page faults on > some of the servers. > > Chris > > Chris > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" This looks like your bug: >Description: when using the command killall watch with at least 1 active watch process running the kernel gets a page fault and reboots. Is the above the behaviour that's the problem, or is the behaviour you describe in your email the issue? I can confirm the stuff in your email, but haven't tried using killall watch when watch is using other options. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mount -u -o rw / not working on NFS?
On Mon, 2007-11-19 at 18:33 +0100, Laszlo Nagy wrote: > Hi All, > > I have a system where a diskless FreeBSD 6.3 i386 machine boots with pxeboot > from a FreeBSD 6.3 amd64 machine. I have lines in /etc/fstab for the diskless > machine like: > > # DeviceMountPoint FsType Options DumpPass > 172.16.0.1:/usr /usrnfs rw 0 0 > 172.16.0.1:/mnt/d2/rootfs/root /root nfs rw 0 0 > > The machine boots from network nicely, then I can login as root and invoke > these commands: > > mount -u -o rw / > mount -u -o rw /usr > mount -u -o rw /root > > There is no error message on the console, nor in the system log. However, > this happens afterwards: > > diskless101#mkdir /aaa > mkdir aaa: Read-only file system > > Question: if the remount did not succeed, why didn't it throw an error? If > succeeded, why can't I write on the filesystem? > > Thanks, > >Laszlo > The answer to the second portion is that you're mounted as a read only file system, so there's no write access. There's an nfs permissions file you may need to edit, /etc/exports/, which controls whether NFS shares the file system as read only, read write, whether root can have root on the file system etc. James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: evolution problems.
On Tue, 2007-11-20 at 01:34 +0800, OutbackDingo wrote: > Yupp as soon as Beta3 arrived i see problems even getting it to load, > takes 5 minutes to just start it, though i dont know if i can say its > the OS > That is *exactly* the same problem I started reporting with Beta 1.5. I'm thinking I need to get in touch with [EMAIL PROTECTED] James > > On Mon, 2007-11-19 at 09:30 -0800, Gary Kline wrote: > > Has anybody had any recent problems exec'ing evo? Say, in > > just the past several days? Here is output to the screen when I > > involve it from the cmd line: > > > > > > > > p0 9:17 [164] evolution > > CalDAV Eplugin starting up ... > > Loading Spamassasin as the default junk plugin > > ** (evolution:44175): DEBUG: mailto URL command: evolution %s > > ** (evolution:44175): DEBUG: mailto URL program: evolution > > > > warning: Unable to get location for thread creation breakpoint: generic > > error > > Backtrace limit of 200 exceeded > > /usr/local/share/bug-buddy/gdb-cmd:3: Error in sourced command file: > > Backtrace limit of 200 exceeded > > Backtrace limit of 200 exceeded > > zsh: killed evolution > > p0 9:18 [165] LibGTop-Server: pid 44178 received eof. > > > > > > As a FWIW, I should add that when I click on System -> Preferences > > -> Preferred Application I have chosen my Web Broswer and my > > Mail Reader which are dark, but the "Command [evolution %s]" > > is greyed-out. Dunno if this means annything, but maybe. > > > > Anybody see what's wrong here? > > > > gary > > > > > > > > > > > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: evolution slow on 7.0
On Fri, 2007-11-16 at 11:44 +0100, Oliver Peter wrote: > On Wed, Nov 14, 2007 at 03:45:28PM -0700, James wrote: > > Hi folks, > > > > first, I know the subject line is a goldmine for jokes, but I couldn't > > think of a better way to phrase it. > > > > Ever since I moved to FreeBSD 7.0, the evolution mail client has become > > ridiculously slow for me. It takes two or three minutes to start up, > > right clicking on a folder takes several minutes to display a context > > menu etc > > > > My install process was as follows: > > > > 1. backup my home directory from a FreeBSD 6.2 install > > 2. Format the hard drive > > 3. Install 7.0 beta 1.5 > > 4. csup sources and install beta 2.0 > > 5. pkg_add xorg, gnome etc -- evolution was slow as a dog from this > > 6. portsnap fetch extract > > 7. follow the instructions in UPDATING for updating gnome > > > > I tried cd /usr/ports/mail/evolution && make deinstall && make > > reinstall, to see if something had simply gone wrong during the build, > > but nothing changed. > > > > Any ideas? > > An random idea: What scheduler are you using in your kernel > configuration? Do you already use SCHED_ULE ? > I built it according to defaults, so I've got the GENERIC kernel running right now. As such, I don't know the answer to your question, but if you tell me how to check I'll get back to you :) James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
