[Pardus-kullanicilari] gmailfs problemi
Erkan Altan
ealt78 at gmail.com
13 Şub 2008 Çar 22:17:47 EET
09.02.2008 tarihinde Necmettin Begiter <necmettin.begiter at gmail.com> yazmış:
>
> Merhabalar ve kolay gelsin,
>
> gmailfs ile Gmail hesabımı yerele bağlamaya çalışıyorum, hem ev dizininde
> .gmailfs ile
> hem de /etc/gmailfs.conf ile denedim, kullanıcı adı olarak @gmail.comkısmını yazmadan
> deniyorum, doğru mu yapıyorum (Aslında iki şekilde de denedim)?
> mount.gmailfs none .
> komutunu ~/baglar/gmail dizininde verdiğimde şöyle bir hata alıyorum:
>
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
> Traceback (most recent call last):
> File "/usr/lib/python2.4/logging/handlers.py", line 73, in emit
> if self.shouldRollover(record):
> File "/usr/lib/python2.4/logging/handlers.py", line 147, in
> shouldRollover
> self.stream.seek(0, 2) #due to non-posix-compliant Windows feature
> IOError: [Errno 29] Illegal seek
>
>
> Ancak mount ile bağlı disklere baktığımda
> python on /home/necmettin/baglar/gmail type fuse (rw,nosuid,nodev)
> görüyorum.
>
> umount python dediğimde ise bazen aygıt meşgul hatası veriyor, sync
> komutunu
> verdikten sonra bağı kaldırabiliyorum.
>
mount öncesinde
"modprobe fuse" yapmak gerekebilir. Bunu yapıyorsanız mount komutu
sonrasında
"cat ~/gmailfs.log"
komutunun çıktısı hataya ilişkin daha doğru düzgün b ilgi verebilir.
benim sorunsuz olarak kullandığım "/etc/gmailfs.conf" dosyası içeriğini
aşağıya yapıştırdım kullanıcı adı ve şifreyi kendinize göre değiştirin. Ben
kullanıcı adında "@gmail.com" kısmını yazmadan bağlanıyorum.
[connection]
# The proxy URL
#proxy = http://user:pass@proxyhost:port
# or just
#proxy = http://proxyhost:port
# The number or retries for the proxy connection.
#retries = 3
[account]
username = KULLANICIADI
password = SIFRE
[filesystem]
fsname = linux_fs_3
[references]
# reference = filesystem:username:password
[logs]
# Change this to DEBUG for verbose output (useful for debugging)
level = INFO
# if you'd like logs to go to stdout, comment out this variable.
# For logging to, say, stderr, use /dev/stderr of your system's
# equivalent for it
logfile = ~/gmailfs.log
Kolaylıklar,
-------------- sonraki bölüm --------------
Bir HTML eklentisi temizlendi...
URL: http://liste.pardus.org.tr/pardus-kullanicilari/attachments/20080213/88111bb0/attachment.htm
Pardus-kullanicilari mesaj listesiyle ilgili
daha fazla bilgi