SFDISK
Section: Linux Programmer's Manual (8)Updated: 1 September 1995
Index Return to Main Contents
NAME
sfdisk - Partition table manipulator for LinuxSYNOPSIS
sfdisk [options] devicesfdisk -s [partition]
DESCRIPTION
sfdisk has four (main) uses: list the size of a partition, list the partitions on a device, check the partitions on a device, and - very dangerous - repartition a device.sfdisk doesn't understand GUID Partition Table (GPT) and it is not designed for large partitions. In particular case use more advanced GNU parted(8).
List Sizes
sfdisk -s partition gives the size of partition in blocks. This may be useful in connection with programs like mkswap(8) or so. Here partition is usually something like /dev/hda1 or /dev/sdb12, but may also be an entire disk, like /dev/xda.-
% sfdisk -s /dev/hda9 81599 %
-
% sfdisk -s /dev/hda: 208896 /dev/hdb: 1025136 /dev/hdc: 1031063 /dev/sda: 8877895 /dev/sdb: 1758927 total: 12901917 blocks %
List Partitions
The second type of invocation: sfdisk -l [options] device will list the partitions on this device. If the device argument is omitted, the partitions on all hard disks are listed.% sfdisk -l /dev/hdc Disk /dev/hdc: 16 heads, 63 sectors, 2045 cylinders Units = cylinders of 516096 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls #blocks Id System /dev/hdc1 0+ 406 407- 205096+ 83 Linux native /dev/hdc2 407<PHONE_NUMBER>28 83 Linux native /dev/hdc3 814 2044 1231 620424 83 Linux native /dev/hdc4 0 - 0 0 0 Empty %The trailing - and + signs indicate that rounding has taken place, and that the actual value is slightly less (more). To see the exact values, ask for a listing with sectors as unit.
Check partitions
The third type of invocation: sfdisk -V device will apply various consistency checks to the partition tables on device. It prints `OK' or complains. The -V option can be used together with -l. In a shell script one might use sfdisk -V -q device which only returns a status.Create partitions
The fourth type of invocation: sfdisk device will cause sfdisk to read the specification for the desired partitioning of device from its standard input, and then to change the partition tables on that disk. Thus, it is possible to use sfdisk from a shell script. When sfdisk determines that its standard input is a terminal, it will be conversational; otherwise it will abort on any error.BE EXTREMELY CAREFUL - ONE TYPING MISTAKE AND ALL YOUR DATA IS LOST
As a precaution, one can save the sectors changed by sfdisk:
-
% sfdisk /dev/hdd -O hdd-partition-sectors.save ... %
Then, if you discover that you did something stupid before anything else has been written to disk, it may be possible to recover the old situation with
-
% sfdisk /dev/hdd -I hdd-partition-sectors.save %
(This is not the same as saving the old partition table: a readable version of the old partition table can be saved using the -d option. However, if you create logical partitions, the sectors describing them are located somewhere on disk, possibly on sectors that were not part of the partition table before. Thus, the information the -O option saves is not a binary version of the output of -d.)
There are many options.
OPTIONS
- -v or --version
- Print version number of sfdisk and exit immediately.
- -? or --help
- Print a usage message and exit immediately.
- -T or --list-types
- Print the recognized types (system Id's).
- -s or --show-size
- List the size of a partition.
- -g or --show-geometry
- List the kernel's idea of the geometry of the indicated disk(s).
- -G or --show-pt-geometry
- List the geometry of the indicated disks guessed by looking at the partition table.
- -l or --list
- List the partitions of a device.
- -d
-
Dump the partitions of a device in a format useful as input
to sfdisk. For example,
% sfdisk -d /dev/hda > hda.out % sfdisk /dev/hda < hda.out
will correct the bad last extended partition that the OS/2 fdisk creates. - -V or --verify
- Test whether partitions seem correct. (See above.)
- -i or --increment
- Number cylinders etc. starting from 1 instead of 0.
- -N number
-
Change only the single partition indicated. For example:
% sfdisk /dev/hdb -N5 ,,,* %
will make the fifth partition on /dev/hdb bootable (`active') and change nothing else. (Probably this fifth partition is called /dev/hdb5, but you are free to call it something else, like `/my_equipment/disks/2/5' or so). - -A number
- Make the indicated partition(s) active, and all others inactive.
- -c or --id number [Id]
-
If no Id argument given: print the partition Id of the indicated
partition. If an Id argument is present: change the type (Id) of
the indicated partition to the given value.
This option has the two very long forms --print-id and --change-id.
For example:
% sfdisk --print-id /dev/hdb 5 6 % sfdisk --change-id /dev/hdb 5 83 OK
first reports that /dev/hdb5 has Id 6, and then changes that into 83. - -uS or -uB or -uC or -uM
- Accept or report in units of sectors (blocks, cylinders, megabytes, respectively). The default is cylinders, at least when the geometry is known.
- -x or --show-extended
- Also list non-primary extended partitions on output, and expect descriptors for them on input.
- -C cylinders
- Specify the number of cylinders, possibly overriding what the kernel thinks.
- -H heads
- Specify the number of heads, possibly overriding what the kernel thinks.
- -S sectors
- Specify the number of sectors, possibly overriding what the kernel thinks.
- -f or --force
- Do what I say, even if it is stupid.
- -q or --quiet
- Suppress warning messages.
- -L or --Linux
- Do not complain about things irrelevant for Linux.
- -D or --DOS
- For DOS-compatibility: waste a little space. (More precisely: if a partition cannot contain sector 0, e.g. because that is the MBR of the device, or contains the partition table of an extended partition, then sfdisk would make it start the next sector. However, when this option is given it skips to the start of the next track, wasting for example 33 sectors (in case of 34 sectors/track), just like certain versions of DOS do.) Certain Disk Managers and boot loaders (such as OSBS, but not LILO or the OS/2 Boot Manager) also live in this empty space, so maybe you want this option if you use one.
- -E or --DOS-extended
- Take the starting sector numbers of "inner" extended partitions to be relative to the starting cylinder boundary of the outer one, (like some versions of DOS do) rather than to the starting sector (like Linux does). (The fact that there is a difference here means that one should always let extended partitions start at cylinder boundaries if DOS and Linux should interpret the partition table in the same way. Of course one can only know where cylinder boundaries are when one knows what geometry DOS will use for this disk.)
- --IBM or --leave-last
- Certain IBM diagnostic programs assume that they can use the last cylinder on a disk for disk-testing purposes. If you think you might ever run such programs, use this option to tell sfdisk that it should not allocate the last cylinder. Sometimes the last cylinder contains a bad sector table.
- -n
- Go through all the motions, but do not actually write to disk.
- -R
- Only execute the BLKRRPART ioctl (to make the kernel re-read the partition table). This can be useful for checking in advance that the final BLKRRPART will be successful, and also when you changed the partition table `by hand' (e.g., using dd from a backup). If the kernel complains (`device busy for revalidation (usage = 2)') then something still uses the device, and you still have to unmount some file system, or say swapoff to some swap partition.
- --no-reread
- When starting a repartitioning of a disk, sfdisk checks that this disk is not mounted, or in use as a swap device, and refuses to continue if it is. This option suppresses the test. (On the other hand, the -f option would force sfdisk to continue even when this test fails.)
- -O file
- Just before writing the new partition, output the sectors that are going to be overwritten to file (where hopefully file resides on another disk, or on a floppy).
- -I file
-
After destroying your filesystems with an unfortunate
sfdisk
command, you would have been able to restore the old situation
if only you had preserved it using the -O flag.
THEORY
Block 0 of a disk (the Master Boot Record) contains among other things four partition descriptors. The partitions described here are called primary partitions.
A partition descriptor has 6 fields:
- struct partition { unsigned char bootable; /* 0 or 0x80 */ hsc begin_hsc; unsigned char id; hsc end_hsc; unsigned int starting_sector; unsigned int nr_of_sectors; }
The two hsc fields indicate head, sector and cylinder of the begin and the end of the partition. Since each hsc field only takes 3 bytes, only 24 bits are available, which does not suffice for big disks (say > 8GB). In fact, due to the wasteful representation (that uses a byte for the number of heads, which is typically 16), problems already start with 0.5GB. However Linux does not use these fields, and problems can arise only at boot time, before Linux has been started. For more details, see the lilo documentation.
Each partition has a type, its `Id', and if this type is 5 or f (`extended partition') the starting sector of the partition again contains 4 partition descriptors. MSDOS only uses the first two of these: the first one an actual data partition, and the second one again an extended partition (or empty). In this way one gets a chain of extended partitions. Other operating systems have slightly different conventions. Linux also accepts type 85 as equivalent to 5 and f - this can be useful if one wants to have extended partitions under Linux past the 1024 cylinder boundary, without DOS FDISK hanging. (If there is no good reason, you should just use 5, which is understood by other systems.)
Partitions that are not primary or extended are called logical. Often, one cannot boot from logical partitions (because the process of finding them is more involved than just looking at the MBR). Note that of an extended partition only the Id and the start are used. There are various conventions about what to write in the other fields. One should not try to use extended partitions for data storage or swap.
INPUT FORMAT
sfdisk reads lines of the form- <start> <size> <id> <bootable> <c,h,s> <c,h,s>
Fields are separated by whitespace, or comma or semicolon possibly followed by whitespace; initial and trailing whitespace is ignored. Numbers can be octal, decimal or hexadecimal, decimal is default. When a field is absent or empty, a default value is used.
The <c,h,s> parts can (and probably should) be omitted - sfdisk computes them from <start> and <size> and the disk geometry as given by the kernel or specified using the -H, -S, -C flags.
Bootable is specified as [*|-], with as default not-bootable. (The value of this field is irrelevant for Linux - when Linux runs it has been booted already - but might play a role for certain boot loaders and for other operating systems. For example, when there are several primary DOS partitions, DOS assigns C: to the first among these that is bootable.)
Id is given in hex, without the 0x prefix, or is [E|S|L|X], where L (LINUX_NATIVE (83)) is the default, S is LINUX_SWAP (82), E is EXTENDED_PARTITION (5), and X is LINUX_EXTENDED (85).
The default value of start is the first nonassigned sector/cylinder/...
The default value of size is as much as possible (until next partition or end-of-disk).
However, for the four partitions inside an extended partition, the defaults are: Linux partition, Extended partition, Empty, Empty.
But when the -N option (change a single partition only) is given, the default for each field is its previous value.
EXAMPLE
The command-
sfdisk /dev/hdc << EOF 0,407 ,407 ; ; EOF
The command
-
sfdisk /dev/hdb << EOF ,3,L ,60,L ,19,S ,,E ,130,L ,130,L ,130,L ,,L EOF
With the -x option, the number of input lines must be a multiple of 4: you have to list the two empty partitions that you never want using two blank lines. Without the -x option, you give one line for the partitions inside a extended partition, instead of four, and terminate with end-of-file (^D). (And sfdisk will assume that your input line represents the first of four, that the second one is extended, and the 3rd and 4th are empty.)
DOS 6.x WARNING
The DOS 6.x FORMAT command looks for some information in the first sector of the data area of the partition, and treats this information as more reliable than the information in the partition table. DOS FORMAT expects DOS FDISK to clear the first 512 bytes of the data area of a partition whenever a size change occurs. DOS FORMAT will look at this extra information even if the /U flag is given -- we consider this a bug in DOS FORMAT and DOS FDISK.
The bottom line is that if you use sfdisk to change the size of a DOS partition table entry, then you must also use dd to zero the first 512 bytes of that partition before using DOS FORMAT to format the partition. For example, if you were using sfdisk to make a DOS partition table entry for /dev/hda1, then (after exiting sfdisk and rebooting Linux so that the partition table information is valid) you would use the command "dd if=/dev/zero of=/dev/hda1 bs=512 count=1" to zero the first 512 bytes of the partition. BE EXTREMELY CAREFUL if you use the dd command, since a small typo can make all of the data on your disk useless.
For best results, you should always use an OS-specific partition table program. For example, you should make DOS partitions with the DOS FDISK program and Linux partitions with the Linux sfdisk program.
DRDOS WARNINGS
Stephen Tweedie reported (930515): `Most reports of superblock corruption turn out to be due to bad partitioning, with one filesystem overrunning the start of the next and corrupting its superblock. I have even had this problem with the supposedly-reliable DRDOS. This was quite possibly due to DRDOS-6.0's FDISK command. Unless I created a blank track or cylinder between the DRDOS partition and the immediately following one, DRDOS would happily stamp all over the start of the next partition. Mind you, as long as I keep a little free disk space after any DRDOS partition, I don't have any other problems with the two coexisting on the one drive.'
A. V. Le Blanc writes in README.efdisk: `Dr. DOS 5.0 and 6.0 has been reported to have problems cooperating with Linux, and with this version of efdisk in particular. This efdisk sets the system type to hexadecimal 81. Dr. DOS seems to confuse this with hexadecimal 1, a DOS code. If you use Dr. DOS, use the efdisk command 't' to change the system code of any Linux partitions to some number less than hexadecimal 80; I suggest 41 and 42 for the moment.'
A. V. Le Blanc writes in his README.fdisk: `DR-DOS 5.0 and 6.0 are reported to have difficulties with partition ID codes of 80 or more. The Linux `fdisk' used to set the system type of new partitions to hexadecimal 81. DR-DOS seems to confuse this with hexadecimal 1, a DOS code. The values 82 for swap and 83 for file systems should not cause problems with DR-DOS. If they do, you may use the `fdisk' command `t' to change the system code of any Linux partitions to some number less than hexadecimal 80; I suggest 42 and 43 for the moment.'
In fact, it seems that only 4 bits are significant for the DRDOS FDISK, so that for example 11 and 21 are listed as DOS 2.0. However, DRDOS itself seems to use the full byte. I have not been able to reproduce any corruption with DRDOS or its fdisk.
BUGS
There are too many options.There is no support for non-DOS partition types.
SEE ALSO
cfdisk(8), fdisk(8), mkfs(8), parted(8), partprobe(8), kpartx(8)AVAILABILITY
The sfdisk command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
Index
- NAME
- SYNOPSIS
- DESCRIPTION
- OPTIONS
- THEORY
- INPUT FORMAT
- EXAMPLE
- DOS 6.x WARNING
- DRDOS WARNINGS
- BUGS
- SEE ALSO
- AVAILABILITY
This document was created by man2html, using the manual pages.
Time: 05:34:30 GMT, December 24, 2015


The above graph is imported from the Plotly example website. Many more examples are provided by Plotly that you can take advantage of in this exact same fashion. Also, examples in D3 or any other web platform will follow a similar structure.
Load this file in a code editor in order to make changes to it. Note the three trace
objects:
// Your Copy/Pasted D3 Template Code
// Primary challenge: Match data format between
// your ML output and the D3 Template.
// Remember data orientation, matrix shape, challenges, etc?
// console.log is crucial.
var trace0 = {
x: [0.92856462, 1.94539677, 0.99756869, 1.31619577],
y: [8.12142991, 15.34381235, 10.47206746, 25.57987969],
mode: 'markers',
type: 'scatter'
};
var trace1 = {
x: [-5.05045834, -0.42648231, -0.85394453, 3.01885035],
y: [6.60747099, 3.27017923, 5.29911288, 4.90037295],
mode: 'lines',
type: 'scatter'
};
var trace2 = {
x: [-3.39215112, -0.49927365, -3.27535284, -3.86280596],
y: [3.76286202, -0.34104423, -0.56915362, 10.2125288],
mode: 'lines+markers',
type: 'scatter'
};
var data = [trace0, trace1, trace2];
// timeout required so that page will have rendered before newPlot
// is called.
setTimeout( function(){Plotly.newPlot('plotlyPlot', data)}, 200);
You can see that the `x` and `y` values are defined within your website code here. It is a trivial step to update these values with real values that reflect whatever you are researching or reporting.
Modify the below graph to contain data samples from our data analysis: High Dimensional Coding Challenge.
Dynamic data can be loaded into a website in this fashion - and some incredible dynamic charts are available at:


{% extends "layout.html" %} {% block title %} Jeroen hobo {% endblock %} {% block body %}
The Hashemite Kingdom of Jordan, a sovereign Arab state in western Asia, on the East Bank of the Jordan River.
TravelThe Kingdom of Cambodia, a sovereign state located in the southern portion of the Indochina Peninsula in Southeast Asia
TravelThe Republic of Ecuador, a representative democratic republic in northwestern South America.
Travel


SPTUser Class Reference
| Inherits from | SPTJSONObjectBase : NSObject |
| Declared in | SPTUser.h |
Overview
This class represents a user on the Spotify service.
API Model: https://developer.spotify.com/web-api/object-model/#user-object-private
API Console: https://developer.spotify.com/web-api/console/user%20profiles/
Tasks
Properties
-
displayName
property -
canonicalUserName
property -
territory
property -
emailAddress
property -
uri
property -
sharingURL
property -
images
property -
smallestImage
property -
largestImage
property -
product
property -
followerCount
property
Request creation methods
-
+ createRequestForCurrentUserWithAccessToken:error:
-
+ requestCurrentUserWithAccessToken:callback:
-
+ requestUser:withAccessToken:callback:
Response parsing methods
Properties
canonicalUserName
The canonical user name of the user. Not necessarily appropriate for UI use.
@property (nonatomic, readonly, copy) NSString *canonicalUserName
Declared In
SPTUser.h
displayName
The full display name of the user.
@property (nonatomic, readonly, copy) NSString *displayName
Discussion
Will be nil
unless your session has been granted the
user-read-private
scope.
Declared In
SPTUser.h
emailAddress
The user’s email address.
@property (nonatomic, readonly, copy) NSString *emailAddress
Discussion
Will be nil
unless your session has been granted the
user-read-email
scope.
Declared In
SPTUser.h
followerCount
The number of followers this user has.
@property (nonatomic, readonly) long followerCount
Declared In
SPTUser.h
images
Returns a list of user images in various sizes, as SPTImage
objects.
@property (nonatomic, readonly, copy) NSArray *images
Discussion
Will be nil
unless your session has been granted the
user-read-private
scope.
Declared In
SPTUser.h
largestImage
Convenience method that returns the largest available user image.
@property (nonatomic, readonly) SPTImage *largestImage
Discussion
Will be nil
unless your session has been granted the
user-read-private
scope.
Declared In
SPTUser.h
product
The product of the user. For example, only Premium users can stream audio.
@property (nonatomic, readonly) SPTProduct product
Discussion
Will be SPTProductUnknown
unless your session has been granted the
user-read-private
scope.
Declared In
SPTUser.h
sharingURL
The HTTP open.spotify.com URL of the user.
@property (nonatomic, readonly, copy) NSURL *sharingURL
Declared In
SPTUser.h
smallestImage
Convenience method that returns the smallest available user image.
@property (nonatomic, readonly) SPTImage *smallestImage
Discussion
Will be nil
unless your session has been granted the
user-read-private
scope.
Declared In
SPTUser.h
Class Methods
createRequestForCurrentUserWithAccessToken:error:
Create a NSURLRequest for requesting the current user
+ (NSURLRequest *)createRequestForCurrentUserWithAccessToken:(NSString *)accessToken error:(NSError **)error
Parameters
- accessToken
An authenticated access token. Must be valid and authorized.
- error
An optional pointer to an
NSError
that will receive the error code if operation failed.
Discussion
See: https://developer.spotify.com/web-api/console/get-current-user/
Declared In
SPTUser.h
requestCurrentUserWithAccessToken:callback:
Request current user
+ (void)requestCurrentUserWithAccessToken:(NSString *)accessToken callback:(SPTRequestCallback)block
Parameters
- accessToken
An authenticated access token. Must be valid and authorized.
- block
The block to be called when the operation is complete. The block will pass a Spotify SDK metadata object on success, otherwise an error.
Discussion
See: https://developer.spotify.com/web-api/console/get-current-user/
Declared In
SPTUser.h
requestUser:withAccessToken:callback:
Request a user profile
+ (void)requestUser:(NSString *)username withAccessToken:(NSString *)accessToken callback:(SPTRequestCallback)block
Parameters
- username
The username of the user to request
- accessToken
An authenticated access token that must be valid and authorized.
- block
The block to be called when the operation is complete. The block will pass a Spotify SDK metadata object on success, otherwise an error.
Discussion
See: https://developer.spotify.com/web-api/console/get-users-profile/
Declared In
SPTUser.h
userFromData:withResponse:error:
Convert a HTTP response into a SPTUser object
+ (instancetype)userFromData:(NSData *)data withResponse:(NSURLResponse *)response error:(NSError **)error
Parameters
- data
The response body
- response
The response headers
- error
An optional pointer to an
NSError
that will receive the error code if operation failed.
Discussion
See: https://developer.spotify.com/web-api/object-model/#user-object-private and https://developer.spotify.com/web-api/object-model/#user-object-public
Declared In
SPTUser.h
userFromDecodedJSON:error:
Convert a decoded response into a SPTUser object
+ (instancetype)userFromDecodedJSON:(id)decodedObject error:(NSError **)error
Parameters
- decodedObject
The decoded JSON object structure.
- error
An optional pointer to an
NSError
that will receive the error code if operation failed.
Discussion
See: https://developer.spotify.com/web-api/object-model/#user-object-private and https://developer.spotify.com/web-api/object-model/#user-object-public
Declared In
SPTUser.h


Real-Time AI-Based Ad Insertion with VCAC-A
AI-Based Ad Insertion
Mode:
Object Detection
Model:
MobileNet SSD
Precision:
FP16
Channels:
24
OpenVisualCloud Software Stack


Set the height of the table (in px)
For fixed height tables the header theme will be inferred if none is selected.
(Note: Deselecting all columns will default to all columns being showed.)
TableComponent
The table component needs both rows
and headerList
to display the data. Given the following simple
example of raw data
:
const data: any[] = {{ rawDataNotesExample | json }}
If we wish to display a table with the columns country
and currency
, the headerList
for
it would look like this:
The code above renders this table:
TableComponent
with TableService
The above example is good enough for displaying simple static tables. However if we wish to handle common features with tables
such as sorting, pagintion and selection we can use the TableService
which handles the logic for that and returns
the values we should pass to the table component. So using the above example, instead of creating our own
headerList
we could use the TableService
instead which generates one based on the data being
registered.
So let's try to get the same table to render but using the TableService
instead.
This example would render the same table as the Basic example.
To below example shows how to enable sorting on the same table as above.


| Up | TOC | Index | |||||
| << 8 API Reference | < 9.2 Version 4.0.6 Date TBD | Up: 9 Release Notes | 9.4 Version 4.0.4 April 4, 2012 > | 10 Index >> |
9.3 Version 4.0.5 October 19, 2012
9.3.1 Bug Fixes
- ticket:777 When invalid input is sent to 'match' or 'find' the error includes 'match' or 'find' in the error message repectively.
- ticket:749 Fix init checks for while-entry and goto
- ticket:563 Default values for arguments are always parsed and resolved as though they were being evaluated from the point of the routine declaration, not the point where the routine is called
- ticket:763 In some cases, the translator did not keep potential routine_id targets when dynamic routine names were used
- ticket:665 documented minimal requirements for various features in EUPHORIA on various platforms.
- ticket:665 set minimal version for Windows in its installer to avoid installing on computers that it wont work on.
- ticket:767 translated insert() could segfault when inserting an atom stored as an integer
- ticket:744 Duplicate case values in a switch block no longer result in a failed compile after being translated to C.
- ticket:775 Fixed potential memory leak when a temp is passed to one of the native type check functions: integer(), atom(), object() or sequence()
- ticket:778 Translator keeps forward referenced routine_id routines in include files
- ticket:789 Make parser read Windows eols the same as unix eols on Linux.
- ticket:795 Corrected std/serialize.e to call define_c_proc correctly
- ticket:795 Corrected std/net/http.e to call do a case insensitive search for 'content-length'
- ticket:796 when binding and translating use different EXE names
- Fixed memory leak in translator when calls to head() result in an empty sequence
9.3.2 Enhancements
- ticket:768 Backported support for deserializing 8-byte integers and 10-byte floating point.
- Optimization of std/map.e remove() to prevent unnecessary copy on write
- ticket:787 Document cases where you pass an empty sequence into search routines


Season’s Greetings from Strike Debt!
The Rolling Jubilee has struck a chord around the country and the world, giving rise to a remarkable outpouring of goodwill and support. The fund has exceeded our wildest expectations. We set out with the goal of raising $50,000 in order to abolish approximately 1 million dollars worth of debt. Thanks to your generosity, we have thus far raised over ten thousand donations at an average of forty dollars each, totaling $480,000. This is enough to abolish nearly ten million dollars worth of debt.
Along with donations to the fund, we have also been overwhelmed with both letters of support and devastating stories of how the predatory debt-economy impacts people’s lives. We are at a moment when these individual experiences of grief and suffering–shared by millions around the country–are beginning to translate into a collective political consciousness about the immorality of the debt-system overall.
At the cost of $5,000 dollars, we have now successfully eliminated $100,000 of debt owed to creditors who profit from people’s sickness and suffering. Letters to 44 debtors will be delivered in specially wrapped holiday packages, designed to catch the eye and pique the curiosity of recipients. Nick Pinto has the story in the Village Voice.
The debtors whose debts have been abolished have been given our contact information and information about Strike Debt and the Rolling Jubilee. If any decide to come forward and share their stories publicly, we will let the world know.
The Rolling Jubilee is only one tactic in a broad campaign against the debt system. On Dec. 16, Strike Debt held an Open House to welcome new and old friends into the debt resistance movement. Here are some photos from the Open House, the first in a series of events to be held each month in NYC.
For more information about our latest debt purchase, here is the redacted agreement documenting our Nov. 12 debt purchase, and here is a sample of the letter we sent to each debtor.
We are currently doing our due diligence as we are learn the ins and outs of the debt buying market. In the coming months, we hope to announce a bigger buy in coordination with a report on the role of debt in our dysfunctional healthcare system. We will also be holding a portion of the ever-growing Rolling Jubilee fund in strategic reserve for future debt-buying projects as we continue to learn more about the possibilities of the market.
Follow us on Facebook and Twitter and sign up for our mailing list to stay in touch.
With love and gratitude,


ABOUT ME
I am not quite sure where to start with this. so I just decided to go with education first.
.....I went to VA Westren Community College for a while. Acumulated some credits, but did not graduate.
Went to WOZ-U through Southern Careers Institute 2018-2019, got a Diploma in Software Development. Future plans are to
go to CSU Global starting Dec 9, 2019. First in a certificate program then to get a bachlors in Computer Science
.....Personally...I have two sons and two dogs. An ex-husband I stay in touch with. A mom and dad. 3 sisters and a brother.
.....Hobbies....Hummm.....I dont know that I have any any more. I love to cook, rarley take the time to do it well any more though. I used to paint pictures, nothing fancy, just mountians and trees.
.....Reckon I should tell you about work. I am a residential and comercial painter. Have been For 16 yrs. Before that,
to many things to list. Just to say I can do a little bit of a number of things.


After this window loads, click on a different application. The application icon will bounce five seconds after launch.


Choosing the best way to start a business will make it easier for you to become a successful entrepreneur.


--- layout: post title: And the Winners Are... date: 2011-02-18 09:00:15.000000000 -05:00 categories: - Giveaways tags: - Giveaway winners status: publish type: post published: true meta: aktt_notify_twitter: 'no' _edit_last: '1' _wp_old_slug: '' dsq_thread_id: '1188585628' author: login: cint email<EMAIL_ADDRESS>display_name: Jacinta first_name: Jacinta last_name: '' ---
Christy, you have won the All You Need Is Love Giveaway!
Tamara, you have won the Pinky McKay Baby Massage DVD Giveaway!
Congratulations to you both. I will contact you both by email to claim your prize. Jacinta


We will call our blogging application flaskr here, feel free to choose a less web-2.0-ish name ;) Basically we want it to do the following things:
We will be using SQLite3 directly for that application because it’s good enough for an application of that size. For larger applications however it makes a lot of sense to use SQLAlchemy that handles database connections in a more intelligent way, allows you to target different relational databases at once and more. You might also want to consider one of the popular NoSQL databases if your data is more suited for those.
Here a screenshot from the final application:
Continue with Step 0: Creating The Folders.


TOPCONS2
Main Menu
New query
SCAMPI
OCTOPUS
ΔG-scale
ZPRED
PRO/PRODIV
Download
Help
Paste your sequences in
FASTA
format:
{% csrf_token %} {{form.as_p}}
Restrainment options
Restrain parts of the sequence to a known Inside/Outside/Membrane location
N-term
inside (cytoplasmic)
outside (non-cytoplasmic)
(optional)
C-term
Inside (cytoplasmic)
Outside (non-cytoplasmic)
(Optional)
Other
(Optional)
String of one or more entries with format [first]-[last]-[label]; where [first] is first residue and [last] is last residue in restrained range, and [label] is i (Inside), o (Outside) or M (Membrane). Example: 1-1-o;20-25-M;
© 2015 Science for Life Laboratory, Stockholm


Getting Started with IBM Spectrum LSF (lsf_quick_admin.html)
[ Top ]
About LSF Cluster labkdd
[ Top ]
Cluster Characteristics
Cluster name and properties
Your cluster
labkdd
was installed according to the installation options specified by:lsfinstall -f /home/bayudwiyansatria/lsfsce<IP_ADDRESS>-x86_64/lsf/lsf10.1_lsfinstall/install.config
- LSF installed by user: root
lsfinstall
directory:/home/bayudwiyansatria/lsfsce<IP_ADDRESS>-x86_64/lsf/lsf10.1_lsfinstall
- LSF installation options file:
/home/bayudwiyansatria/lsfsce<IP_ADDRESS>-x86_64/lsf/lsf10.1_lsfinstall/install.config
- Installation log:
/home/bayudwiyansatria/lsfsce<IP_ADDRESS>-x86_64/lsf/lsf10.1_lsfinstall/Install.log
- Cluster name: labkdd
- Top-level LSF installation directory:
/usr/share/lsf
- Current LSF version: 10.1
- Primary LSF cluster administrator: lsfadmin
- Daemon management by EGO: Y
"Y" means that EGO Service Controller will manage LSF res and sbatchd.
"N" means that LSF res and sbatchd are started manually.
- Dynamic hosts: Y
"Y" means that you can add or remove cluster hosts dynamically.
LSF hosts
- Host types installed in LSF cluster
labkdd
:linux2.6-glibc2.3-x86_64
These hosts are listed in the
Hosts
section of/usr/share/lsf/conf/lsf.cluster.labkdd
.- LSF master host: blade1-node
- LSF master host and master candidates (all automatically become EGO management hosts):
blade1-node
- Server hosts defined in LSF cluster
labkdd
:blade1-node blade2-node
LSF server hosts defined in your cluster are indicated by 1 in the server column of the Hosts section of
/usr/share/lsf/conf/lsf.cluster.labkdd
.- Client-only hosts defined in LSF cluster
labkdd
:NONE
LSF client-only hosts are indicated by
0
(zero) in the server column of the Hosts section of/usr/share/lsf/conf/lsf.cluster.labkdd
.[ Top ]
LSF Directories and Configuration Files
- Four important LSF configuration files
- LSF directories
- LSF cluster configuration files
- LSF Batch configuration files
- Daemon log files
Four important LSF configuration files
LSF configuration is administered through several configuration files, which you use to modify the behavior of your cluster. The four most important files you will work with most often are:
/usr/share/lsf/conf/lsf.conf
/usr/share/lsf/conf/lsf.cluster.labkdd
/usr/share/lsf/conf/lsf.shared
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
These files are created during LSF installation according to the options you specified in the
/usr/share/lsf/10.1/install/install.config
file. After installation, you can change the configuration parameters in these files to suit the needs of your site; if the LSF parameters you configure have matching parameters in the equivalent EGO file, make sure the values are the same in both files. These are the equivalent EGO files:
These files are owned by the primary LSF administrator (lsfadmin), and readable by all cluster users.
The most important file in LSF. It contains the paths to the LSF configuration directories, log directories, libraries and other global configuration information. The location of
lsf.conf
is defined by the LSF_ENVDIR variable. If LSF cannot find this file, it cannot start properly.lsf.cluster.cluster_name
Defines the host names, models, and types of all of the hosts in the cluster. It also defines the user names of the LSF administrators, and the locations of different shared resources for one LSF cluster.
This file is like a dictionary that defines all the keywords used by the LSF cluster. You can add your own keywords to specify the names of resources or host types.
Defines the LSF batch queues and their parameters for one LSF cluster.
LSF directories
The following directories are owned by the primary LSF administrator (lsfadmin) and are readable by all cluster users:
- LSF_CONFDIR--LSF configuration directory:
/usr/share/lsf/conf- LSB_CONFDIR--LSF Batch configuration directory:
/usr/share/lsf/conf/lsbatch- LSB_SHAREDIR--LSF Batch job history directory:
/usr/share/lsf/work- LSF_LOGDIR--Server daemon error logs, one for each LSF daemon:
/usr/share/lsf/logThe following directories are owned by root and are readable by all cluster users:
- LSF_BINDIR--LSF user commands, shared by all hosts of the same type. For example:
/usr/share/lsf/10.1/sparc-sol10/bin/- LSF_INCLUDEDIR--Header files
lsf/lsf.h
andlsf/lsbatch.h
:/usr/share/lsf/10.1/include- LSF_LIBDIR--LSF libraries, shared by all hosts of the same type. For example:
/usr/share/lsf/10.1/sparc-sol10/lib/- LSF_MANDIR--LSF man pages:
/usr/share/lsf/10.1/man- LSF_MISC--Examples and other miscellaneous files:
/usr/share/lsf/10.1/misc- LSF_SERVERDIR--Server daemon binaries, scripts and other utilities, shared by all hosts of the same type. For example:
/usr/share/lsf/10.1/sparc-sol10/etc/- LSF_TOP--Top-level installation directory:
/usr/share/lsfOther configuration directories are specified in
/usr/share/lsf/conf/lsf.conf
.LSF cluster configuration files
The following files are owned by the primary LSF administrator (lsfadmin) and are readable by all cluster users:
- LSF global configuration files describing the configuration and operation of the cluster
labkdd
:
/usr/share/lsf/conf/ego/labkdd/kernel/ego.conf
/usr/share/lsf/conf/lsf.conf
- LSF keyword definition file shared by all clusters. Defines cluster name, host types, host models, and site-specific resources:
/usr/share/lsf/conf/lsf.shared
- LSF cluster configuration file that defines hosts, administrators, and location of site-defined shared resources:
/usr/share/lsf/conf/lsf.cluster.labkdd
- LSF mapping files for task names and their default resource requirements:
/usr/share/lsf/conf/lsf.task
/usr/share/lsf/conf/lsf.task.labkdd
LSF Batch configuration files
The following files are owned by the primary LSF administrator (lsfadmin) and are readable by all cluster users:
- LSF server hosts and their attributes, such as scheduling load thresholds, dispatch windows, and job slot limits:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.hosts
If no hosts are defined in this file, then all LSF server hosts listed in
/usr/share/lsf/conf/lsf.cluster.labkdd
are assumed to be LSF Batch server hosts.- LSF scheduler and resource broker plugin modules. If no scheduler or resource broker modules are configured, LSF uses the default scheduler plugin module named schmod_default:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.modules
- LSF Batch system parameter file:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.params
- LSF job queue definitions:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
- Resource allocation limits, exports, and resource usage limits:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.resources
- LSF user groups, hierarchical fairshare for users and user groups, and job slot limits for users and user groups:
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.users
Also used to configure account mappings in a MultiCluster environment.
- Application profiles, common parameters for the same type of jobs, including the execution requirements of the applications, the resources they require, and how they should be run and managed :
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.applications
This file is optional. Use the DEFAULT_APPLICATION parameter in
lsb.params
to specify a default application profile for all jobs. LSF does not automatically assign a default application profile.LSF Batch log files
- LSF Batch events log:
/usr/share/lsf/work/labkdd/logdir/lsb.events
- LSF Batch accounting log:
/usr/share/lsf/work/labkdd/logdir/lsb.acct
Daemon log files
LSF server daemon log files are stored in /usr/share/lsf/log:
- Load Information Manager (
lim
)
/usr/share/lsf/log/lim.log.host_name
- Remote Execution Server (
res
)
/usr/share/lsf/log/res.log.
host_name
- Master Batch Daemon (
mbatchd
)
/usr/share/lsf/log/mbatchd.log.blade1-node
- Master Scheduler Daemon (
mbschd
)
/usr/share/lsf/log/mbschd.log.blade1-node
- Slave Batch Daemon (
sbatchd
)
/usr/share/lsf/log/sbatchd.log.
host_name
- Process Information Manager (
pim
)
/usr/share/lsf/log/pim.log.host_name
Make sure that the primary LSF administrator (lsfadmin) owns the LSF log directory (/usr/share/lsf/log), and thatroot
can write to this directory. If an LSF server is unable to write to /usr/share/lsf/log, then the error logs are created in/tmp
.
[ Top ]
Working with LSF
[ Top ]
Starting, Stopping, and Reconfiguring LSF
- Two LSF administration commands (lsfadmin and badmin)
- Setting up the LSF environment (cshrc.lsf and profile.lsf)
- Start your cluster
- Stop your cluster
- Reconfigure your cluster
Two LSF administration commands (lsfadmin and badmin)
Only LSF administrators or root can run these commands.
To start and stop LSF, and to reconfigure LSF after making changes to any configuration file, you use two commands:
Setting up the LSF environment (cshrc.lsf and profile.lsf)
Before using LSF, you must set up the LSF execution environment.
After logging on to an LSF host, use one of the following shell environment files to set your LSF environment:
- For
csh
ortcsh
:%source /usr/share/lsf/conf/cshrc.lsf
- For
sh
,ksh
, orbash
:$. /usr/share/lsf/conf/profile.lsf
These two files are created by
lsfinstall
to set up the LSF operating environment.Start your cluster
You installed LSF as user root.
By default, only
root
can start LSF daemons. Iflsfinstall
detected you installed as non-root user, you chose to configure either a multi-user cluster or a single-user cluster:
- Multi-user--Only
root
can start LSF daemons. Any user can submit jobs to your cluster.See Troubleshooting LSF Problems for information about changing ownership and permissions for
lsadmin
andbadmin
.To permit LSF administrators to start and stop LSF daemons, set up
/etc/lsf.sudoers
, as described in Configuring LSF Startup.- Single-user--Your user account must be primary LSF administrator (lsfadmin). You are able to start LSF daemons, but only your user account can submit jobs to the cluster. Your user account must be able to read the system kernel information, such as
/dev/kmem
.Use
lsadmin
andbadmin
to start the LSF daemons.
- Log on as
root
to each LSF server host ( blade1-node blade2-node).If you installed a single-user cluster as a non-root user, log on as primary LSF administrator lsfadmin.
Start with the LSF master host blade1-node, and repeat these steps on all LSF hosts.
- Use the following commands to start the LSF cluster:
#lsadmin limstartup
#lsadmin resstartup
#badmin hstartup
Before using any LSF commands, wait a few minutes for
lim
on all hosts to do the following:Stop your cluster
Use
lsadmin
andbadmin
to stop the LSF daemons.
- Log on as
root
to any LSF server host ( blade1-node blade2-node).If you installed a single-user cluster as a non-root user, log on as primary LSF administrator lsfadmin.
- Use the following commands to stop the LSF cluster:
#badmin hshutdown all
#lsadmin resshutdown all
#lsadmin limshutdown all
Reconfigure your cluster
Use
lsadmin
andbadmin
to reconfigure LSF after making changes to any configuration file.
- Log on as
root
to any LSF server host ( blade1-node blade2-node).If you installed a single-user cluster as a non-root user, log on as primary LSF administrator lsfadmin.
- Use the following commands to reconfigure the LSF cluster:
This command also reads the/usr/share/lsf/work/labkdd/logdir/lsb.events
file, so it can take some time to complete if a lot of jobs are running.
[ Top ]
Checking LSF Status
- Example command output
- Check cluster configuration (lsadmin)
- Find out cluster status (lsid and lsload)
- Check LSF Batch configuration (badmin)
- Find out LSF Batch system status (bhosts and bqueues)
Example command output
The LSF commands shown in this section show examples of typical output. The output you see will differ according to your configuration.
The commands are described briefly so that you can easily use them as a "sanity check" for your LSF installation. You can use these commands on any LSF host.
If you get proper output from these commands, your cluster is ready to use. If your output from the commands discussed in this section has errors, see Troubleshooting LSF Problems or the LSF Command Reference for help.
Check cluster configuration (lsadmin)
lsadmin ckconfig -v
The
lsadmin
command controls the operation of an LSF cluster and administers the LSF daemons,lim
andres
. Use thelsadmin ckconfig
command to check the LSF configuration files. The-v
flag displays detailed information about the LSF configuration. For example:%lsadmin ckconfig -v
Checking configuration files ... EGO <IP_ADDRESS> build 88888, Feb 12 2016 Copyright IBM Corp. 1992, 2016. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. binary type: linux2.6-glibc2.3-x86_64 Reading configuration from /usr/share/lsf/conf/ego/labkdd/kernel/ego.conf Feb 13 10:31:32 2016 759460 6 3.4.0 Lim starting... Feb 13 10:31:32 2016 759460 6 3.4.0 LIM is running in advanced workload execution mode. Feb 13 10:31:32 2016 759460 6 3.4.0 Master LIM is not running in EGO_DISABLE_UNRESOLVABLE_HOST mode. Feb 13 10:31:32 2016 759460 5 3.4.0 /usr/share/lsf/10.1/linux2.6-glibc2.3-x86_64/etc/lim -C Feb 13 10:31:32 2016 759460 6 3.4.0 LIM is running as IBM Spectrum LSF Standard Edition. Feb 13 10:31:32 2016 759460 7 3.4.0 chuserId: setresuid/seteuid(0) failed, Operation not permitted. Feb 13 10:31:32 2016 759460 3 3.4.0 domanager(): /usr/share/lsf/conf/lsf.cluster.labkdd(15): The cluster manager is the invokerin debug mode Feb 13 10:31:32 2016 759460 6 3.4.0 reCheckClass: numhosts 1 so reset exchIntvl to 15.00 Feb 13 10:31:32 2016 759460 6 3.4.0 Checking Done. --------------------------------------------------------- No errors found. The messages shown above are typical output from
lsadmin ckconfig -v
. Other messages may indicate problems with your LSF configuration.Find out cluster status (lsid and lsload)
Tells you if your LSF environment is set up properly.
lsid
displays the current LSF version number (10.1), cluster name (labkdd
), and host name of the current LSF master host for your cluster (blade1-node).The LSF master name displayed by
lsid
may vary, but it is usually the first host configured in theHosts
section of/usr/share/lsf/conf/lsf.cluster.labkdd
. For example:%lsid
My cluster name islabkdd
My master name is blade1-nodeIf you see the message
Cannot open lsf.conf file
the LSF_ENVDIR environment variable is probably not set correctly. Use
/usr/share/lsf/conf/cshrc.lsf
or/usr/share/lsf/conf/profile.lsf
to set up your environment. See Top 10 LSF problems for additional help.Displays the current load levels of the cluster. The output contains one line for each host in the cluster. The status should be
ok
for all hosts in your cluster. For example:%lsload
HOST_NAME status r15s r1m r15m ut pg ls it tmp swp mem hostn ok 0.0 0.0 0.1 1% 0.0 1 224 43M 67M 3M hostk -ok 0.0 0.0 0.0 3% 0.0 3 0 38M 40M 7M hostg busy *6.2 6.9 9.5 85% 1.1 30 0 5M 400M 385M hostf busy 0.1 0.1 0.3 7% *17 6 0 9M 23M 28M hostv unavailA
busy
status is shown for hosts with any load index beyond its configured thresholds. An asterisk (*
) marks load indices that are beyond their thresholds, causing the host status to bebusy
. A minus sign (-
) in front of the valueok
means thatres
is not running on that host.If you see the message
lsid: getentitlementinfo() failed: LIM is down; try lateror
LSF daemon (LIM) not responding ... still tryingafter starting or reconfiguring LSF, wait a few seconds and try
lsload
again to givelim
on all hosts time to initialize. If the problem persists, see Top 10 LSF problems for help.
- The
lshosts
command displays configuration information for LSF hosts and their static resource information.- The
lsinfo
command displays cluster configuration information about resources, host types, and host models.Check LSF Batch configuration (badmin)
badmin ckconfig -v
The
badmin
command controls and monitors the operation of the LSF Batch system. Use thebadmin ckconfig
command to check the LSF Batch configuration files. The-v
flag displays detailed information about the configuration:%badmin ckconfig -v
Checking configuration files ... --------------------------------------------------------- No errors found.The messages shown above are typical output from
badmin ckconfig -v
. Other messages may indicate problems with the LSF Batch configuration.See Troubleshooting LSF Problems for help with some common configuration errors.
Find out LSF Batch system status (bhosts and bqueues)
To use LSF Batch commands, the cluster must be up and running. See Start your cluster for information about starting LSF daemons.
The
bhosts
command tells you if LSF Batch is running properly.bhosts
displays the status of LSF Batch server hosts in the cluster, and other details about the batch hosts:
- Maximum number of job slots allowed by a single user
- Total number of jobs in the system, jobs running, jobs suspended by users, and jobs suspended by the system
- Total number of reserved job slots
The status should be
ok
for all hosts in your cluster. For example:%bhosts
HOST_NAME STATUS JL/U MAX NJOBS RUN SSUSP USUSP RSV hosta ok - - 0 0 0 0 0 hostb ok - - 0 0 0 0 0 hostc ok - - 0 0 0 0 0 hostd ok - - 0 0 0 0 0If you see the message
batch system daemon not responding ... still trying
after starting or reconfiguring LSF, wait a few seconds and try
bhosts
again to givembatchd
time to initialize. If the problem persists, see Top 10 LSF problems for help.LSF Batch queues organize jobs with different priorities and different scheduling policies.
The
bqueues
command displays the status of available queues and their configuration parameters.  Several queues are defined by default in/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
. Modify this file to add, delete, or change queues. See Managing Users, Hosts, and Queues for more information about modifying queues.To see more detailed queue information, use
bqueues -l
:%bqueues -l normal
QUEUE: normal -- For normal low-priority jobs, This is the default queue.  The
bhist
command displays historical information about jobs.[ Top ]
Running LSF Jobs
- Commands for running LSF jobs (lsrun and bsub)
- Submit batch jobs (bsub)
- Display job status (bjobs)
- Control job execution (bstop, bresume, bkill)
- Run interactive tasks (lsrun and lsgrun)
- Integrate your applications with LSF
Commands for running LSF jobs (lsrun and bsub)
You use two basic commands to run jobs through LSF:
bsub
submits jobs to LSF Batch. LSF schedules and dispatches jobs to the best available host based on the scheduling policies you configure in your LSF queues.lsrun
runs an interactive task on the best available host, based on current system load information gathered bylim
.For most jobs, all you need to do is add either
lsrun
orbsub
in front of the job commands you normally use; there is usually no need to modify job executables or execution scripts.Submit batch jobs (bsub)
The
bsub
command submits jobs to LSF queues.The following command submits a
sleep
job to the default queue (normal
):%bsub sleep 60
Job <3616> is submitted to default queue <normal>.When a job is submitted to LSF, it is assigned a unique job ID, in this case
3616
.You can specify a wide range of job options on the
bsub
command. For example, you can specify a queue, and the job commandsleep
is the last option:%bsub -q short sleep 60
Job <3628> is submitted to queue <short>.By default, when the job is finished, LSF sends email with a job report and any output and error messages to the user account from which the job was submitted. You can optionally save standard output and standard error to files with the
-o
and-e
options:%bsub -q short -o /home/user1/jobs/output.%J -e /home/user1/jobs/errors.%J ls -l
Job <3640> is submitted to queue <short>.This command appends the standard output and standard error of the job to the files
output.3640
anderrors.3640
in thejobs
subdirectory of the home directory ofuser1
. The%J
variable in the command line is replaced by the job ID when the files are created, which helps keep track of job output when you run a lot of jobs.To submit an interactive job through LSF, use the
-I
option:%bsub -I ls
Submits a batch interactive job that displays the output of the
ls
command.To submit a batch interactive job by using a pseudo-terminal, use the
bsub -Ip
option. To submit a batch interactive job and create a pseudo-terminal with shell mode support, use thebsub -Is
option.Display job status (bjobs)
The status of each LSF job is updated periodically, and you can use the job ID to monitor and manipulate the job status.
The
bjobs
command displays the job ID and other job status. For example:%bjobs
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME 1266 user1 RUN normal hosta hostb sleep 60 Jun 5 17:39:58If all hosts are busy, the job is not started immediately and the
STAT
column saysPEND
. The jobsleep 60
should take 60 seconds to run. When the job completes, LSF sends email reporting the job completion.Control job execution (bstop, bresume, bkill)
To suspend a running job, use the
bstop
command and specify the job ID:%bstop 1266
Job <1266> is being stoppedIf the job was running when it was stopped, the
bjobs
command shows USUSP status for job1266
:%bjobs
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME 1266 user1 USUSP normal hosta hostb sleep 60 Jun 5 17:39:58Job owners can only suspend their own jobs. LSF administrators can suspend any job.
To resume a suspended job, use the
bresume
command.%bresume 1266
Job <1266> is being resumedIf the job resumes immediately. the
bjobs
command shows RUN status for job1266
:%bjobs
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME 1266 user1 RUN normal hosta hostb sleep 60 Jun 5 17:39:58Job owners can only resume their own jobs. LSF administrators can resume any job.
To kill a job, use the
bkill
command, which sends a signal to the specified jobs. For example, if the job owner or the LSF administrator runs the following command, job1266
is killed:%bkill 1266
Job <1266> is being terminatedRun interactive tasks (lsrun and lsgrun)
The
lsrun
command runs a task on either the current local host or remotely on the best available host, provided it can find the necessary resources and the appropriate host type.For example, the following command runs the UNIX
ls
command. In this case, the command ran through LSF on the local host:%lsrun ls -l /usr/share/lsf/conf
total 742 -rw-r--r-- 1 root lsf 11372 Jul 16 16:23 cshrc.lsf -rw-r--r-- 1 root lsf 365 Oct 25 10:55 hosts drwxr-xr-x 3 lsfadmin lsf 512 Jul 16 15:53 lsbatch -rw-r--r-- 1 lsfadmin lsf 1776 Nov 23 15:13 lsf.conf -rw-r--r-- 1 lsfadmin lsf 8453 Nov 16 17:46 lsf.shared -rw-r--r-- 1 lsfadmin lsf 578 Jul 16 15:53 lsf.task -rw-r--r-- 1 root lsf 10485 Jul 16 17:08 profile.lsfYou can also specify a host where you want to run a command. For example, the following command runs the UNIX
hostname
command on the remote hosthosta
:%lsrun -v -m hosta hostname
<<Execute hostname on remote host hosta>> hostaThe
lsgrun
command is similar tolsrun
, but it runs a task on a group of hosts.For example, the following command runs the UNIX
hostname
command on three remote hosts:%lsgrun -v -m "hosta hostb hostc" hostname
<<Executing hostname on hosta>> hosta <<Executing hostname on hostb>> hostb <<Executing hostname on hostc>> hostcIntegrate your applications with LSF
By integrating your applications with LSF, you can assure your users correct and complete job submission and execution without requiring them to learn LSF commands. There are three basic ways to integrate applications with LSF:
- Wrapper shell scripts
- Wrapper binary executables
- Modifying existing application source code and interfaces
The easiest integration method is to put the
bsub
command into an executable file like a shell script. A wrapper script is an executable file for launching your application through LSF. It gives users a simple interface to run their jobs that is easy to deploy and maintain.For example, if your application is called
abc
, renameabc
toabc_real
and create a wrapper script calledabc
, like this:#! /bin/sh bsub -R "rusage[abc_res=1:duration=1]" abc_realWhen users run
abc
, they are actually running a script to submit a jobabc_real
to LSF using 1 shared resource namedabc_res
.By adding appropriate options to the script, you can enhance your integration to:
- Requeue jobs based on resource availability
- Copy input and output files to and from the local directory on the execution host
- Calculate and estimate resource requirements
A wrapper binary is similar to a wrapper shell script in the form of a compiled binary executable. Compiled wrapper binaries usually run faster and more efficiently than shell scripts, and they also have access to the LSF API (LSLIB and LSBLIB). Binary code is also more secure because users cannot modify it without the source code and appropriate libraries, but it is more time consuming to develop wrapper binary programs than wrapper shell scripts.
LSF is already integrated closely with many commonly used software products. IBM and other software application vendors provide facilities and services for closer integration of LSF and other applications. By modifying existing application user interfaces, you can enable easy job submission, parallel execution, and other advanced LSF features. In some cases, you are able to run an LSF job directly from the application user interface.
We can work with you to discuss your specific application integration requirements. Contact your application vendor or IBM for more information.
[ Top ]
Managing Your Cluster
[ Top ]
Managing Users, Hosts, and Queues
- Make your cluster available to users (cshrc.lsf and profile.lsf)
- Add a host to your cluster
- Remove a host from your cluster
- Add a queue
- Remove a queue
Make your cluster available to users (cshrc.lsf and profile.lsf)
To set up the LSF environment for your users, use the following two shell files:
/usr/share/lsf/conf/cshrc.lsf
(forcsh
,tcsh
)/usr/share/lsf/conf/profile.lsf
(forsh
,ksh
, orbash
)Make sure all LSF users include one of these files at the end of their own
.cshrc
or.profile
file, or run one of these two files before using LSF.Add
/usr/share/lsf/conf/cshrc.lsf
to the end of the.cshrc
file for all users:OR
Add
/usr/share/lsf/conf/profile.lsf
to the end of the.profile
file for all users:OR
Add a host to your cluster
Adding a host to your cluster has the following major steps:
- Install LSF binaries for the host type.
- Add host Information to
lsf.cluster.labkdd
.- Set up the new host.
Make sure you have the LSF distribution files for the host types you want to add. For example, to add a Sun SPARC system running 64-bit Solaris 10 to your cluster, get the file
lsf10.1_sparc-sol10-64.tar.Z
.Distribution tar files for all supported LSF releases are available for download through the Online Support Web site or the FTP site.
Access to the download area of the Web site and the FTP site is controlled by login name and password.
See the Product Support site for a complete list of supported platforms.
Use
/usr/share/lsf/10.1/install/lsfinstall
to add new host types to your cluster. You can skip these steps if you already have the executables
- Log on as
root
to any host that can access the LSF install script directory/usr/share/lsf/10.1/install/
.- Change to the LSF install script directory.
#
cd /usr/share/lsf/10.1/install
- Edit
/usr/share/lsf/10.1/install/
install.config
to specify desired options for new host types.- Run
./lsfinstall -f
install.config
.- Follow the steps for host setup in "Completing Your IBM Spectrum LSF Installation" (
/home/bayudwiyansatria/lsfsce<IP_ADDRESS>-x86_64/lsf/lsf10.1_lsfinstall/lsf_getting_started.html
) to set up the new hosts.2 Add host Information to lsf.cluster.labkdd
- Log on to the LSF master host blade1-node as the primary LSF administrator lsfadmin.
- Edit
/usr/share/lsf/conf/lsf.cluster.labkdd
, and add host information for the new host to theHost
section:
- Add model or type.
If you enter the
!
keyword in themodel
andtype
columns, the host model is automatically detected bylim
running on the host.You may want to use the default values for that host type now, and change them later on when you have more experience or more information. This can be done without interrupting LSF service.
- Specify LSF server or client in the
server
column:By default, all hosts are considered LSF server hosts.
For example:
HOSTNAME model type server r1m mem RESOURCES REX PRI hosta ! SUNSOL6 1 1.0 4 () 0 hostb ! SUNSOL6 0 1.0 4 () 0 hostc ! HPPA1132 1 1.0 4 () 0 hostd ! HPPA1164 1 1.0 4 () 0 End Host- Save the changes to
lsf.cluster.labkdd
.- Reconfigure
lim
to enable the new host in the cluster:%lsadmin reconfig
Checking configuration files ... No errors found. Do you really want to restart LIMs on all hosts? [y/n]y
Restart LIM on <hosta> ...... done Restart LIM on <hostc> ...... done Restart LIM on <hostd> ...... doneThe
lsadmin reconfig
command checks for configuration errors.If no errors are found, you are asked to confirm that you want to restart
lim
on all hosts andlim
is reconfigured. If fatal errors are found, reconfiguration is aborted.- Reconfigure
mbatchd
:%badmin reconfig
Checking configuration files ... No errors found. Do you want to reconfigure? [y/n]y
Reconfiguration initiatedThe
badmin reconfig
command checks for configuration errors.If no fatal errors are found, you are asked to confirm reconfiguration. If fatal errors are found, reconfiguration is aborted.
- Log on as
root
to any host that can access the LSF install script directory/usr/share/lsf/10.1/install/
.- Change to the LSF install script directory.
#
cd /usr/share/lsf/10.1/install
- Run the
hostsetup
command to set up the new host.#
./hostsetup --top="/usr/share/lsf"
- Start LSF on the new host:
#lsadmin limstartup
#lsadmin resstartup
#badmin hstartup
Dynamic host configuration allows you to add hosts to the cluster without manually changing the LSF configuration.
Remove a host from your cluster
Never remove the master host from LSF. If you want to remove your current default master from LSF, change
lsf.cluster.
cluster_name to assign a different default master host. Then remove the host that was once the master host.
- Log on to the host as
root
or the primary LSF administrator lsfadmin.- Run
badmin hclose
to close the host. This prevents jobs from being dispatched to the host and allows running jobs to finish.- When all dispatched jobs are finished, run
lsfshutdown
to stop the LSF daemons on the host to be removed.- Edit
/usr/share/lsf/conf/lsf.cluster.labkdd
and remove the host from theHost
section.- Remove any other references to the host, if applicable, from the following LSF configuration files:
- Log off the host to be removed, and log on as
root
or the primary LSF administrator lsfadmin to any other host in the cluster.- Reconfigure
lim
:%lsadmin reconfig
Checking configuration files ... No errors found. Do you really want to restart LIMs on all hosts? [y/n]y
Restart LIM on <hosta> ...... done Restart LIM on <hostc> ...... doneThe
lsadmin reconfig
command checks for configuration errors.If no errors are found, you are asked to confirm that you want to restart
lim
on all hosts andlim
is reconfigured. If fatal errors are found, reconfiguration is aborted.- Reconfigure
mbatchd
:%badmin reconfig
Checking configuration files ... No errors found. Do you want to reconfigure? [y/n]y
Reconfiguration initiatedThe
badmin reconfig
command checks for configuration errors.If no fatal errors are found, you are asked to confirm reconfiguration. If fatal errors are found, reconfiguration is aborted.
- If you configured LSF daemons to start automatically as system startup, remove the LSF section from the host's system startup files. See Set up automatic LSF startup for details.
Dynamic host configuration allows you to remove hosts from the cluster without manually changing the LSF configuration.
Add a queue
Adding a queue does not affect pending or running jobs.
- Log on as the LSF administrator lsfadmin to any host in the cluster.
- Edit
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
to add the new queue definition.You can copy another queue definition from this file as a starting point; remember to change the
QUEUE_NAME
of the copied queue.- Save the changes to
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
.- Use the command
badmin ckconfig
to check the new queue definition.If any errors are reported, fix the problem and check the configuration again.
- When the configuration files are ready, reconfigure the cluster:
%badmin reconfig
Checking configuration files ... No errors found. Do you want to reconfigure? [y/n]y
Reconfiguration initiatedThe
badmin reconfig
command checks for configuration errors.If no fatal errors are found, you are asked to confirm reconfiguration. If fatal errors are found, reconfiguration is aborted.
Remove a queue
Before removing a queue, make sure there are no jobs in that queue.
Use the
bqueues
command to view a list of existing queues.If there are jobs in the queue, you must move pending and running jobs to another queue, then remove the queue.
If you remove a queue that has pending jobs in it, the jobs are temporarily moved to a
lost and found
queue. The job state does not change. Running jobs continue, and jobs pending in the original queue are pending in thelost and found
queue, and remain pending until the user or the LSF administrator lsfadmin uses thebswitch
command to switch the jobs into regular queues. Jobs in other queues are not affected.
- Log on to any host in the cluster as primary LSF administrator lsfadmin.
- Close the queue to prevent any new jobs from being submitted:
For example:
%badmin qclose night
Queue <night> is closed- Move all pending and running jobs into another queue.
For example, the
bswitch -q night
command below chooses jobs from thenight
queue, and the job ID number0
specifies that all jobs should be switched (job ID of0
matches all jobs):%bjobs -u all -q night
JOBID USER STAT QUEUE FROM_HOST EXEC_HOST JOB_NAME SUBMIT_TIME 5308 user5 RUN night hosta hostd job5 Nov 21 18:16 5310 user5 PEND night hosta hostc job10 Nov 21 18:17 %bswitch -q night idle 0
Job <5308> is switched to queue <idle> Job <5310> is switched to queue <idle>- Edit
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
and remove or comment out the definition for the queue being removed.- Save the changes to
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
.- Reconfigure the cluster:
%badmin reconfig
Checking configuration files ... No errors found. Do you want to reconfigure? [y/n]y
Reconfiguration initiatedThe
badmin reconfig
command checks for configuration errors.If no fatal errors are found, you are asked to confirm reconfiguration. If fatal errors are found, reconfiguration is aborted.
[ Top ]
Configuring LSF Startup
Allow LSF administrators to start LSF daemons (lsf.sudoers)
To allow LSF administrators (lsfadmin bayudwiyansatria) to start and stop LSF daemons, you should configure the
/etc/lsf.sudoers
file. Iflsf.sudoers
does not exist, onlyroot
can start and stop LSF daemons.
- Log on as
root
to each LSF server host ( blade1-node blade2-node).Start with the LSF master host blade1-node, and repeat these steps on all LSF hosts.
- Create
/etc/lsf.sudoers
on each LSF host and specify the LSF_STARTUP_USERS and LSF_STARTUP_PATH parameters. For example:LSF_STARTUP_USERS="lsfadmin bayudwiyansatria" LSF_STARTUP_PATH=/usr/share/lsf/10.1/sparc-sol10/etcLSF_STARTUP_PATH is normally LSF_SERVERDIR, where the LSF server binaries (
lim
,res
,sbatchd
,mbatchd
,mbschd
, etc.) are installed, as defined in your/usr/share/lsf/conf/lsf.conf
file.
lsf.sudoers
must have file permission mode-rw-------
(600) and be readable and writable only byroot
:#ls -la /etc/lsf.sudoers
-rw------- 1 root lsf 95 Nov 22 13:57 lsf.sudoers- Run
lsfrestart
to restart the cluster:#lsfrestart
Set up automatic LSF startup
Use the
boot=y
option ofhostsetup
to configure LSF daemons to start automatically on every LSF server host in the clusterlabkdd
.[ Top ]
[ Top ]
Troubleshooting LSF Problems
[ Top ]
Common LSF Problems
Finding LSF error logs
When something goes wrong, LSF server daemons log error messages in the LSF log directory (/usr/share/lsf/log).
Make sure that the primary LSF administrator (lsfadmin) owns /usr/share/lsf/log, and thatroot
can write to this directory. If an LSF server is unable to write to /usr/share/lsf/log, then the error logs are created in/tmp
.
LSF logs to the following files
/usr/share/lsf/log/vemkd.log.
blade1-node
/usr/share/lsf/log/lim.log.
host_name/usr/share/lsf/log/res.log.
host_name/usr/share/lsf/log/pim.log.
host_name/usr/share/lsf/log/
mbatchd
.log.blade1-node
/usr/share/lsf/log/mbschd.log.blade1-node
/usr/share/lsf/log/sbatchd.log.
host_nameIf there are any error messages in the log files that you do not understand, contact your LSF system engineer.
For most LSF problems
The general troubleshooting steps for most LSF problems are:
- Run
lsadmin ckconfig -v
and note any errors shown in the command output.Look for the error in Top 10 LSF problems. If none of these applies to your situation, contact Product Support.
- Use the following commands to restart the LSF cluster:
#lsadmin limrestart all
#lsadmin resrestart all
#badmin hrestart all
- Run
ps -ef
to see if the LSF daemons are running.Look for the processes similar to the following:
root 17426 1 0 13:30:40 ? 0:00 /usr/share/lsf/10.1/sparc-sol10/etc/lim root 17436 1 0 13:31:11 ? 0:00 /usr/share/lsf/10.1/sparc-sol10/etc/sbatchd root 17429 1 0 13:30:56 ? 0:00 /usr/share/lsf/10.1/sparc-sol10/etc/res- Check the LSF error logs on the first few hosts listed in the
Host
section of/usr/share/lsf/conf/lsf.cluster.labkdd
. If LSF_MASTER_LIST is defined in/usr/share/lsf/conf/lsf.conf
, check the error logs on the hosts listed in this parameter instead.Top 10 LSF problems
You might see this message running
lsid
. This means that/usr/share/lsf/conf/lsf.conf
is not accessible to LSF.By default, LSF checks the directory defined by LSF_ENVDIR
for
lsf.conf
. Iflsf.conf
is not in LSF_ENVDIR, LSF looks for it in/etc
.
- Make sure that there is either a symbolic link from
/etc/lsf.conf
to/usr/share/lsf/conf/lsf.conf
or
- Use
/usr/share/lsf/conf/csrhc.lsf
or/usr/share/lsf/conf/profile.lsf
to set up your LSF environment.Make sure that
/usr/share/lsf/conf/cshrc.lsf
or/usr/share/lsf/conf/profile.lsf
are available for users to set the LSF environment variables.See Setting up the LSF environment (cshrc.lsf and profile.lsf) for more information.
Sometimes
lim
is up, but thelsload
command displays one of the following error messages:
lsid: getentitlementinfo() failed: LIM is down; try later
LSF daemon (LIM) not responding ... still trying
ls_limcontrol: Communication time out
If
lim
has just been started, this is normal;lim
needs time to read configuration files and contactlim
daemons on other hosts. Iflim
does not respond within one or two minutes, check thelim
error log (/usr/share/lsf/log/lim.log.
host_name) for the host you are working on.When the local
lim
is running but there is no masterlim
in the cluster, LSF applications display the following message:Cannot locate master LIM now, try later.
lim
problems can have several causes. Check:
- The host is defined in the configuration files:
The host must be listed in the HOSTNAME column of the Host section in
/usr/share/lsf/conf/lsf.cluster.labkdd
- The LSF environment (LSF_ENVDIR) is set properly.
Use
cshrc.lsf
orprofile.lsf
to set the LSF environment on the host.- Ownership of the LSF files and directories.
The primary LSF administrator (lsfadmin) should own all LSF directories and most files. The LSF administration commands
lsadmin
andbadmin
must be owned byroot
and have the file permission mode-rwsr-xr- x
(user ID bit for the owner issetuid
).See problem 5 lsadmin or badmin fails for more information.
- The ports for
lim
andres
are not used by any other process, and are set correctly in one of:A common mistake is a typo in port names in
/usr/share/lsf/conf/lsf.conf
.The following ports are defined in
/usr/share/lsf/conf/lsf.conf
:The port numbers can be any numbers ranging from 1024 to 65535 that are not already used by other services. To make sure that the port numbers you supply are not already used by applications registered in your service database, check
/etc/services
.To change the port numbers:
After starting the LSF daemons, use the
ps
command to check that LSF is running on all LSF hosts, andmbatchd
is running on the master host.mbatchd
is started automatically bysbatchd
on the master host. You never need to startmbatchd
yourself.Before using any LSF commands, wait a few minutes
lim
on all hosts to do the following:Check the daemon error logs. Most common problems are:
- LSF service port conflicts:
Check that the ports for
lim
andres
are not used by any other process, and are set correctly in one of:and are not used by any other process.
A common mistake is a typo in port names in
/usr/share/lsf/conf/lsf.conf
.The following ports are defined in
/usr/share/lsf/conf/lsf.conf
:The port numbers can be any numbers ranging from 1024 to 65535 that are not already used by other services. To make sure that the port numbers you supply are not already used by applications registered in your service database, check
/etc/services
.To change the port numbers:
- Ownership of the LSF files and directories.
The primary LSF administrator (lsfadmin) should own all LSF directories and most files.
In particular,
/usr/share/lsf/work
must be owned and writable by the LSF primary administrator.The LSF administration commands
lsadmin
andbadmin
must be owned byroot
and have the file permission mode-rwsr-xr-x
(user ID bit for the owner issetuid
).See problem 5 lsadmin or badmin fails for more information.
The LSF administration commands
lsadmin
andbadmin
, or theeauth
executable might give the error messages like:Check the following:
- If you ran
lsfinstall
as root,lsfadmin
,badmin
, andeauth
have the file permission mode-rwsr-xr-x
(4755) so that the user ID bit for the owner issetuid
. However, on the file system where LSF was installed, setuid permission may be turned off. Do one of the following:
- If
lsadmin
,badmin
, andeauth
are in a directory shared through NFS, share and mount the LSF_TOP directory withsetuid
enabled. Do not mount with thenosuid
flag.- If your site does not permit this, you must copy
lsadmin
andbadmin
, andeauth
to a local directory on each host in the cluster. (make sure the local directory is in the PATH; for example,/usr/bin
or/bin
.)- If you ran
lsfinstall
as a non-root user to install a multi-user cluster, you must manually change the ownership forlsadmin
andbadmin
toroot
and the file permission mode to-rwsr-xr-x
(4755) so that the user ID bit for the owner issetuid
.Use the following commands to set the correct owner, user ID bit, and file permission mode for a multi-user cluster:
#chown root lsadmin badmin eauth
#chmod 4755 lsadmin badmin eauth
- You may also see these messages if you run the
bsub
command asroot
.By default, you cannot submit jobs with
bsub
asroot
. This is a normal security precaution. If you need to submit jobs asroot
, set LSF_ROOT_REX=local in/usr/share/lsf/conf/lsf.conf
.If you continue to see this message, it means that the remote host cannot securely determine the user ID of the user requesting remote execution.
Check:
- The messages in
/usr/share/lsf/log/res.log.
host_name on the execution host.res
is responsible for authenticating users in LSF- The setting of LSF authentication (LSF_AUTH in
/usr/share/lsf/conf/lsf.conf
):- That the
eauth
executable in LSF_SERVERDIR (for example, /usr/share/lsf/10.1/sparc-sol10/etc/eauth) is implemented correctly- That all LSF commands are owned by
root
and have the file permission mode to-rwsr-xr-x
so that the user ID bit for the owner issetuid
Many things can prevent jobs from starting. Check:
- Wait for up to a minute for LSF to dispatch your job. Some LSF activities happen periodically. You may be able to speed up job dispatch by changing the following parameters:
- Use
bjobs -p
and check the job pending reason.- Examine the output of
bhosts -l
for the load thresholds on the hosts andlsload -E
for the effective run queue lengths on the hosts.- Use
bqueues -l
to check the queue thresholds, host limits, and user limits.- If you submitted the jobs from a host that is the only host of its type in the cluster, by default, LSF tries to run the job on this host only. To run jobs on any available host type, submit the job with a command like:
%bsub -R "type==any" myjob
If none of these applies to your situation, contact Product Support.
6 LSF jobs go to a slow host while faster hosts are idle
Host processor speed is not the only factor in host selection:
- LSF uses the effective run queue lengths (displayed by
lsload -E
) to choose the least loaded execution hosts. Two hosts with the same effective run queue length are ordered according to their CPU factors.- By default, LSF runs jobs on hosts of the same type as the submission host. To run jobs on any available host type, submit the job with a command like:
%bsub -R "type==any" myjob
- The faster hosts may not be included in the queue where the job was submitted.
- The faster hosts may not have the resources required by the job.
- The faster hosts may be closed or have closed dispatch windows or closed run windows.
If none of these applies to your situation, contact Product Support.
7 Application runs fine under UNIX or with lsrun, but fails or hangs when submitted through bsub
On some UNIX systems, certain applications only run with specific limit values. Different limit values or no limits can cause problems for these applications.
lsrun
,lsgrun
and other interactive LSF commands copy the submission host environment, including any limits, to the execution host andres
sets the submission environment on the execution host.LSF Batch works differently. Jobs run in a queue, and are subject to queue limits, not submission host limits. By default, LSF Batch sets all limits to unlimited and only limits values explicitly set in the queue. To see the limit settings for your queues, use the command:
%bqueues -l -q
queue_nameTo troubleshoot this type of problem:
- Run the application under UNIX to confirm that it works without LSF.
- Create a small script like this:
#!/bin/sh # display limits from command line # Check the man pages for more limits that can be displayed ulimit -Hc ulimit -Hd ulimit -Sc ulimit -Sd- Run the script to determine the limits from the submission host under UNIX, and record the limit values.
- Create a new version of the script, setting the limit values reported by the original script and running the command for your application. For example:
#!/bin/sh # display limits from command line # Check the man pages for more limits that can be displayed ulimit -Hc 45333 ulimit -Hd 256 ulimit -Sc 24335 ulimit -Sd 256 <your application>You can also set these limits in a queue in
/usr/share/lsf/conf/lsbatch/labkdd/configdir/lsb.queues
.Once the limit values are set correctly, your application should run fine under LSF Batch. If it still does not work, contact Product Support.
8 LSF Batch job runs in /tmp or cannot find home directory
The problem could be caused by:
- Different home directories existing for the same user account on the submission and execution hosts
- NFS
automount
problems cause LSF to look for incorrect mount points- Permissions or ownership of your submission directory is incorrect for the home directory on the execution host
- You have a non-shared file system
A command may fail with the following error message due to a non-uniform file name space.
chdir(...) failed: no such file or directoryThis error means that you are trying to run a command remotely, and:
- Your current working directory does not exist on the remote host
If your current working directory does not exist on a remote host, you should not execute commands remotely on that host.
or
- Your current working directory is mapped to a different name on the remote host.
If the directory exists, but is mapped to a different name on the remote host, you must create symbolic links to make them consistent.
LSF can resolve most, but not all, problems using
automount
. The automount maps must be managed through NIS.9 Job is killed by some unknown signal or unknown reason
A job exit value smaller than 128 is the real exit value from your application.
If neither a user nor an LSF administrator kills the job, check if it was killed because it exceeded a resource usage limit:
- Use
bjobs -l
to check if any limit is specified on the job submission command.- Use
bqueues -l
to check if any limit is specified on the queue.- Use
bsub -q -I csh -c limit
to check if any other limit is set for the job.If none of these applies to your situation, contact Product Support.
[ Top ]
Get Technical Support
Contact IBM or your LSF vendor for technical support.
[ Top ]
Copyright
© 1994-2016 International Business Machines Corp
All rights reserved.


---
company: Net Nanny
subject: 7 Surprising Reasons for School Anxiety
date-month: August
date-year: 2016
date-vol: IV
tracking-ace: "&ace=----ACE_ID----"
tracking-campaign: "?pid=1-249&utm_source=newsletter&utm_medium=email&utm_campaign=201608newsletter4&utm_content="
url-webroot: "https://www.netnanny.com/"
url-blog: "https://www.netnanny.com/blog/"
url-blogasset: "https://www.netnanny.com/assets/blogimages/"
url-asset: "https://www.netnanny.com/assets/email/newsletter/"
blog: [{
"title": "Not Your Typical Back to School Tips",
"url": "https://www.netnanny.com/blog/not-your-traditional-back-to-school-tips/",
"image": "https://www.netnanny.com/assets/blogimages/201608notyourtypical.jpg",
"tracking": "?pid=1-249&utm_source=newsletter&utm_medium=email&utm_campaign=201608newsletter3&utm_content=20160810notyourtypical&ace=----ACE_ID----"
},
{
"title": "Motivate Your Teenager to Do School Work",
"url": "https://www.netnanny.com/blog/how-to-motivate-your/",
"image": "https://www.netnanny.com/assets/blogimages/201608motivateyourteenager.jpg",
"tracking": "?pid=1-249&utm_source=newsletter&utm_medium=email&utm_campaign=201608newsletter3&utm_content=201608motivateyourteen&ace=----ACE_ID----"
},
{
"title": "Rules for Cell Phone Use in Schools",
"url": "https://www.netnanny.com/blog/rules-for-cell-phone-use-in-school/",
"image": "https://www.netnanny.com/assets/blogimages/201608cellphonesinschool.jpg",
"tracking": "?pid=1-249&utm_source=newsletter&utm_medium=email&utm_campaign=201608newsletter3&utm_content=201608settingboundaries&ace=----ACE_ID----"
}
]
---
How to Ease the First Day of School Anxiety
The booklet includes actionable strategies on how your family can work together and with the school to reduce anxiety for your child.
{{ company }} in the News
First Time Parent Magazine featured Net Nanny in their ‘August Featured Products’ section this month. The article stated, "...to effectively cut the technology cord, parents can look to effective parental control products like Net Nanny, to cut screen time and limit the harmful side effects of issues like blue light exposure."
Family Matters
Here are 3 of our readers' top favorite blog posts.
{{#each blog}}
{{ this.title }}
{{/each}}
Set screen time limits to pause the internet during family dinners, sleep time, or when your family needs a tech time out.


SHOP NOW


The following sample PixieApp provides two simple views and their associated routes. The first view (default view) creates a button that, when clicked, will invoke the second view. The second view creates another button that redirects to the first view, and so on and so forth.
from pixiedust.display.app import *@PixieAppclass HelloWorldPixieApp: @route() def main(self): return""" <input pd_options="clicked=true" type="button" value="Click Me"> """ @route(clicked="true") def _clicked(self): return """ <input pd_options="clicked=false" type="button" value="You Clicked, Now Go back"> """#run the appHelloWorldPixieApp().run(runInDialog='false')


Start script
Starts a new script execution. If you identify a script with properties
scriptId
or scriptName
, then the latest version of that script will
be used. @see also Script versioning
Example
Here’s a startScript
example
> POST /command
Content-Type: application/json
{ "startScript" :
{ "scriptName" : "Submit order",
"input" : {
item: "Donuts",
quantity: 7
}
}
}
< HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
{ "scriptExecutionId": "se1" }
Request properties
| Property name | Required? | Type | Description |
|---|---|---|---|
scriptId |
One of scriptId or scriptName or scriptVersionId is required |
String | ID that identifies the script for which the latest version should be started |
scriptName |
One of scriptId or scriptName or scriptVersionId is required |
String | Name that identifies the script for which the latest version should be started |
scriptVersionId |
One of scriptId or scriptName or scriptVersionId is required |
String | The ID of the exact script version that should be started |
input |
Optional | Any json type | The system.input value. See also Language |
Response properties
| Property name | Data type | Description |
|---|---|---|
scriptExecutionId |
String | ID of the script execution |
Failures
The request returns a 400 BAD REQUEST
in the following situations
- The script for the given
scriptId
orscriptName
is not found - The script version for the given
scriptVersionId
is not found - No
scriptId
,scriptName
orscriptVersionId
are given - The specified script does not have an active script version yet. Fix this by using the
deployScript
instead of thesaveScript
command.
In each of these, a json body will be returned with an error message. For example
HTTP/1.1 400 BAD REQUEST
Content-Type: application/json
{ "message": "No script found with name UnexistingScript.rs" }


Welcome to Regular Expretion Validation application
Select option from bellow what you want to check...
Email Validation Check
Mobile No Validation Check
Postal Code Validation Check
URL Validation Check


Writing
- still working on non-parametric bayes draft today..
Reviewing
- review sent to PRSB
Reading
- Came across this rather nice summary of big data in Ecology through some buzz in the twittersphereHampton et. al. (2013) .
- More fishery managment controversy with Halpern et. al. (2013) critiquing the ‘ocean food provision index’ from Nature last year, and a subset of that team replying Halpern et. al. (2013) . Seems to fall along the usual divisions of whether to use or ignore imperfect data; no doubt the truth lies somewhere in between.
- Looks like Cavanaugh et. al. (2013) have a nice synchrony paper in kelp forests which I’m looking forward to reading.
- Nonlinear forecasting strikes again in PNAS, Deyle et. al. (2013) Predicting climate effects on sardine with the usual suspects. May disentangle physical forcing from ecological dynamics.
- Halpern et. al. (2013b) discuss the classic problem of optimization in conservation: balancing social equity, economic return and conservation needs.
ROpenSci is mentioned in a letter to the editor published in Ecotoxicology, (Schäfer et. al. 2013 ).
- Kyle C. Cavanaugh, Bruce E. Kendall, David A. Siegel, Daniel C. Reed, Filipe Alberto, Jorge Assis, (2013) Synchrony in Dynamics of Giant Kelp Forests is Driven by Both Local Recruitment And Regional Environmental Controls. Ecology 94 499-509 10.1890/12-0268.1
- E. R. Deyle, M. Fogarty, C.-h. Hsieh, L. Kaufman, A. D. MacCall, S. B. Munch, C. T. Perretti, H. Ye, G. Sugihara, (2013) Predicting Climate Effects on Pacific Sardine. Proceedings of The National Academy of Sciences 10.1073/pnas.1215506110
- Benjamin S. Halpern, Steven D. Gaines, Kristin Kleisner, Catherine Longo, Daniel Pauly, Andrew A. Rosenberg, Jameal F. Samhouri, Dirk Zeller, (2013) Halpern et al. Reply. Nature 495 E7-E7 10.1038/nature11975
- B. S. Halpern, C. J. Klein, C. J. Brown, M. Beger, H. S. Grantham, S. Mangubhai, M. Ruckelshaus, V. J. Tulloch, M. Watts, C. White, H. P. Possingham, (2013) Achieving The Triple Bottom Line in The Face of Inherent Trade-Offs Among Social Equity, Economic Return, And Conservation. Proceedings of The National Academy of Sciences 10.1073/pnas.1217689110
- Stephanie E Hampton, Carly A Strasser, Joshua J Tewksbury, Wendy K Gram, Amber E Budden, Archer L Batcheller, Clifford S Duke, John H Porter, (2013) Big Data And The Future of Ecology. Frontiers in Ecology And The Environment 11 156-162 10.1890/120103
Ralf B. Schäfer, Mirco Bundschuh, Andreas Focks, Peter C. von der Ohe, (2013) to The Editor. Environmental Toxicology And Chemistry 32 734-735 10.1002/etc.2140


SKILLS Digital Integrated Circuit Design PCB Design C Programming Power Electronics Embedded Systems MATLAB NGspice Altium Designer


8th-ranked Gonzaga men overwhelm North Dakota
by Seattle Times staffSPOKANE – Gonzaga had no video of North Dakota to study, so coach Mark Few said his staff improvised on the fly.
Filip Petrusev had 19 points, 15 rebounds and four blocked shots as the No. 8 Zags used a superior inside game to beat North Dakota 97-66 on Tuesday.
Gonzaga outscored the Fighting Hawks 64-32 in the paint.
“We feel it’s going to be one of our strengths this year,” said Few, citing the play of Petrusev, Drew Timme, Anton Watson and Corey Kispert.
Kispert scored 20 points, Timme had 16 and Watson added 15 for Gonzaga (3-0), which has won its games by a combined 112 points.
Marlon Stewart scored 21 points and Filip Rebraca had 16 points and 13 rebounds for North Dakota (1-1), which took the Zags to overtime before losing in Spokane in 2017.
No such thriller this time, as Gonzaga held the Fighting Hawks to 34.7% shooting and outrebounded them 53-29.
“Our low-post defense was really good,” Few said. “Filip had a good rebounding night. That’s a good, positive sign for us.”
The Zags figure to be even stronger inside when forward Killian Tillie returns from knee surgery.
Few didn’t provide much insight as to when that will occur, saying, “When he’s ready to play, he’ll play.”
The Zags are likely to face a more demanding test at Texas A&M on Friday.
“We’re excited to go down there,” Petrusev said. “It’s going to be tough down there.”
Gonzaga jumped to a 15-2 lead as North Dakota missed eight of its first nine shots.
Kispert and Admon Gilder each made three-pointers as Gonzaga built a 25-9 lead.
After North Dakota reduced the Zags’ lead to 30-21, Gonzaga responded with a 14-1 run.
The Zags shot 57.7% from the field.
“We really tried to get offensive rebounds and easy baskets,” Petrusev said.
North Dakota coach Paul Sather said, “We just have to rebound better. We started out a little nervous, but we responded well after the first timeout. We started competing, worrying less about who we were playing against.”
Seattle Times staff


Creating an Unit
Learn how to create a ComposingUnit ad the benefits of using it
What is a ComposingUnit?
It’s a simple protocol that puts together all info needed to display your data. You can make it a Struct
to deliver immutable and predictable data render, or you can use a Class
and make some dynamic behavior. Or you can mix them together.
So, to display some data, a ComposingUnit needs to answer 3 questions:
- What’s the identifier of this unit (so we can track and dynamically animate inserts and deletes)
- What is the dimension unit that represents it’s height and it’s width
- What is the reuse identifier that will be used to retrieve some UICollectionViewCell/UITableViewCell that will represent this unit.
and it also needs to know how to do these tasks:
- How to configure the view that represents this unit. (Once a view has been dequeued, the unit must know how to configure it)
- How to register a UICollectionViewCell (if this unit can be added to an UICollectionView)
- How to register a UITableViewCell (if this unit can be added to an UITableView)
So let’s create a simple unit that will display an empty view with a given color:
struct EmptyViewUnit {
let identifier: String
let backgroundColor: UIColor
let heightUnit: DimensionUnit
func configure(view: UIView) {
view.backgroundColor = backgroundColor
}
func reuseIdentifier()-> String {
return UICollectionViewCell.identifier()
}
func register(in collectionView: UICollectionView) {
UICollectionViewCell.register(in: collectionView)
}
}
let separator = EmptyViewUnit(identifier:"separator", backgroundColor: .red, height: 120)
As you can see, it’s really simple to define your own unit.
And because reuseIdentifier
and register(in:)
are methods, you could choose different views to display the same data.


[§269-44] Solar water heater system standards. Not later than July 1, 2009, or as soon as reasonably practicable, the public utilities commission shall adopt or establish by rule, tariff, or order, standards for solar water heater systems to include, but not be limited to, specifications for the performance, materials, components, durability, longevity, proper sizing, installation, and quality to promote the objectives of section 269-124. [L 2008, c 204, §3]
Cross References
Systems required for new single-family residential construction, see §196-6.5.


The ident authentication method works by obtaining the client's operating system user name from an ident server and using it as the allowed database user name (with an optional user name mapping). This is only supported on TCP/IP connections.
When ident is specified for a local (non-TCP/IP) connection, peer authentication (see Section 20.9) will be used instead.
The following configuration options are supported for ident:
map
Allows for mapping between system and database user names. See Section 20.2 for details.
The “Identification Protocol” is described in
RFC 1413. Virtually every Unix-like
operating system ships with an ident server that listens on TCP
port 113 by default. The basic functionality of an ident server
is to answer questions like “What user initiated the
connection that goes out of your port X
and connects to my port Y
?”.
Since PostgreSQL knows both X
and
Y
when a physical connection is established, it
can interrogate the ident server on the host of the connecting
client and can theoretically determine the operating system user
for any given connection.
The drawback of this procedure is that it depends on the integrity of the client: if the client machine is untrusted or compromised, an attacker could run just about any program on port 113 and return any user name they choose. This authentication method is therefore only appropriate for closed networks where each client machine is under tight control and where the database and system administrators operate in close contact. In other words, you must trust the machine running the ident server. Heed the warning:
|
The Identification Protocol is not intended as an authorization or access control protocol. |
||
| --RFC 1413 |
Some ident servers have a nonstandard option that causes the returned user name to be encrypted, using a key that only the originating machine's administrator knows. This option must not be used when using the ident server with PostgreSQL, since PostgreSQL does not have any way to decrypt the returned string to determine the actual user name.


-- No Effect --
{{ description }}
{{ gameConfig.code }}
{{ leftPlayer }}
{{ rightPlayer }}
Cards: {{ currentPack.length }}
(Export cards on the left)
Cards: {{ gameConfig.cards.length }}


--- layout: default title: ICSECT'19 - PayPal Payment Successful meta: Your payment has been successful! keyword: structural engineering, structural engineering conference 2019, building design, building design conference, prague, construction conference, construction management conference, structural dynamics conference, earthquake conference, construction management, structural dynamics, earthquake engineering, structural conference 2019, structural engineering conference, prague conference, construction, earthquake, earthquake engineering conference ---
Your payment has been successful!
We thank you very much for registering for ICSECT'19. An email has been sent to you confirming your payment to ICSECT'19. Please keep this email for your reference.
Please make sure you fill out and submit the registration form. Failing to fill out this form will result in the elimination of your registration.
You may find the registration form by following the link below:
Should you have any concerns, questions or comments, please do not hesitate to contact us at:
We are looking forward to seeing you at ICSECT'19!


--- layout: post status: publish published: true title: I Suck at WPF author: display_name: Tomas Restrepo login: tomasr email<EMAIL_ADDRESS>url: http://winterdom.com/ author_login: tomasr author_email<EMAIL_ADDRESS>author_url: http://winterdom.com/ wordpress_id: 553 wordpress_url: http://winterdom.com/2006/12/isuckatwpf date: '2006-12-03 18:20:49 +0000' date_gmt: '2006-12-03 18:20:49 +0000' categories: - WPF tags: [] comments: - id: 375 author: Bryant Likes author_email: '' author_url: http://blogs.sqlxml.org/bryantlikes date: '2006-12-04 12:36:42 +0000' date_gmt: '2006-12-04 12:36:42 +0000' content: | Looks like you're using the Zune theme? If so that is probably the issue of why the visual styles stopped working. See: http://notstatic.com/archives/56 - id: 376 author: Tomas Restrepo author_email<EMAIL_ADDRESS>author_url: http://www.winterdom.com/weblog/ date: '2006-12-04 12:40:55 +0000' date_gmt: '2006-12-04 12:40:55 +0000' content: | Bryant: Thanks, that's probably it. I could swear it worked before, but maybe I just don't remember correctly :) ---
Creating decent WPF applications is definitely hard for someone design-challenged as me. I've been trying to polish a small sample WPF client for a WCF service sample I've been playing with, and this is the best I've managed to come up with:
Ugly, isn't it?
Doesn't quite help the fact that, for some reason, the damn application just stopped using Visual Styles all of a suddent (don't know what's going on yet, but the controls are just not using the visual style anymore). Ohh well.