Sponsored Content
Top Forums Web Development managed service reccomendations Post 302253185 by edzillion on Friday 31st of October 2008 06:21:12 AM
Old 10-31-2008
managed service reccomendations

Dunno If its ok to post this, but I am looking for a company to manage our linux server. If the company is a specialist in security issues then that would be ideal

Thanks
Ed
 

7 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

FSCK on veritas managed disk

I've had a VXFS filesystem get corrupted and now it won't mount. Can I run a fsck -y on the raw disk device or should something be done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Discussion started by: ozzmosiz
2 Replies

2. Solaris

Smf managed service not starting

Hi Experts, While playing with smf in my local system ( which is not in production ) i am unable to restart the service svc:/network/nfs/server:default . I tried starting it in different way, however unable to restart the same. I was checking the dependency for that I disabled the... (11 Replies)
Discussion started by: kumarmani
11 Replies

3. Shell Programming and Scripting

Managed file transfer

Hello All, Firstly, the systems involved are Solaris 9/10 x86 and SPARC. At present, we have an internally written file transfer system that we use to manage incoming transfers and distribute the files to relevant processing systems. This is based on log watching. Over the years its become... (3 Replies)
Discussion started by: dcarrion87
3 Replies

4. AIX

[Tip] Using DHCP for Managed Systems Service Processors

This is a warning because we just went through searching for the error for some weeks. In many cases the managed systems (respectively their service processors) reside on their own network, together with the HMC(s) managing them. In this setup usually the HMC acts as DHCP server for the service... (0 Replies)
Discussion started by: bakunin
0 Replies

5. AIX

HEA configuration on managed node.

Folks, Please have a look to the attached screenshot from my managed node's HEA configuration option page. I would like to know - what does "Flow Control Enabled" checkbox help us with if opted for? Thanks! -- Souvik (3 Replies)
Discussion started by: thisissouvik
3 Replies

6. AIX

Managed system's uptime

How to find Physical server uptime from HMC/ ASMI. Server was in standby mode. We have started the Lpar manually. Server rebooted automatically but no information updated in Lpars's errpt, alog.console or HMC prior to the reboot. (1 Reply)
Discussion started by: sunnybee
1 Replies

7. Red Hat

Looking for Reccomendations to Clone RHEL 7

Hello, We are installing a group of stand-alone RHEL 7.1.3 servers for a new application in our environment. We are new to RHEL and would like to know what is the best way to clone the OS once we have the 1st install in the LAB with all the apps installed and passed all security checks. From... (3 Replies)
Discussion started by: Steve_9999
3 Replies
GIT-CHECK-MAILMAP(1)						    Git Manual						      GIT-CHECK-MAILMAP(1)

NAME
git-check-mailmap - Show canonical names and email addresses of contacts SYNOPSIS
git check-mailmap [options] <contact>... DESCRIPTION
For each "Name <user@host>" or "<user@host>" from the command-line or standard input (when using --stdin), look up the person's canonical name and email address (see "Mapping Authors" below). If found, print them; otherwise print the input as-is. OPTIONS
--stdin Read contacts, one per line, from the standard input after exhausting contacts provided on the command-line. OUTPUT
For each contact, a single line is output, terminated by a newline. If the name is provided or known to the mailmap, "Name <user@host>" is printed; otherwise only "<user@host>" is printed. MAPPING AUTHORS
If the file .mailmap exists at the toplevel of the repository, or at the location pointed to by the mailmap.file or mailmap.blob configuration options, it is used to map author and committer names and email addresses to canonical real names and email addresses. In the simple form, each line in the file consists of the canonical real name of an author, whitespace, and an email address used in the commit (enclosed by < and >) to map to the name. For example: Proper Name <commit@email.xx> The more complex forms are: <proper@email.xx> <commit@email.xx> which allows mailmap to replace only the email part of a commit, and: Proper Name <proper@email.xx> <commit@email.xx> which allows mailmap to replace both the name and the email of a commit matching the specified commit email address, and: Proper Name <proper@email.xx> Commit Name <commit@email.xx> which allows mailmap to replace both the name and the email of a commit matching both the specified commit name and email address. Example 1: Your history contains commits by two authors, Jane and Joe, whose names appear in the repository under several forms: Joe Developer <joe@example.com> Joe R. Developer <joe@example.com> Jane Doe <jane@example.com> Jane Doe <jane@laptop.(none)> Jane D. <jane@desktop.(none)> Now suppose that Joe wants his middle name initial used, and Jane prefers her family name fully spelled out. A proper .mailmap file would look like: Jane Doe <jane@desktop.(none)> Joe R. Developer <joe@example.com> Note how there is no need for an entry for <jane@laptop.(none)>, because the real name of that author is already correct. Example 2: Your repository contains commits from the following authors: nick1 <bugs@company.xx> nick2 <bugs@company.xx> nick2 <nick2@company.xx> santa <me@company.xx> claus <me@company.xx> CTO <cto@coompany.xx> Then you might want a .mailmap file that looks like: <cto@company.xx> <cto@coompany.xx> Some Dude <some@dude.xx> nick1 <bugs@company.xx> Other Author <other@author.xx> nick2 <bugs@company.xx> Other Author <other@author.xx> <nick2@company.xx> Santa Claus <santa.claus@northpole.xx> <me@company.xx> Use hash # for comments that are either on their own line, or after the email address. GIT
Part of the git(1) suite Git 1.8.5.3 01/14/2014 GIT-CHECK-MAILMAP(1)
All times are GMT -4. The time now is 10:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy