Keeping old Private Messages Post: 302236166

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Keeping the format ...

Hi all, Am trying to execute a loop but having some troubles... Files that will be query'd use the Julian date (eg: cpu032, cpu365) in their naming convention. I'm a little lost how to maintain the three character format of the numeric portion of the file name while cycling backwards(or...

2. IP Networking

private network to private network gateway

i have one private network with one ip address, and i have a seperate network on a seperate ip address. now, each network is behind a firewall/router. now what i want to do is be able to access one server on the second network from a computer on the first., but with the private ip address, (this...

3. Solaris

keeping a process alive ?

Hello guys, I have one script running that I need to keep it running 24x7 so I'd like to know how can I implement a sort of monitoring process I mean if for some reason this process dies somehow it gets automatically started again. Thanks.

4. Shell Programming and Scripting

Keeping last part

Hello, Sorry for the poor tilte but I still don't know how to this. Here is my problem. I have to huge log file. In this log file I can know where is stored all my files. As I have to get a reporting of of files I only need to keep the file name but I don't know how to do it. I hope you...

5. Shell Programming and Scripting

Replace date value with another value keeping all as is

Hi forum. How do I change the following date value with another value (while keeping the rest of the line) using sed? The date values can change so I need a general sed command to change the date value within the first quotation marks only. Date values will be coming from 2 different files....

6. Post Here to Contact Site Administrators and Moderators

Private messages

Hi, As i am recieving private messages, i am unable to reply to them. Could you please enable my private messages. Thanks!

7. UNIX for Dummies Questions & Answers

Replace some strings keeping others

I want to replace strings in test2 according to test1 table. In doing so, I`m losing records that I dont need to replace, please suggest modifications. what i have $ cat > test1 a b c d 　 $ cat > test2 a a a d d 　 what i tried $ awk ' BEGIN {FS=OFS=" "} FNR==NR{a=$2;next}...

8. What is on Your Mind?

Private Messages.

Well I have just noticed over the years that I have PMs that I have not seen or even known about. Apologies if any of you have not had any replies to your PMs. It is too late now as some go back to my early days on here. The notification that comes up currently has notified me of a couple...

LEARN ABOUT DEBIAN

fssync-debug_list

FSSYNC-DEBUG_LIST(8)					       AFS Command Reference					      FSSYNC-DEBUG_LIST(8)

NAME

       fssync-debug_list - Historical sync command (FSYNC_VOL_LISTVOLUMES opcode)

SYNOPSIS

       fssync-debug list -volumeid <volume ID>
	   [-partition <exact partition name>]
	   [-reason <sync protocol reason code>]
	   [-programtype <program type code>]
	   [-help]

       fssync-debug li -v <volume ID>
	   [-pa <exact partition name>]
	   [-r <sync protocol reason code>]
	   [-pr <program type code>]
	   [-h]

       fssync-debug ls -v <volume ID>
	   [-pa <exact partition name>]
	   [-r <sync protocol reason code>]
	   [-pr <program type code>]
	   [-h]

DESCRIPTION

       The fssync-debug list does nothing but return success, assuming the fileserver is available. The opcode it calls exists for historical
       reasons, and now does nothing.

OPTIONS

       -volumeid <volume ID>
	   Specifies the numeric volume ID. Volume names are not permitted.

       -partition <exact partition name>
	   Specifies the exact partition name (e.g. /vicepa). Abbreviations are not permitted.

       -reason <sync protocol reason code>
	   Specifies numeric sync protocol reason code.  Available codes are listed in OpenAFS source file src/vol/fssync_inline.h. For
	   SYNC_REASON_NONE, use -reason 0.

       -programtype <program type code>
	   Specifies program type code. Permitted values are fileServer, volumeUtility, salvager, salvageServer, volumeServer and volumeSalvager.

PRIVILEGE REQUIRED

       The issuer must have write access to the file server.  Usually, this means that the issuer must be the local superuser "root" on the file
       server machine.

SEE ALSO

       fssync-debug_header(8), fssync-debug_stats(8)

COPYRIGHT

       Copyright 2010 Davor Ocelic <docelic@spinlocksolutions.com>

       This documentation is covered by the IBM Public License Version 1.0.  This man page was written by Davor Ocelic for OpenAFS, based on
       documentation from Steven Jenkins, Tom Keiser and Simon Wilkinson.

OpenAFS 							    2012-03-26						      FSSYNC-DEBUG_LIST(8)