mesage "cannot ceate hardlink" when uploading var directory

Next topic

Author	Message
Vytautas Germanavičius	Wednesday 20 July 2005 6:45:47 am I made website with EZ on my computer (debian). When i uploading images from var/storege of this site using ftp to server i alway get message "cannot ceate hardlink". What is reason of this? {set-block scope=root variable=cache_ttl}0{/set-block}
Łukasz Serwatka	Tuesday 02 August 2005 11:42:52 pm Hi, There are two types of links in Unix: hard and symbolic. A hard link is a file that is, for all intents and purposes, the file to which it is linked. The difference between a hardlink and the linked file is one of placement in the filesystem. Editing the hardlink edits the linked file. One limitation of hard links is that linked files cannot reside on different filesystems. This means that if /var and /home are two different mount points in /etc/fstab (or /etc/vfstab), then a file in /var/tmp cannot be hardlinked with a file in /home These issues are not specific to eZ publish, but rather to the workings of a Unix system and FTP server configuration. Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Luc Chase	Wednesday 03 August 2005 12:51:56 am Vytis, might you be trying to upload to the wrong var directory?? The Web Application Service Provider

Author

Message

Wednesday 20 July 2005 6:45:47 am

I made website with EZ on my computer (debian).
When i uploading images from var/storege of this site using ftp to server i alway get message "cannot ceate hardlink".

What is reason of this?

{set-block scope=root variable=cache_ttl}0{/set-block}

Łukasz Serwatka

Tuesday 02 August 2005 11:42:52 pm

Hi,

There are two types of links in Unix: hard and symbolic.

A hard link is a file that is, for all intents and purposes, the file to which it is linked. The difference between a hardlink and the linked file is one of placement in the filesystem. Editing the hardlink edits the linked file. One limitation of hard links is that linked files cannot reside on different filesystems. This means that if /var and /home are two different mount points in /etc/fstab (or /etc/vfstab), then a file in /var/tmp cannot be hardlinked with a file in /home

These issues are not specific to eZ publish, but rather to the workings of a Unix system and FTP server configuration.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Luc Chase

Wednesday 03 August 2005 12:51:56 am

Vytis,
might you be trying to upload to the wrong var directory??

The Web Application Service Provider

eZ debug

Timing:	Jan 20 2025 05:53:25
Script start
Timing:	Jan 20 2025 05:53:25
Module start 'layout'
Timing:	Jan 20 2025 05:53:25
Module start 'content'
Timing:	Jan 20 2025 05:53:25
Module end 'content'
Timing:	Jan 20 2025 05:53:25
Script end

Main resources:

Total runtime	0.0256 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0058	589.6094	152.6563
Module start 'layout'	0.0058	0.0033	742.2656	39.4922
Module start 'content'	0.0091	0.0144	781.7578	89.4297
Module end 'content'	0.0235	0.0020	871.1875	34.3047
Script end	0.0255		905.4922

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	11.1821	14	0.0002
Check MTime	0.0013	5.0895	14	0.0001
Mysql Total
Database connection	0.0006	2.4557	1	0.0006
Mysqli_queries	0.0031	12.3064	3	0.0010
Looping result	0.0000	0.0382	1	0.0000
Template Total	0.0016	6.3	1	0.0016
Template load	0.0008	3.1913	1	0.0008
Template processing	0.0008	3.0701	1	0.0008
Override
Cache load	0.0006	2.1583	1	0.0006
General
dbfile	0.0047	18.4951	8	0.0006
String conversion	0.0000	0.0308	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs