From 99bde6889d3d8b7a9e950c86c30e82662e1dacdd Mon Sep 17 00:00:00 2001 From: Gerald Carter Date: Tue, 9 Sep 2003 02:58:53 +0000 Subject: syncing files from 3.0 into HEAD again (This used to be commit bca0bba209255d0effbae6a3d3b6d298f0952c3a) --- docs/faq/FAQ-Install.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/faq/FAQ-Install.html') diff --git a/docs/faq/FAQ-Install.html b/docs/faq/FAQ-Install.html index 0bb21ed543..c331922fdb 100644 --- a/docs/faq/FAQ-Install.html +++ b/docs/faq/FAQ-Install.html @@ -1,4 +1,4 @@ -Chapter 2. Compiling and installing Samba on a Unix host
Chapter 2. Compiling and installing Samba on a Unix host
Prev   Next

Chapter 2. Compiling and installing Samba on a Unix host

Table of Contents

My client reports "cannot locate specified share name" or similar
Why are my file's timestamps off by an hour, or by a few hours?

My client reports "cannot locate specified share name" or similar

+Chapter 2. Compiling and installing Samba on a Unix host

Chapter 2. Compiling and installing Samba on a Unix host
Prev   Next

Chapter 2. Compiling and installing Samba on a Unix host

Table of Contents

My client reports "cannot locate specified share name" or similar
Why are my file's timestamps off by an hour, or by a few hours?

My client reports "cannot locate specified share name" or similar

This message indicates that your client CAN locate the specified server, which is a good start, but that it cannot find a service of the name you gave. @@ -7,7 +7,7 @@ The first step is to check the exact name of the service you are trying to connect to (consult your system administrator). Assuming it exists and you specified it correctly (read your client's docs on how to specify a service name correctly), read on: -

Many clients cannot accept or use service names longer than eight characters.
Many clients cannot accept or use service names containing spaces.
Some servers (not Samba though) are case sensitive with service names.
Some clients force service names into upper case.

Why are my file's timestamps off by an hour, or by a few hours?

+

Many clients cannot accept or use service names longer than eight characters.
Many clients cannot accept or use service names containing spaces.
Some servers (not Samba though) are case sensitive with service names.
Some clients force service names into upper case.

Why are my file's timestamps off by an hour, or by a few hours?

This is from Paul Eggert eggert@twinsun.com.

Most likely it's a problem with your time zone settings. @@ -19,7 +19,7 @@ namely, the number of seconds since 1970-01-01 00:00:00 Universal Time On the server side, Samba uses the Unix TZ variable to convert internal timestamps to and from local time. So on the server side, there are two things to get right. -

The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.

+

The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.
The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.

TZ must have the correct value.

If possible, use geographical time zone settings (e.g. TZ='America/Los_Angeles' or perhaps -- cgit