Best of Technical Support

Our experts answer your technical questions.
PLIP or SLIP?

Is there an easy way to connect my laptop running MS Windows for WorkGroups to my PC running Red Hat 5.0? Should I use PLIP, SLIP or something else? —Thomas Svanelind

PLIP is probably the cheapest and simplest networking setup around (although it has limitations), and it is supported by both platforms. —Scott Maxwell, maxwell@pacbell.net

Time Synchronization

How does someone configure Time Synchronization with Debian 1.3.1? Specifically, I want my Linux computer to get the current time from another computer. —Michael Breton, michaelb@geiger.com

A pair of time protocols is available for use over the network. The easiest choice is rdate, which gives accuracy to within one second. For example, by having this line in my root crontab file, my host “morgana” resyncs with “hyppy” at 10 AM every day:

0 10 * * * rdate -s hyppy

--Alessandro Rubini, rubini@prosa.it

Netscape Mail

I am using Red Hat 5.0. I want to use Netscape for mail; however, the SMTP mailer (Sendmail) and the POP3 mailer clash to the extent that some mail is coming into Netscape and some is going to Sendmail, accessed via elm.

I would like all mail to go through Netscape (POP3) via the ISP. How do I stop Sendmail or halt it? Thanks in advance for any help. —Bill Lunnon, bill@mirrim.demon.co.uk

Sendmail is most likely sending out mail using your full host name. When a recipient replies to a message you sent from elm, the reply is sent directly to your computer and not to your mailbox at your ISP. The easiest workaround is to set the Reply-to: field in Netscape's mail preferences to your correct e-mail address. A better solution is to edit the /etc/sendmail.cf file to set the domain Sendmail masquerades as. This will exclude your host name from mail sent out using Sendmail. —Peter Struijk, bts@ssc.com

Changes After Restoring /home

Somewhere along the line I thought I messed up the file systems under the /home directory (I have a number of user accounts here), so I restored /home using a tar backup file. Ever since then, I have not been able to get information when running various things like finger or whoami.

When I do whoami, I get the following message instead of the alias name: “whoami: cannot find user name for UID 500” where I used to see grb. When I do a finger while logged on as myself or another user, I get this message: “No one logged on” instead of a list of users logged onto the system.

When I type the command ls -al, I get the user ID number and group ID number instead of the login name: e.g., instead of user and group ID both being grb, they have the value 500, which is correct according to what I assigned when originally setting up the accounts. However, I used to see the alias names.

I cannot get the Caldera Desktop to run while logged in as any user, and before, everything ran just fine. When running the startx program—it tries to initialize and I even see a color background—the server bombs and goes back to the /dev/tty screen. Looking at the Xerror logs doesn't give me any information as to why it is now failing.

I can still start a customized X session with a TWM-type desktop while running the XwinPro PC X package on my PC. I can also run programs on the client X server with no problem. I am at a loss as to what to do to get the system restored or corrected at this point. Can you offer an explanation and a possible fix to this problem? Thank you in advance for any help you may offer. —George R. Boyko, grb99@nni.com

These symptoms sound a lot like problems with permissions. This crops up sometimes when you restore with tar. If you do not set your umask to 0 before doing the restore, then tar will obey the current umask when restoring files. In addition, tar finalizes permissions at the end of the restore process. So, it is possible to end up with incorrect ownership or permissions if the restore is interrupted before completion. If you restored /home by doing a full backup and then stopping it once /home had been restored, you could end up with home directories or other files with wrong ownership or permission bits.

To fix your problem, you will have to check that all of the directories in /home are owned by their proper owners and that the permissions give at least user read and write. Use chmod -R and chown -R to recursively change permissions or ownership of directories.

You should also check the /etc/passwd and the /etc/group files to be sure they are world-readable (chmod a+r). If they are not, this would explain the problem with ls reporting UID instead of name. Also, verify that the files /var/log/wtmp and /var/run/utmp are world-readable as well. If they are not, this would explain the problem with finger.

As for the Caldera Desktop and X, that could be a problem with the permissions of /tmp or /var/tmp. Type:

chmod a+rwxt /tmp /var/tmp

to set proper permissions (world read-write, sticky) on those directories. —Bob Huack, bobh@wasatch.com

______________________

Webinar
One Click, Universal Protection: Implementing Centralized Security Policies on Linux Systems

As Linux continues to play an ever increasing role in corporate data centers and institutions, ensuring the integrity and protection of these systems must be a priority. With 60% of the world's websites and an increasing share of organization's mission-critical workloads running on Linux, failing to stop malware and other advanced threats on Linux can increasingly impact an organization's reputation and bottom line.

Learn More

Sponsored by Bit9

Webinar
Linux Backup and Recovery Webinar

Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.

In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.

Learn More

Sponsored by Storix