when users ftp to server the timezone reflected is UTC but the server is set to TZ in localtime
Guys,
Need your help coz my server runs in local time GMT +8, but when client use ftp and login, the resulting timestamp seen in each file is in UTC format. We need to set that the time should be the same as GMT +8 when in ftp session.
I am using RHEL 5.3.
Hi
I have changed my timezone using the command
export TZ='Asia/Calcutta"
but teh affect is taking place only in teh shell where I am logged in. If I export teh variable when I open the new session, things are fine.
Can I affetct the change universally, without restarting the server.
... (2 Replies)
I've set up a FTP server (vsftpd) with some local user account and it works fine. Now i want to upgrade this FTP server with an ability that can authorize user through Active Directory. I do a search around our forum and it leads me to this page:
Native LDAP, native Kerberos and Windows Server... (0 Replies)
Hi,
I need to copy few files from remote server to local server.
I write a shell script to connect to the remote server using ftp and go to that path. Now i need to copy those files in the remote directory to my local server with the timestamp of all those files shouldnt be changed.
... (5 Replies)
Hi All,
I need your expertise in finding a way to solve my problem.Please excuse if this is not the right forum to ask this question and guide me to the correct forum,if possible.
I am a DBA and on a daily basis i have to ftp huge dump files from my company server to my laptop and then... (3 Replies)
There is a unix server where the time zone has been changed from EST to CST.Can we get any kind of log when it was changed anywhere in the unix machine. Also the path for the same.
If there is any other way to know this please let me know (3 Replies)
Hi All,
We are working on HP_UNIX.
I am facing a strange problem regarding crontab in our unix environment.Whenever a server reboot takes place on our server the old crontab gets reflected due to which several scripts which were earlier uncommented starts running causing a huge problem .Is... (6 Replies)
We have RHEL 5.8 in our environment, I had a query whether we can implement an FTP server using vsftpd package and Linux configurations like setsebool without using any external FTP clients like FileZilla etc. I am very confused on this. The FTP functionalities that should be present are download &... (3 Replies)
Discussion started by: RHCE
3 Replies
LEARN ABOUT OPENSOLARIS
dat_ia_close
dat_ia_close(3DAT) Direct Access Transport Library Functions dat_ia_close(3DAT)NAME
dat_ia_close - close an IA
SYNOPSIS
cc [ flag... ] file... -ldat [ library... ]
#include <dat/udat.h>
DAT_RETURN
dat_ia_close (
IN DAT_IA_HANDLE ia_handle,
IN DAT_CLOSE_FLAGS ia_flags
)
PARAMETERS
ia_handle Handle for an instance of a DAT IA.
ia_flags Flags for IA closure. Flag definitions are:
DAT_CLOSE_ABRUPT_FLAG Abrupt close. Abrupt cascading close of IA including all Consumer created DAT objects.
DAT_CLOSE_GRACEFUL_FLAG Graceful close. Closure is successful only if all DAT objects created by the Consumer have been
freed before the graceful closure call.
Default value of DAT_CLOSE_DEFAULT = DAT_CLOSE_ABRUPT_FLAG represents abrupt closure of IA.
DESCRIPTION
The dat_ia_close() function closes an IA (destroys an instance of the Interface Adapter).
The ia_flags specify whether the Consumer wants abrupt or graceful close.
The abrupt close does a phased, cascading destroy. All DAT Objects associated with an IA instance are destroyed. These include all the con-
nection oriented Objects: public and reserved Service Points; Endpoints, Connection Requests, LMRs (including lmr_contexts), RMRs (includ-
ing rmr_contexts), Event Dispatchers, CNOs, and Protection Zones. All the waiters on all CNOs, including the OS Wait Proxy Agents, are
unblocked with the DAT_HANDLE_NULL handle returns for an unblocking EVD. All direct waiters on all EVDs are also unblocked and return with
DAT_ABORT.
The graceful close does a destroy only if the Consumer has done a cleanup of all DAT objects created by the Consumer with the exception of
the asynchronous EVD. Otherwise, the operation does not destroy the IA instance and returns the DAT_INVALID_STATE.
If async EVD was created as part of the of dat_ia_open(3DAT), dat_ia_close() must destroy it. If async_evd_handle was passed in by the Con-
sumer at dat_ia_open(), this handle is not destroyed. This is applicable to both abrupt and graceful ia_flags values.
Because the Consumer did not create async EVD explicitly, the Consumer does not need to destroy it for graceful close to succeed.
RETURN VALUES
DAT_SUCCESS The operation was successful.
DAT_INSUFFICIENT_RESOURCES The operation failed due to resource limitations. This is a catastrophic error.
DAT_INVALID_HANDLE Invalid DAT handle; ia_handle is invalid.
DAT_INVALID_PARAMETER Invalid parameter; ia_flags is invalid.
DAT_INVALID_STATE Parameter in an invalid state. IA instance has Consumer-created objects associated with it.
USAGE
The dat_ia_close() function is the root cleanup method for the Provider, and, thus, all Objects.
Consumers are advised to explicitly destroy all Objects they created prior to closing the IA instance, but can use this function to clean
up everything associated with an open instance of IA. This allows the Consumer to clean up in case of errors.
Note that an abrupt close implies destruction of EVDs and CNOs. Just as with explicit destruction of an EVD or CNO, the Consumer should
take care to avoid a race condition where a Consumer ends up attempting to wait on an EVD or CNO that has just been deleted.
The techniques described in dat_cno_free(3DAT) and dat_evd_free(3DAT) can be used for these purposes.
If the Consumer desires to shut down the IA as quickly as possible, the Consumer can call dat_ia_close(abrupt) without unblocking CNO and
EVD waiters in an orderly fashion. There is a slight chance that an invalidated DAT handle will cause a memory fault for a waiter. But this
might be an acceptable behavior, especially if the Consumer is shutting down the process.
No provision is made for blocking on event completion or pulling events from queues.
This is the general cleanup and last resort method for Consumer recovery. An implementation must provide for successful completion under
all conditions, avoiding hidden resource leakage (dangling memory, zombie processes, and so on) eventually leading to a reboot of the oper-
ating system.
The dat_ia_close() function deletes all Objects that were created using the IA handle.
The dat_ia_close() function can decrement a reference count for the Provider Library that is incremented by dat_ia_open() to ensure that
the Provider Library cannot be removed when it is in use by a DAT Consumer.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard: uDAPL, 1.1, 1.2 |
+-----------------------------+-----------------------------+
|MT-Level |Unsafe |
+-----------------------------+-----------------------------+
SEE ALSO dat_cno_free(3DAT), dat_evd_free(3DAT), dat_ia_open(3DAT), libdat(3LIB), attributes(5)SunOS 5.11 16 Jul 2004 dat_ia_close(3DAT)