Re: Extending pw(8) username limit
I already run 10 domains worth of emails here, I would prefer to avoid adding
anything that will screw with already functioning accounts...
But maybe there's an option on Dovecot to reroute specific username requests to
masquerade that... I'll check that out tomorrow.
Thanks.
On Apr 14, 2011, at 4:49 PM, Chuck Swiger wrote:
> On Apr 14, 2011, at 2:20 PM, Ryan Coleman wrote:
>> I have a special situation where I'd like to do either
>> first.last_somedomain.com or first.l...@somedomain.com but the former is
>> rejected due to length and the latter due to the "@" by pw(8).
>>
>> How do I extend this from 16 chars to 32 or 64? I have been finding it
>> difficult to find explicit details on this.
>
>> From prior experience, your users are going to loathe ("hate" isn't strong
>> enough) 16+ character usernames.
>
> If the problem is that you want to setup email aliases mapping (eg)
> charles.swiger, charles_swiger, chuck.swiger, etc, etc to cswiger, the mail
> aliases file supports that just fine. And if you want to support users in
> multiple domains, the /etc/passwd database is just not the place to do it.
> Consider SASL, LDAP, or even NIS+; and SASL in particular integrates very
> smoothly with multi-domain email via Cyrus, Dovecot, etc.
>
> 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"
___
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: Extending pw(8) username limit
On Apr 14, 2011, at 2:20 PM, Ryan Coleman wrote:
> I have a special situation where I'd like to do either
> first.last_somedomain.com or first.l...@somedomain.com but the former is
> rejected due to length and the latter due to the "@" by pw(8).
>
> How do I extend this from 16 chars to 32 or 64? I have been finding it
> difficult to find explicit details on this.
>From prior experience, your users are going to loathe ("hate" isn't strong
>enough) 16+ character usernames.
If the problem is that you want to setup email aliases mapping (eg)
charles.swiger, charles_swiger, chuck.swiger, etc, etc to cswiger, the mail
aliases file supports that just fine. And if you want to support users in
multiple domains, the /etc/passwd database is just not the place to do it.
Consider SASL, LDAP, or even NIS+; and SASL in particular integrates very
smoothly with multi-domain email via Cyrus, Dovecot, etc.
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"
Extending pw(8) username limit
I have a special situation where I'd like to do either first.last_somedomain.com or first.l...@somedomain.com but the former is rejected due to length and the latter due to the "@" by pw(8). How do I extend this from 16 chars to 32 or 64? I have been finding it difficult to find explicit details on this. Thanks, Ryan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
Damien Fleuriot wrote: > > > On 4/13/11 6:40 PM, Michael J. Kearney wrote: [snip] >> >> Hi, I am new to the Linux environment. FreeBSD is *NOT* Linux! >> I am trying to build a virtual >> Freebsd server to run another virtual device (a Juniper router). I have >> found that after building the base operating system that I cannot >> remotely access the virtual Freebsd server. I have tried using both Qemu >> and VMware with the same result. It looks to me as though the server has >> a default setting that allows it to contact other devices (e.g., I can >> ping, ftp, telnet, etc., other devices from my Freebsd server) but I >> cannot ping, ftp, telnet into the Freebsd server from my host PC. My >> host is a Windows 7 desktop, but I have tried pinging from another >> virtual device and cannot get a response from the Freebsd server. I do >> not believe that the issue is my Windows 7 PC. >> >> I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also >> tried a few other images with the same result. >> >> I have combed through the documentation, tried configuring the firewall >> using the "open" template, tried to disable the packet filter in rc.conf >> (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no >> matter what I have tried, and I feel I have exhausted my options. The >> ports are open and responsive on the virtual server itself, but access >> seems to be blocked to the Freebsd server. >> >> I am hoping you can tell me how to change the default settings on the >> Freebsd server to allow access from my Windows 7 host PC. Hopefully it >> does not involve manually rebuilding the kernel! >> [snip] > > > This has nothing to do with firewalling. > > He's very likely using NAT on his virtual machine. > > So outgoing connections work just fine: NAT from the guest through the > host. > > But inbound connections fail, and rightly so: NO NAT *to* the guest > through the host. I use VirtualBox these days, but if memory serves it is very much like Vmware in this regard. The OP needs to understand that the default install provides a NAT and a DHCP for the guest VM so it can be brought up automagically. I know in the VirtualBox documentation it is clearly explained about how incoming connections are not passed through this NAT. There are typically 3 networking configurations available: the default as described above, bridged, and host-only. Host-only does exactly what it sounds like - only the host machine and guest may communicate with each other. Bridged networking is what you want to set up if you want your VM to be totally available to your outside network. Hint: the "bridge" is not on the VM guest OS side, but rather the bridge would connect your Windows 7 host's NIC to the VM. A bridged config replaces the default install NAT. I haven't used Vmware for a while now, but in VirtualBox you can use the VBoxManage command line to enable port forwards in the default install's NAT. This is OK if you only want to make a small number of services available, like let's say only a web server on port 80. But you'll want a bridged config if you want the entire VM visible. -Mike ___ 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"
Two questions
Yesterday I received some very helpful advice from your technician. I hope you can answer these two questions today! I am trying to configure Freebsd so that I can access it from my host PC, which is Windows 7. Yesterday the technician told me to configure bridging in VMware when I created the virtual Freebsd server. This worked fine, but I'm wondering if there is a way to configure this outside of VMware. I tried this on a Freebsd v8.2: ifconfig bridge create ifconfig bridge0 addm em0 addm em1 up #interface names are em0 and em1 But it did not work. I assigned an IP address to em0 but could not access it from my Windows 7 host, although I could ping that address from the virtual server (TCP/IP stack was working). Is there something else I need to do to get this to work? My second question is that this command is not in an older version of Freebsd that I am using, v4.11. Do you have other commands to create a bridged interface on this version? Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ZFS performance strangeness
On 4/12/11 1:33 PM, Lars Wilke wrote: > Hi, > > There are quite a few threads about ZFS and performance difficulties, > but i did not find anything that really helped :) > Therefor any advice would be highly appreciated. > I started to use ZFS with 8.1R, only tuning i did was setting > > vm.kmem_size_scale="1" > vfs.zfs.arc_max="4M" > > The machines are supermicro boards with 48 GB ECC RAM and 15k RPM SAS > drives. Local read/write performance was and is great. > But exporting via NFS was a mixed bag in 8.1R. > Generally r/w speed over NFS was ok, but large reads or writes took > ages. Most of the reads and writes were small, so i did not bother. > > Now i upgraded one machine to 8.2R and i get very good write performance > over NFS but read performance drops to a ridiciously low value, around > 1-2 MB/s. While writes are around 100MB/s. The network is a dedicated > 1GB Ethernet. The zpool uses RAIDZ1 over 7 drives, one vdev. > The filesystem has compression enabled. Turning it off made no > difference AFAICT > > Now i tried a few of the suggested tunables and my last try was this > > vfs.zfs.txg.timeout="5" > vfs.zfs.prefetch_disable="1" > vfs.zfs.txg.synctime=2 > fs.zfs.vdev.min_pending="1" > fs.zfs.vdev.max_pending="1" > > still no luck. Writting is fast, reading is not. Even with enabled > prefetching. The only thing i noticed is, that reading for example 10MB > is fast (on a freshly mounted fs) but when reading larger amounts, i.e. > couple hundred MBs, the performance drops and zpool iostat or iostat -x > show that there is not much activity on the zpool/hdds. > > It seems as if ZFS does not care that someone wants to read data, also idle > time of the reading process happily ticks up and gets higher and higher!? > When trying to access the file during this time, the process blocks and > sometimes is difficult to kill, i.e. ls -la on the file. > > I read and write with dd and before read tests i umount and mount the > NFS share again. > > dd if=/dev/zero of=/mnt/bla size=1M count=X > dd if=/mnt/bla of=/dev/null size=1M count=Y > > mount is done with this options from two centos 5 boxes: > rw,noatime,tcp,bg,intr,hard,nfsvers=3,noacl,nocto > > thanks >--lars > > ___ > 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" I refer you to this post by Jeremy Chadwick with tuning values *AND* their actual explanation. http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061642.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"
Re: Remote access to Freebsd server
On 4/13/11 6:40 PM, Michael J. Kearney wrote: > /var/log/security and "ipfw list" ftw. .. if a rule maches your configuration > atm > > afiddler10 wrote: > > > Hi, I am new to the Linux environment. I am trying to build a virtual > Freebsd server to run another virtual device (a Juniper router). I have > found that after building the base operating system that I cannot remotely > access the virtual Freebsd server. I have tried using both Qemu and VMware > with the same result. It looks to me as though the server has a default > setting that allows it to contact other devices (e.g., I can ping, ftp, > telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, > telnet into the Freebsd server from my host PC. My host is a Windows 7 > desktop, but I have tried pinging from another virtual device and cannot get > a response from the Freebsd server. I do not believe that the issue is my > Windows 7 PC. > > I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried > a few other images with the same result. > > I have combed through the documentation, tried configuring the firewall using > the "open" template, tried to disable the packet filter in rc.conf > (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter > what I have tried, and I feel I have exhausted my options. The ports are > open and responsive on the virtual server itself, but access seems to be > blocked to the Freebsd server. > > I am hoping you can tell me how to change the default settings on the Freebsd > server to allow access from my Windows 7 host PC. Hopefully it does not > involve manually rebuilding the kernel! > > Thanks for your help! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" This has nothing to do with firewalling. He's very likely using NAT on his virtual machine. So outgoing connections work just fine: NAT from the guest through the host. But inbound connections fail, and rightly so: NO NAT *to* the guest through the host. ___ 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: PAE: Cannot fork
On Thu, 14 Apr 2011 05:14:37 -0500, Dennis Nikiforov wrote: There is a legacy piece of custom software that runs only on 32 bit systems, so going to 64 bit is not possible. Run it in a 32bit jail. PAE has never been very stable/reliable. Regards, Mark ___ 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: PAE: Cannot fork
On 14/04/2011 12:14, Dennis Nikiforov wrote: There is a legacy piece of custom software that runs only on 32 bit systems, so going to 64 bit is not possible. Some ideas: 1) You can run 32-bit applications on 64-bit FreeBSD (and / or set up a 32-bit jail) 2) You can try booting a snapshot of 9-CURRENT and see if it helps. I think I saw some commits that could have fixed this problem. As far as I can see, 9-CURRENT is quite stable right now (and should be much faster than the 7.x you are proposing to use). ___ 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: ZFS performance strangeness
On 12/04/2011 13:33, Lars Wilke wrote: Now i upgraded one machine to 8.2R and i get very good write performance over NFS but read performance drops to a ridiciously low value, around 1-2 MB/s. While writes are around 100MB/s. The network is a dedicated If you don't get any answer here, try posting on the freebsd-fs @ freebsd.org list. ___ 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: PAE: Cannot fork
Well, the idea was to run many instances of the app (each process does not need more than a couple of gigs of ram). Using virtualization is another option, but it will require a lot more maintenance of every VM. It would be a lot better if a single OS can use PAE. On Apr 14, 2011, at 3:47 PM, krad wrote: > > > On 14 April 2011 11:14, Dennis Nikiforov wrote: > There is a legacy piece of custom software that runs only on 32 bit systems, > so going to 64 bit is not possible. > > On Apr 14, 2011, at 12:08 PM, krad wrote: > >> >> >> On 14 April 2011 08:05, Dennis Nikiforov wrote: >> Hello, >> >>I have a problem with FreeBSD 7.x 32bit running the standard PAE >> kernel on a dell R210 server with 16GB of RAM. All servers spec'ed like this >> have the same identical problem and it is not a hardware issue because all >> memory tests have been negative. >> >>basically the issue comes after PAE kernel has been compiled and the >> system outputs all the time the following: >> >>cannot fork kstack allocation failed or vm_thread_new: kstack >> allocation failed >> >>Since, this is a dell server there is basically nothing that I can >> disable in BIOS, so perhaps someone knows what loader options do I need to >> tweak the kernel and stop this from happening. >> >> Thanks, >> Dennis___ >> 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 not use 64 bit as the r210 should be capable > > > not even with lib32, also why not just not run pae. After all if its a 32bit > app it cant address all the ram anyhow ___ 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: PAE: Cannot fork
On 14 April 2011 11:14, Dennis Nikiforov wrote: > There is a legacy piece of custom software that runs only on 32 bit > systems, so going to 64 bit is not possible. > > On Apr 14, 2011, at 12:08 PM, krad wrote: > > > > On 14 April 2011 08:05, Dennis Nikiforov wrote: > >> Hello, >> >>I have a problem with FreeBSD 7.x 32bit running the standard PAE >> kernel on a dell R210 server with 16GB of RAM. All servers spec'ed like this >> have the same identical problem and it is not a hardware issue because all >> memory tests have been negative. >> >>basically the issue comes after PAE kernel has been compiled and >> the system outputs all the time the following: >> >>cannot fork kstack allocation failed or vm_thread_new: kstack >> allocation failed >> >>Since, this is a dell server there is basically nothing that I can >> disable in BIOS, so perhaps someone knows what loader options do I need to >> tweak the kernel and stop this from happening. >> >> Thanks, >> Dennis___ >> 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 not use 64 bit as the r210 should be capable > > > not even with lib32, also why not just not run pae. After all if its a 32bit app it cant address all the ram anyhow ___ 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: PAE: Cannot fork
There is a legacy piece of custom software that runs only on 32 bit systems, so going to 64 bit is not possible. On Apr 14, 2011, at 12:08 PM, krad wrote: > > > On 14 April 2011 08:05, Dennis Nikiforov wrote: > Hello, > >I have a problem with FreeBSD 7.x 32bit running the standard PAE > kernel on a dell R210 server with 16GB of RAM. All servers spec'ed like this > have the same identical problem and it is not a hardware issue because all > memory tests have been negative. > >basically the issue comes after PAE kernel has been compiled and the > system outputs all the time the following: > >cannot fork kstack allocation failed or vm_thread_new: kstack > allocation failed > >Since, this is a dell server there is basically nothing that I can > disable in BIOS, so perhaps someone knows what loader options do I need to > tweak the kernel and stop this from happening. > > Thanks, > Dennis___ > 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 not use 64 bit as the r210 should be capable ___ 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: PAE: Cannot fork
On 14 April 2011 08:05, Dennis Nikiforov wrote: > Hello, > >I have a problem with FreeBSD 7.x 32bit running the standard PAE > kernel on a dell R210 server with 16GB of RAM. All servers spec'ed like this > have the same identical problem and it is not a hardware issue because all > memory tests have been negative. > >basically the issue comes after PAE kernel has been compiled and the > system outputs all the time the following: > >cannot fork kstack allocation failed or vm_thread_new: kstack > allocation failed > >Since, this is a dell server there is basically nothing that I can > disable in BIOS, so perhaps someone knows what loader options do I need to > tweak the kernel and stop this from happening. > > Thanks, > Dennis___ > 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 not use 64 bit as the r210 should be capable ___ 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 8.2 (i386) does not install under Hyper-V
Try to install FreeBSD 8.2 on Hyper-V but some-virt-hdd.VHD not bigger then 30Gb. ___ 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"
PAE: Cannot fork
Hello, I have a problem with FreeBSD 7.x 32bit running the standard PAE kernel on a dell R210 server with 16GB of RAM. All servers spec'ed like this have the same identical problem and it is not a hardware issue because all memory tests have been negative. basically the issue comes after PAE kernel has been compiled and the system outputs all the time the following: cannot fork kstack allocation failed or vm_thread_new: kstack allocation failed Since, this is a dell server there is basically nothing that I can disable in BIOS, so perhaps someone knows what loader options do I need to tweak the kernel and stop this from happening. Thanks, Dennis___ 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"
