Hey Darrick,
My build system was under Ubuntu 8.04 x86_64. I did it on a VPS I have.
I honestly didn't really spend too much time debugging it, as I had
already spent about 3 hours (starting at 12AM) trying to get everything
else working. Mostly ran into just missing libraries and stuff like
that. If I recall correctly, it had something to do with not being able
to find nlist.h or the iksemel libraries, both of which were installed
on the box. I did a little research and found some possible
configure.in work arounds, but as it was late and I finally hit the "z"
packages (home stretch), I just wanted to get it finished so gave up
trying. Not to mention not having a use for zabbix anyway.
The most confusing issue was failing at getting 'at' to compile. It was
also having similar problems.
No big deal on the nfsd stuff. Samba is working well for me. I was more
curious as to whether I was missing something or if it just wouldn't
work. I like trying to get the most out of hardware, so I'm pushing
this little box to the limit. Outside of Asterisk of course, and
serving as a router w/QoS, firewall, NAT, inter-vlan routing, etc., I
also have openvpn server working, just finished tweaking msmtp to
forward voicemail-to-email through my remote mail server, and now have
it configured as a file server for media.
Earlier I doing some testing to see how much it could handle. Had two
samba transfers going to it, a torrent download through it (with about
100 peer connections), pushed some traffic through the VPN tunnel, and
had four calls into a conference bridge, three remote and a local.
Didn't skip a beat on any of it. Not too bad for a little 1ghz VIA
processor with 256MB of ram.
Only weird issue I'm still having is with memory usage. For some reason
I haven't been able to figure out my available memory floats down from
about 110 to 4MB randomly through the day. First I thought it might be
a tmpfs issue, but eliminated that possibility. Trimmed Asterisk down a
little and started systematically killing processes to see if I could
find a cause, but nothing yet. Don't have a lot of time right now, and
the diagnostic tools are a bit limited, but will look into it more
later.
Thanks again.
-James
Darrick Hartman wrote:
James,
Glad you were able to get most of this figured out. We could possibly
look at adding support for nfsd sometime later in the cycle again if
there was enough demand for it. It may require a kernel module.
Can you tell me what Linux distribution your build system is running?
Someone else reported a problem with building zabbix too. I have not
seen any issues on Fedora or CentOS builds. It's a small binary but
does nothing if you're not using the zabbix monitoring system. Because
it's small, I made it a default build option. You certainly won't break
anything by disabling it in the 'make menuconfig' step.
Darrick
On 12/29/2009 09:59 PM, James F. Babiak wrote:
Thanks for the information. Did it ever officially support being
utilized as an NFS server? I imagine since there is some legacy, albeit
broken, nfsd stuff still present that at one time it would have
supported it. Especially since there are NFS_EXPORT variables to define
what you want to share. Though like I said earlier, I couldn't find
anything in the svn repository going back to 0.4 that directly supported
it. And based on the included nfsd init scripts, assume it wasn't a
kernel module.
In any case, I was able to setup a build environment for my via system
and built the 0.7 branch including samba support. Outside of having to
install about two dozen packages to get it working (and having issues
with 'at' and 'zabbix' for some reason, and being forced to exclude them
in the end), got everything working. Not wanting to mess with loading a
new full custom image right away, I copied over the smbd, nmbd and samba
client utilities and wrote up an smbd.conf file for my existing beta 0.7
system. A few tweaks and I got everything up and running. Was able to
successfully share /mnt/usb with read/write access. Transfered over a
700MB file at about 4.5MBps. Not too shabby for samba. So now I can have
my astlinux box serve as a NAS device too!
-James
Darrick Hartman wrote:
On 12/28/2009 11:51 AM, James Babiak wrote:
Hey Everyone,
I'm new to the mailing list, and had a question that hopefully someone
can help me with. I'm using the beta version of Astlinux 0.7, and am
trying to setup nfsd to export a share. Basically, I want to try to get
the box to be a NAS server of sorts. I have a USB drive attached and
it's mounted on /mnt/usb. I actually ran into issues getting it to
automount on reboots. Reading other messages on this list I found the
only successful way to get this to work was by appending a mount command
to the end of /etc/rc. Any other method, via fstab or mouting it in
/etc/rc with the rest of the filesystem, failed. But that problem has
been solved. My only remaing issue is getting nfsd working properly.
I ran into a few problems even figuring out how to get nfsd started. I
found that I had to load it as a kernel module, as there was no
userspace nfsd. In fact, I don't see anything in the filesystem for nfs
outside of a kernel module, and an invalid init.d script. I say invalid
because /etc/init.d/nfsd uses nfsd,mountd,lockd and portmap to start,
but those are not present in the filesystem. I didn't see any
nfs-kernel-server start-up script. I setup the variables for rc.conf in
/mnt/kd/rc.conf.d/nfs.conf for:
NFS_EXPORTS_RW="/mnt/usb"
NFS_EXPORTS_RO="/mnt/kd"
(the usb one being the one I care about, and adding the kd one since it
wasn't working without a RO line and I thought maybe it needed one too?)
and this appends to /etc/rc.conf as well as creating the /etc/exports
file with:
/mnt/kd 172.20.0.0/24(ro,no_root_squash,sync)
<http://172.20.0.0/24(ro,no_root_squash,sync)>
/mnt/usb 172.20.0.0/24(rw,no_root_squash,sync)
<http://172.20.0.0/24(rw,no_root_squash,sync)>
in it. So far so good. However, nothing I do manually will get it
working. When I load (manually or automatically) the nfsd kernel module,
I get:
nfs 216360 0
nfs_acl 2624 1 nfs
lockd 53832 1 nfs
sunrpc 162876 5 nfs,nfs_acl,lockd
all loaded. I've never really messed with nfs-kernel-server, so I read
up on it. I see there are commands to push export changes out, but don't
see anything installed that will do it.
Reading up on other people's nfs work with Astlinux on the mailing list
in the past, it seems like others have gotten it working. I thought
maybe the beta, or current, release was lacking something, so I svn'd
the entire trunk and all branches out of the repository to see if I am
missing something, or can enable something in a custom image. But as far
as I can tell, there was never any apps available for nfsd, at least
since 0.4. So I'm not sure how /etc/init.d/nfsd ever worked.
Am I missing something, or has anyone else had any success doing what I
am trying to do? I've gotten everything else working except for the nfs
stuff, and would really like to get that up and running too. Worst case
scenario, I see there seems to be a samba server available in the trunk,
so I might have to play with that.
Any help would be appreciated. Thanks!
-James
AstLinux is not designed to be an nfs server. It's designed to have nfs
client access to an nfs server.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
|
