tag:blogger.com,1999:blog-7226944307125070492023-11-15T09:14:13.697-06:00The Lone SysAdminThe trials and tribulations of a lone system administratorJoehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.comBlogger12125tag:blogger.com,1999:blog-722694430712507049.post-24870146622532394802018-09-05T10:28:00.000-05:002018-09-05T10:28:28.318-05:00Building a statically linked rsyncInstall dependencies for building:<br />
<blockquote>yum -y install glibc-static popt-devel popt-static</blockquote><br />
Download, then build:<br />
<blockquote>tar xf rsync-3.0.9.tar.gz<br />
cd rsync-3.0.9<br />
./configure<br />
make CFLAGS="-static" EXEEXT="-3.0.9-static"<br />
strip rsync-3.0.9-static<br />
</blockquote><br />
That's what I needed to do on RHEL7. YMMV.Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-53987331032068745462012-09-21T14:03:00.000-05:002012-09-21T14:03:06.174-05:00What packages require a given package?How do you determine what packages require a given package?<br />
<blockquote>repoquery --tree-whatrequires <package></blockquote>For example, let's say you want to find out what packages depend on rdma:<br />
<blockquote>$ repoquery --tree-whatrequires rdma<br />
rdma-1.0-14.el6.noarch [cmd line]<br />
\_ opensm-3.3.9-1.el6.x86_64 [1: rdma = 1.0-14.el6]<br />
$<br />
</blockquote>There you have it... opensm is the only package that requires rdma.<br />
<br />
Source: <a href="http://stackoverflow.com/questions/4869180/how-do-you-find-out-what-rpms-in-a-repository-depend-on-a-particular-rpm">Stack Overflow</a>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-51709297358441130012011-10-22T16:02:00.001-05:002011-10-22T16:02:51.988-05:00The Philosophy of Monitoring<div><p>This is a really good one too...</p>
<p><a href="https://lopsa.org/content/philosophy-monitoring">The Philosophy of Monitoring | League of Professional System Administrators</a><br>
</p>
</div>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-51278278575616014272011-10-22T14:03:00.001-05:002011-10-22T14:03:11.386-05:00Cargo Cult System Administration<div><p>Great post that I had to share...</p>
<p><a href="http://feedproxy.google.com/~r/lonesysadmin/mkpe/~3/0IPoETCrHew/">Cargo Cult System Administration</a><br>
</p>
</div>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-59999423561090155542011-02-09T12:33:00.000-06:002011-02-09T12:33:19.409-06:00RHEL5 Interactive Startup Without Pressing "i"This was not easy information to come by, but once I dug through RHEL5's /etc/rc.sysinit it was obvious. Instead of pressing "i" when prompted for an interactive startup (ie, asking if you want to start each service), you can add "confirm" to the kernel command line in GRUB.Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-7838058385563678812010-12-17T16:21:00.000-06:002010-12-17T16:21:39.142-06:00Changing File PermissionsMaybe I missed the memo on this feature of chmod(1), but I really dig it.<br />
<blockquote>chmod o=g foo</blockquote>That sets the "other" permissions to whatever the "group" permissions are. Combine that with "-R" and you can quickly adjust the "other" permissions of a whole tree to be the same as the file/dir "group" permissions.<br />
<br />
Of course, care should be taken so as to not grant everyone write permissions. :)Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-51622758553020288252009-10-07T10:36:00.000-05:002009-10-07T10:36:22.886-05:00Debian pushes development of kFreeBSD portWoohoo!!! I'll definitely be <strike>playing</strike> testing this out...<br />
<br />
<a href="http://www.debian.org/News/2009/20091007">http://www.debian.org/News/2009/20091007</a>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0tag:blogger.com,1999:blog-722694430712507049.post-59374039894234961582009-09-22T16:52:00.000-05:002009-09-22T16:52:32.779-05:00DHCP UsageI don't think anybody reads this blog, but...<br />
<br />
If anybody <i>is</i> reading (Hello? Is this thing on?) I have a question... How extensive is your use of DHCP? I'm slowly migrating almost every network device to statically assigned DHCP, including servers. Do you use DHCP for servers and other fixed devices?<br />
<br />
Just wonderin'...Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com2tag:blogger.com,1999:blog-722694430712507049.post-36272199089698187502009-09-09T14:29:00.001-05:002009-09-09T14:30:11.478-05:00Upgrading RHEL from 5.3 to 5.4I was having all sorts of strange problems while upgrading my test box from RHEL5.3 to RHEL5.4. I did a search, but it didn't seem to turn up much... just a link to an unrelated problem, and a Russian website. Well, I don't know Russian but I was able to decipher a hint: "yum clean all". That did the trick. I think I'll run that prior to upgrading all my production boxes. Here's the error I was getting:<br />
<br />
<pre># yum update libX11
Loaded plugins: rhnplugin, security
Skipping security plugin, no data
Setting up Update Process
Resolving Dependencies
Skipping security plugin, no data
--> Running transaction check
--> Processing Dependency: libX11 = 1.0.3-9.el5 for package: libX11-devel
---> Package libX11.i386 0:1.0.3-11.el5 set to be updated
--> Running transaction check
---> Package libX11-devel.i386 0:1.0.3-11.el5 set to be updated
--> Processing Dependency: /usr/share/X11/XKeysymDB for package: openmotif22
--> Processing Dependency: /usr/share/X11/XKeysymDB for package: openmotif
--> Finished Dependency Resolution
openmotif22-2.2.3-18.i386 from installed has depsolving problems
--> Missing Dependency: /usr/share/X11/XKeysymDB is needed by package openmotif22-2.2.3-18.i386 (installed)
openmotif-2.3.1-2.el5.i386 from installed has depsolving problems
--> Missing Dependency: /usr/share/X11/XKeysymDB is needed by package openmotif-2.3.1-2.el5.i386 (installed)
Error: Missing Dependency: /usr/share/X11/XKeysymDB is needed by package openmotif22-2.2.3-18.i386 (installed)
Error: Missing Dependency: /usr/share/X11/XKeysymDB is needed by package openmotif-2.3.1-2.el5.i386 (installed)
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
</pre>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com1tag:blogger.com,1999:blog-722694430712507049.post-25834594183190958282009-08-19T17:00:00.000-05:002009-08-19T17:00:58.368-05:00FocusIt's nice to be able to dive into a project and not have emergencies that need to be dealt with. I've made a lot of headway into setting up my <a href="http://bcfg2.org/">Bcfg2</a> repository. But when you start to surface, you realize that all those items in your inbox still need to be taken care of, even if they're not emergencies. There's a lot of 'em...Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com2tag:blogger.com,1999:blog-722694430712507049.post-21543104872456869472009-06-24T11:44:00.001-05:002009-06-24T11:52:44.063-05:00How to Find Dangling SymlinksSometimes, you need to find all symbolic links which point to a non-existant target (aka, a dangling symlink). Well, I found[1] an easy way to dig them up...<br />
<blockquote>find -L . -type l</blockquote>And the best part is, it's portable (well, it works on RHEL5, Ubuntu 6.06, and Mac OS X 10.5). Another way[2] to do it with GNU find is...<br />
<blockquote>find . -follow -lname '*'</blockquote>[1] <a href="http://linux.derkeiler.com/Mailing-Lists/Debian/2006-06/msg01907.html">http://linux.derkeiler.com/Mailing-Lists/Debian/2006-06/msg01907.html</a><br />
[2] <a href="http://mail.milwaukeelug.org/wws/arc/mlug-list/2007-03/msg00243.html">http://mail.milwaukeelug.org/wws/arc/mlug-list/2007-03/msg00243.html</a>Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com2tag:blogger.com,1999:blog-722694430712507049.post-16071216340895659222009-06-17T12:10:00.004-05:002009-06-17T12:30:23.687-05:00RHEL5 and FirewireIt took a while, but I finally figured out how to fully enable firewire in RHEL5.3.<br /><br />Because firewire is still a "Technology Preview" in RHEL5.3, you must disable the blacklisting of the kernel module in <span style="font-style: italic;">/etc/modprobe.d/blacklist-firewire</span><br /><pre># Comment out the next line to enable the firewire drivers<br />#blacklist firewire-ohci<br /></pre>But that's not all you have to do... Oh no... In order for the drive to be visible in your file manager (we use Xfce, but it also applies to Gnome), you must also mark the drive as "hotpluggable" in HAL. Why it isn't done so automatically, I don't know.<br /><br />Create or update the file <span style="font-style: italic;">/etc/hal/fdi/policy/preferences.fdi</span> with this code:<br /><pre><?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- --><br /><deviceinfo version="0.2"><br /><device><br /> <match key="@info.parent:@info.parent:@info.parent:info.linux.driver" string="firewire_ohci"><br /> <match key="info.category" string="storage"><br /> <match key="storage.drive_type" string="disk"><br /> <merge key="storage.hotpluggable" type="bool">true</merge><br /> </match><br /> </match><br /> </match><br /></device><br /></deviceinfo><br /></pre>Now, I don't know if that's the <span style="font-style: italic;">best</span> matching, but it works.Joehttp://www.blogger.com/profile/08996979219430469815noreply@blogger.com0