Sponsored Content
The Lounge What is on Your Mind? Tips for hiring a Linux Application developer Post 302675945 by emerging_desk on Monday 23rd of July 2012 10:43:11 PM
Old 07-23-2012
Tips for hiring a Linux Application developer

I am looking to hire a Linux Application developer for my startup. But am having trouble screening for the right skill-set. What should I look for ? And, where do I find these developers who have experience in building applications for Linux?

Best,
E
 

5 More Discussions You Might Find Interesting

1. Red Hat

linux tips

Hi, I am working on a linux install to a desktop pc and will configure this onto our main server once happy with the functions etc. I am actually a HP and AIX sys admin and was looking for the best ways to: create a bootable file that can be copied to dvd-rw / cd-rw or to dds be able to... (8 Replies)
Discussion started by: chlawren
8 Replies

2. UNIX for Dummies Questions & Answers

iPhone and iPod touch application developer's thread

I am a complete noob when it comes to coding... If I could get some help with coding an iPhone or iPod touch application so I can learn the basics, that would be great. For now I want to make something simple that will take me only an hour or so... Basically, I'm not sure what to do... I started... (0 Replies)
Discussion started by: Nintenman
0 Replies

3. Red Hat

Tips to speed up Redhat linux machine

:confused:hi all, I run a virtual RedHat Linux 4.0 ES machine using VMWARE.I've allocated a RAM of 512Mb.Could you please provide suggestions/tips to get my machine to run faster.. Thanks in advance:) (4 Replies)
Discussion started by: tj23
4 Replies

4. UNIX for Dummies Questions & Answers

help to move from windows to linux as a developer

Hi, I am working as a c++/MFC developer from last 3 years on windows, recently i came across LINUX due to some small involvement in c++ projet @ linux platform. I really found it fascinated and found more challenging rather than developing the applications on windows. I really want to go more... (3 Replies)
Discussion started by: capoorhimanshu
3 Replies

5. Advertise with Us

Web Application Manager and Developer (India)

The UNIX and Linux Forums are looking for one or two web application developers in India. The position will be virtual and can be performed from anywhere with a high speed Internet connection. The following are the minimal qualifications: Education: University graduate in engineering, computer... (0 Replies)
Discussion started by: Neo
0 Replies
SKILL(1)							Linux User's Manual							  SKILL(1)

NAME
skill, snice - send a signal or report process status SYNOPSIS
skill [signal to send] [options] process selection criteria snice [new priority] [options] process selection criteria DESCRIPTION
These tools are probably obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep com- mands instead. The default signal for skill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP, CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL. The default priority for snice is +4. (snice +4 ...) Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority num- bers are restricted to administrative users. GENERAL OPTIONS
-f fast mode This is not currently useful. -i interactive use You will be asked to approve each action. -v verbose output Display information about selected processes. -w warnings enabled This is not currently useful. -n no action This only displays the process ID. -V show version Displays version of program. PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation. Do not blame Albert for this interesting interface. -t The next argument is a terminal (tty or pty). -u The next argument is a username. -p The next argument is a process ID number. -c The next argument is a command name. SIGNALS
The signals listed below may be available for use with skill. When known, numbers and default behavior are shown. Name Num Action Description 0 0 n/a exit code indicates if a signal may be sent ALRM 14 exit HUP 1 exit INT 2 exit KILL 9 exit this signal may not be blocked PIPE 13 exit POLL exit PROF exit TERM 15 exit USR1 exit USR2 exit VTALRM exit STKFLT exit may not be implemented PWR ignore may exit on some systems WINCH ignore CHLD ignore URG ignore TSTP stop may interact with the shell TTIN stop may interact with the shell TTOU stop may interact with the shell STOP stop this signal may not be blocked CONT restart continue if stopped, otherwise ignore ABRT 6 core FPE 8 core ILL 4 core QUIT 3 core SEGV 11 core TRAP 5 core SYS core may not be implemented EMT core may not be implemented BUS core core dump may fail XCPU core core dump may fail XFSZ core core dump may fail EXAMPLES
Command Description snice seti crack +7 Slow down seti and crack skill -KILL -v /dev/pts/* Kill users on new-style PTY devices skill -STOP viro lm davem Stop 3 users snice -17 root bash Give priority to root's shell SEE ALSO
killall(1), pkill(1), kill(1), renice(1), nice(1), kill(2), signal(7) STANDARDS
No standards apply. AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version, and is the current maintainer of the procps collection. Please send bug reports to <procps-feedback@lists.sf.net>. Linux March 12, 1999 SKILL(1)
All times are GMT -4. The time now is 07:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy