similar to: Useful NFS hint

Hi all, I have an odd interaction on a CentOS 7 file server. The basic setup is a minimal 7.x install. I have 4 internal drives (/dev/sd[a-d]) configured in a RAID5 and mounted locally on /data. This is exported via NFS to ~12 workstations which use the exported file systems for /home. I have an external drive connected via USB (/dev/sde) and mounted on /rsnapshot. I use rsnapshot to back up

Steve, Thanks, makes sense. I just don't see why I have to effectively waste an extra IP address to get my connection established. Boris. On Fri, Jan 23, 2015 at 7:16 PM, Stephen Harris <lists at spuddy.org> wrote: > On Fri, Jan 23, 2015 at 07:10:57PM -0500, Boris Epstein wrote: > > > This makes two of us. I've done everything as you have described and it > >

On Fri, Apr 24, 2015 at 08:54:48AM -0400, Pete Geenhuizen wrote: > Even though Solaris started using ksh as the default user environment, > almost all of the start scrips were either bourne or bash scripts. With > Bash having more functionality the scripts typically used the > environment that suited the requirements best. Bash is a better command shell for many people, but ksh

On Sat, Sep 12, 2015 at 11:14:07AM +1000, Damien Miller wrote: > ssh server.example.com /usr/bin/do/something > r=$? > if [ $r -eq 0 ] ; then > echo success > elif [ $r -eq 255 ] ; then > echo ssh failed > else > echo command failed > fi ssh remoteserver exit 255 Hmm :-) exit(-1) aka exit(255) is a pretty standard "generic failure code" for many

On Fri, Mar 15, 2019 at 09:10:26AM +0000, Jochen Bern wrote: > Imagine sysadminning a boatload of VMs getting IPs from a dynamic pool, a la > > $ for ADDR in $CUSTOMER_1_RANGE $CUSTOMER_2_RANGE... ; do > > ping -c 1 -w 2 $ADDR >/dev/null 2>&1 && ssh root@$ADDR do_urgent_fix > > done > > , and it mightn't be that much of a niche anymore ... And

On Fri, Feb 27, 2015 at 12:38:06PM -1000, Dave Burns wrote: > What makes you think NIS is involved? > Is Errno 12 a clue? I tried searching for (do_ypcall: clnt_call: rpc: timed "do_ypcall" is a NIS error message. (Previous NIS was called "yellow pages"; the "yp" in do_ypcall is a reference to that). Maybe you have "hosts: files nis" in

On Fri, Apr 24, 2015 at 03:15:27PM +0200, Joerg Schilling wrote: > Stephen Harris <lists at spuddy.org> wrote: > > > Bash was bigger than ksh in the non-commercial Unix world because of ksh88 > > licensing problems. Back in 1998 I wanted to teach a ksh scripting > > course to my local LUG, but AT&T (David Korn himsef!) told me I couldn't > > give

On Tue, Jan 21, 2020 at 12:18:52PM +1100, Damien Miller wrote: > I wouldn't say it's a lot harder to take control of current connections - > writing a ptrace-based tool that hijacked a running ssh client and > injected a one-off implant payload via keystrokes doesn't seem like > much work. * Injection of key strokes into an existing channel may be detected just because

On Fri, Apr 24, 2015 at 08:32:45AM -0400, Scott Robbins wrote: > Wasn't Solaris, which for awhile at least, was probably the most popular > Unix, using ksh by default? Solaris /bin/sh was a real real dumb version of the bourne shell. Solaris included /bin/ksh as part of the core distribution (ksh88 was a part of the SVr4 specification) and so many scripts were written with #!/bin/ksh at

Tim, where did you installed this nrpe package? is selinux running enforcing mode (getenforce command), try disabling with setenforce 0. why you are running it under xinetd as usual way is to run it as nrped daemon. test against with check_nrpe, not using telnet. -- Eero 2015-05-04 2:27 GMT+03:00 Stephen Harris <lists at spuddy.org>: > On Sun, May 03, 2015 at 07:23:19PM -0400, Tim

Once upon a time, Stephen Harris <lists at spuddy.org> said: > On Sun, Apr 19, 2015 at 09:40:29PM -0400, Tim Dunphy wrote: > > Good tip! But I ran the script with sh +x . I guess that running it with sh > > You should use "bash -x" ("bash" and not "sh" because sh may not be bash > everywhere; eg Ubuntu; "-x" and not "+x"

Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN. Seems - and acts - like a legitimate setup and works fine, except for this particular instance. Thanks. Boris. On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml at

I thought I'd done that standard stuff /etc/modprobe.conf: alias net-pf-10 off alias ipv6 off /etc/sysconfig/network: NETWORKING_IPV6=no But on reboot I still see ipv6 entries against the eth devices, ipv6 module is still loaded, and sit0 tunnel is present. What needs to be done to disable ipv6? -- rgds Stephen

Hi All, I know this isn't the ganesha mailing list but wondered if anyone can help. I'm having issue with file creation over NFS, I have a gluster volume "vol1" presented via Ganesha with the following config:EXPORT{? ? ? ? Export_Id = 20;? ? ? ? Path = "/vol1";? ? ? ? FSAL {? ? ? ? ? ? ? ? name = GLUSTER;? ? ? ? ? ? ? ? hostname = "gnfs01";? ? ? ? ? ? ? ?

Hello, I'm having an unusual amount of trouble setting up Centos 6.6 as an NFS server. I have already created my exportfs file and run "chkconfig nfs on". When I try to start the nfs service with "service nfs start", I get FATAL: Module nfsd not found. FATAL: Error running install command for nfsd Starting NFS services: exportfs: internal: no supported addresses in

CentOS 6.4 x86_64 Kernel: 2.6.32-358.14.1.el6.x86_64 I have been noticing repeatedly that after a couple of weeks of uptime my NFS server starts to generate the following error: ------------[ cut here ]------------ WARNING: at lib/list_debug.c:26 __list_add+0x6d/0xa0() (Tainted: G W ---

I know, I know... don't use the non-standard kernels unless you have to... BUT: I have a D-Link N150 USB card. Bus 001 Device 004: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271] This isn't supported in C5, but it is supported in newer kernels (ath9k_htc). So let's try NDISwrapper: # rpm -i kmod\-ndiswrapper\-1.56\-1.el5.elrepo.i686.rpm

Hey All, Appears I solved this one and NFS mounts now work on all my clients. No issues since fixing it a few hours back. RESOLUTION Auditd is to blame for the trouble. Noticed this in the logs on 2 of the 3 NFS servers (nfs01, nfs02, nfs03): type=AVC msg=audit(1526965320.850:4094): avc: denied { write } for pid=8714 comm="ganesha.nfsd" name="nfs_0"

On Wed, Aug 22, 2018 at 11:23:11AM +0000, Peter Stuge wrote: > I guess that Oracle has patched sshd to call sd_notify() and thus Well, RedHat. > introduced dependency on the systemd libraries for sshd. I don't Yup % ldd /usr/sbin/sshd | grep syst libsystemd.so.0 => /lib64/libsystemd.so.0 (0x00007f0e5b715000) -- rgds Stephen

On Sun, Jan 25, 2015 at 09:12:29AM -0500, Boris Epstein wrote: > OK... but why does it need to be a trunk port? If you are on a trunk port then your machine needs to be configured for VLANs. If you are not on a trunk port then your machine needs to be configured normally. It _sounds_ like you have configured your machine for VLANs but are not on a trunk port. -- rgds Stephen