Losing the connection

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Losing Time

Our Unix system is losing a considerable amount of time each day, and our support service company says our motherboard is the cause. They "upgraded" us 5 years ago to basically the same thing as what we had previously, and are looking to "upgrade" us again now for about $5,000... I think...

2. Programming

Losing signal problem

I'm newbie in UNIX programming, I have a problem with signals. I'm writing multithread program, where threads can die at any moment. When thread dies it generates signal SIGUSR1 to main thread and then thread dies. Main thread gets a signal and waits for thread dead. I wrote program like this: ...

3. HP-UX

losing mail enroute

system is HP-UX B.11.23 U ia64 A standard feature of almost all of our cron jobs is to redirect output to a log file, then at the end of the script to embed the contents of that log file in the body of an email sent to the IT staff. Typical code to do this is $MAILER -s "$PROC: $SUBJECT"...

4. Emergency UNIX and Linux Support

losing ESSID

Hey guys, facing a weird issue - hoping someone might be able to help. The wireless network on my laptop is configured with a static IP address. (not using nm) When i take the laptop out of the range (or i power the router down) the essid is becoming "off/any". When i'm back in range the...

5. Shell Programming and Scripting

Losing quotes after redirection

Hello experts, Pleas I have written a shell script to build a parfile but I keep losing the quotes from query1 and query variables after the redirection.. How do I fix this ? PARFILE=${EXPDP_BASE}/expdp_${DAY}.par USERID=$(${ORACLE_BASE}/getpass.ksh SYSTEM opnlkp2.uk.ml.com)...

6. Solaris

Losing my solaris virginity

So here's the scoop. I am working on a project to automate the building of spark based solaris servers. I've got a cursory amount of knowledge of how to use the os after some pretty heavy experience with Linux, and doing a similar project there. I have a few questions though... 1) how is...

7. Solaris

Solaris 10 ftp connection problem (connection refused, connection timed out)

Hi everyone, I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the...

8. Shell Programming and Scripting

Losing zero in while read

I'm using a while read statement to read in lines from a file, if a value (for example) is 1000.10 in a field, the last zero is removed leaving 1000.1 does anyone know a way to keep the field as it is in the original file?

9. UNIX for Dummies Questions & Answers

Losing ownership with gzip

I'm trying to sell the use of gzip instead of compress in our department. One issue I'm having (which is a showstopper) is that I lose the ownership when gzipping and gunzipping, though it's mentioned all over the web that files are supposed to keep ownership. Example: -rwxrwxrwx 1 ms32345 ...

10. UNIX for Dummies Questions & Answers

losing time

Hi all, The server seems to be losing time, not a lot, but enough to be noticed. UNIX AIX 4.3.3 Any ideas, Kathy

LEARN ABOUT ULTRIX

lockd

lockd(8c) lockd(8c)

Name
lockd - network lock daemon

Syntax
/usr/etc/lockd [ -t timeout ] [ -g graceperiod ]

Description
The daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking service
makes this advisory locking support possible by using the system call and the subroutine. The daemon forwards lock requests for remote
data to the server site's lock daemon. The daemon then requests the status monitor daemon, for monitor service. The reply to the lock
request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.

If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.

When a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests. Client site daemons are noti-
fied by of the server recovery and promptly resubmit previously granted lock requests. If a client site's daemon fails to secure previ-
ously granted locks at the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
cannot reclaim them.

Options
-t timeout The daemon uses timeout (in seconds) as the interval instead of the default value of 15 seconds to retransmit a lock
request to the remote server.

-g graceperiod The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.

See Also
fcntl(2), lockf(3), signal(3), statd(8c)

lockd(8c)

Forum Support Area for Unregistered Users & Account Problems