FreeSSHD SFTP Server
其实是有2个软件，一个是freeSSHd，一个是freeFTPd。
freeSSHd 的 sftp，所有用户只有一个 sftp 的主目录。
freeFTPd 的 sftp，可以给不同的用户设定不同的目录。
freeSSHd 可以设置系统账号、公钥、密码的登录方式，不像 xlight 只能在密码、公钥里二选一。
freeFTPd 可以设置系统账号、密码、匿名的登录方式。
月度归档： 2021年2月
执行yum update出现Cannot allocate memory错误
CentOS 6在进行yum update后出现如下错误，
Error in POSTIN scriptlet in rpm package libstdc++-4.4.7-23.el6.x86_64
error: Couldn't fork %post(libstdc++-4.4.7-23.el6.x86_64): Cannot allocate memory
Updating : pcre-7.8-7.el6.x86_64 5/239
Error in POSTIN scriptlet in rpm package pcre-7.8-7.el6.x86_64
error: Couldn't fork %post(pcre-7.8-7.el6.x86_64): Cannot allocate memory
Updating : grep-2.20-6.el6.x86_64 6/239
Error in POSTIN scriptlet in rpm package grep-2.20-6.el6.x86_64
error: Couldn't fork %post(grep-2.20-6.el6.x86_64): Cannot allocate memory
Updating : cpio-2.10-13.el6.x86_64 7/239
Error in POSTIN scriptlet in rpm package cpio-2.10-13.el6.x86_64
error: Couldn't fork %post(cpio-2.10-13.el6.x86_64): Cannot allocate memory
Updating : sysvinit-tools-2.87-6.dsf.el6.x86_64 8/239
Updating : tcp_wrappers-libs-7.6-58.el6.x86_64 9/239
Error in POSTIN scriptlet in rpm package tcp_wrappers-libs-7.6-58.el6.x86_64
error: Couldn't fork %post(tcp_wrappers-libs-7.6-58.el6.x86_64): Cannot allocate memory
Updating : 1:findutils-4.4.2-9.el6.x86_64 10/239
Error in POSTIN scriptlet in rpm package 1:findutils-4.4.2-9.el6.x86_64
error: Couldn't fork %post(findutils-1:4.4.2-9.el6.x86_64): Cannot allocate memory
Updating : sqlite-3.6.20-1.el6_7.2.x86_64 11/239
Error in POSTIN scriptlet in rpm package sqlite-3.6.20-1.el6_7.2.x86_64
error: Couldn't fork %post(sqlite-3.6.20-1.el6_7.2.x86_64): Cannot allocate memory
Updating : nss-softokn-3.14.3-23.3.el6_8.x86_64 12/239
Error in POSTIN scriptlet in rpm package nss-softokn-3.14.3-23.3.el6_8.x86_64
error: Couldn't fork %post(nss-softokn-3.14.3-23.3.el6_8.x86_64): Cannot allocate memory
Updating : libtasn1-2.3-6.el6_5.x86_64 13/239
Error in POSTIN scriptlet in rpm package libtasn1-2.3-6.el6_5.x86_64
error: Couldn't fork %post(libtasn1-2.3-6.el6_5.x86_64): Cannot allocate memory
Updating : p11-kit-0.18.5-2.el6_5.2.x86_64 14/239
Error in POSTIN scriptlet in rpm package p11-kit-0.18.5-2.el6_5.2.x86_64
error: Couldn't fork %post(p11-kit-0.18.5-2.el6_5.2.x86_64): Cannot allocate memory
Updating : p11-kit-trust-0.18.5-2.el6_5.2.x86_64 15/239
Error in POSTIN scriptlet in rpm package p11-kit-trust-0.18.5-2.el6_5.2.x86_64
error: Couldn't fork %post(p11-kit-trust-0.18.5-2.el6_5.2.x86_64): Cannot allocate memory
Updating : less-436-13.el6.x86_64 16/239
Updating : gmp-4.3.1-13.el6.x86_64 17/239
Error in POSTIN scriptlet in rpm package gmp-4.3.1-13.el6.x86_64
error: Couldn't fork %post(gmp-4.3.1-13.el6.x86_64): Cannot allocate memory
Updating : device-mapper-persistent-data-0.6.2-0.2.rc7.el6.x86_64 18/239
Updating : 1:make-3.81-23.el6.x86_64 19/239
Error in POSTIN scriptlet in rpm package 1:make-3.81-23.el6.x86_64
error: Couldn't fork %post(make-1:3.81-23.el6.x86_64): Cannot allocate memory
Updating : gdbm-1.8.0-39.el6.x86_64 20/239
Error in POSTIN scriptlet in rpm package gdbm-1.8.0-39.el6.x86_64
error: Couldn't fork %post(gdbm-1.8.0-39.el6.x86_64): Cannot allocate memory
Updating : plymouth-core-libs-0.8.3-29.el6.centos.x86_64 21/239
Segmentation fault找了一圈后，找到结局方案，具体如下：
编辑 /etc/sysctl.conf ，改vm.overcommit_memory=1，然后sysctl -p 使配置文件生效
vi /etc/sysctl.conf修改/添加
vm.overcommit_memory=1Esc 退出 :wq 保存
然后sysctl -p 使配置文件生效
CentOS 6下域名yum命令报错YumRepo Error: All mirror URLs are not using
CentOS6已经在2020年11月30日停止维护了。centos官方停止了对centos6的所有更新，并且下架了包括官方所有的centos6源，目前阿里、163、清华等centos6源已无法使用。
CentoS 6 停止维护更新日期：2020年11月30日
CentOS 7 停止维护更新日期：2024年6月
CentOS 8 停止维护更新日期：2029年5月
1、输入下面命令，切换到root用户
su root2、备份配置文件，防止以后出错后不好修复
mv /etc/yum.repos.d/CentOS-Base.repo /etc/yum.repos.d/CentOS-Base.repo.backup3、执行下面命令，新建CentOS-Base.repo配置，复制粘贴如下命令
vim /etc/yum.repos.d/CentOS-Base.repo[centos-office]
name=centos-office
failovermethod=priority
baseurl=https://vault.centos.org/6.10/os/x86_64/
gpgcheck=1
gpgkey=https://vault.centos.org/6.10/os/x86_64/RPM-GPG-KEY-CentOS-64、按Ecs键后:wq保存并退出
5、正常啦~
使用Powershell将多个csv文件转换为多个工作簿的Excel文件
从SQLSERVER数据库通过脚本将数据导出成为CSV文件后，就需要将数据合并为多个工作簿的Excel文件，具体代码如下，大家可以参阅一下。
$path="D:\TestFold" #target folder
cd $path;
$csvs = Get-ChildItem .\* -Include *.csv
$y=$csvs.Count
Write-Host "Detected the following CSV files: ($y)"
foreach ($csv in $csvs)
{
Write-Host "—"$csv.Name
}
$outputfilename = $(get-date -f yyyyMMdd) + "_" + "-data.xlsx" #creates file name with date/username
Write-Host Creating: $outputfilename
$excelapp = new-object -comobject Excel.Application
$excelapp.sheetsInNewWorkbook = $csvs.Count
$xlsx = $excelapp.Workbooks.Add()
$sheet=1
foreach ($csv in $csvs)
{
$row=1
$column=1
$worksheet = $xlsx.Worksheets.Item($sheet)
$worksheet.Name = $csv.Name
$file = (Get-Content $csv)
foreach($line in $file)
{
$linecontents=$line -split ',(?!\s*\w+")'
foreach($cell in $linecontents)
{
$worksheet.Cells.Item($row,$column) = $cell
$column++
}
$column=1
$row++
}
$sheet++
}
$output = $path + "\" + $outputfilename
$xlsx.SaveAs($output)
$excelapp.quit()
cd \ #returns to drive rootPowershell脚本在计划任务中处理产生的Excel文件失败的解决方法
PowerShell脚本在PowerShell ISE中执行一切都正常，但是将脚本加入到Windows的计划任务中就出现无法处理Excel文件的问题，最后在网上找到一个方法，在system32目录下创建Destop目录就可以解决相关问题，遇到这样问题的朋友可以试试。
(32位系统&64位系统)
C:\Windows\System32\config\systemprofile\Desktop
(64位系统)
C:\Windows\SysWOW64\config\systemprofile\Desktop原文：
Interactive Excel permissions
Stumbled upon an interesting one today, where I had a legacy application that needs to open excel to generate some excel spreadsheets. But when this happened i got the usual error:
System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Office Excel cannot access the file 'c:\temp\test.xls'. There are several possible reasons:
• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open workbook.
For this example the application is running under an application pool account called ExcelAppPoolAct
Obviously the first step is to grant the correct permissions in component services. To do this:
- Navigation to Adminstrative Tools->Component Services->MyComputer->DCOM->Microsoft Excel Application
- Right Click on Microsoft Excel Application and select Properties
- Click the Security tab
- Change Launch and Activation Permissions to Customize
- Click Edit
- Add ExcelAppPoolAct
- Check Local Launch and Local Activation
Next we need to configure the systemprofile directory. You need to create a Desktop folder in one of the following paths, dependant on which version (32-bit or 64-bit) of Microsoft Office you are running.
| Office Version | Folder |
|---|---|
| 32-bit | C:\Windows\System32\config\ systemprofile\ |
| 64-bit | C:\Windows\SysWOW64\config\systemprofile\ |
The next step is to configure the appropriate permissions to thefolders for the Application Pool account, ExcelAppPoolAct. Again the folder is dependent on your version (32-bit or 64-bit) of Microsoft Office.
| Folder | Required Permission |
|---|---|
| C:\Windows\System32\config\systemprofile\Desktop | Read & Execute, List folder contents, Read |
| C:\Windows\System32\config\systemprofile\AppData\Roaming\Microsoft | Modify, Read & Execute, List Folder Content, Read, Write |
| C:\Windows\System32\config\systemprofile\AppData\Local\Microsoft | Modify, Read & Execute, List Folder Content, Read, Write |
| Folder | Required Permission |
|---|---|
| C:\Windows\SysWOW64\config\systemprofile\Desktop | Read & Execute, List folder contents, Read |
| C:\Windows\SysWOW64\config\systemprofile\AppData\Roaming\Microsoft | Modify, Read & Execute, List Folder Content, Read, Write |
| C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft | Modify, Read & Execute, List Folder Content, Read, Write |
I've got a nice piece of powershell that does all of this during installation.