On Sat, Nov 04, 2006 at 03:30:19PM +0100, Ludovic Rousseau wrote:
> [24 lines, 90 words, 682 characters] Top characters: *eoti\nnu
>
> Le 04.11.2006, à 08:23:01, Jeff Abrahamson a écrit:
> > On Sat, Nov 04, 2006 at 11:24:26AM +0100, Ludovic Rousseau wrote:
> > > What communication port is configured in jpilot?
> >
> > /dev/ttyS0
>
> On a previous mail your logs have:
> ****************************************
> Syncing on device /dev/pilot
> Press the HotSync button now
> ****************************************
>
> So I don't think you have /dev/ttyS0 configured in jpilot but /dev/pilot
> instead.
>
> Execute:
> $ grep 'port ' ~/.jpilot/jpilot.rc
> and send me the result.
It was incorrect for my test user (def), correct for me (jeff). In
any case, /dev/pilot currently points to /dev/ttyS0, a just-in-case
measure I took in trying to fix the problem. Setting correctly for
dev and trying again yields the same results:
[EMAIL PROTECTED]:~$ ls -l /dev/pilot
lrwxrwxrwx 1 root root 5 Nov 3 11:23 /dev/pilot -> ttyS0
[EMAIL PROTECTED]:~$ grep 'port ' ~/.jpilot/jpilot.rc
port /dev/ttyS0
[EMAIL PROTECTED]:~$ jpilot -d
Debug messages on.
calling check_hidden_dir
pidfile: /home/dev/.jpilot/jpilot.pid
opening dir /usr/lib/jpilot/plugins/
found plugin libbackup.so
opened plugin [/usr/lib/jpilot/plugins/libbackup.so]
This plugin is version (0.99).
getting plugin_get_name
getting plugin_get_menu_name
getting plugin_get_help_name
getting plugin_get_db_name
plugin name is [Backup 0.53]
opening dir /home/dev/.jpilot/plugins/
plugin: [Backup 0.53] was loaded
calling plugin_startup for [Backup 0.53]
Backup: plugin_startup
calling check_backup_dir
Trying to open /home/dev/.jpilot/Backup/test for write
Backup: Loading prefs
Backup: loaded preferences from backup.rc
rc file from prefs is jpilotrc.default
parsing /usr/share/jpilot/jpilotrc.default
parse_geometry()
get_todos2()
Entering jp_read_DB_files: ToDoDB
Leaving jp_read_DB_files
Leaving get_todos2()
entries_shown=0
set_new_button_to new 1 old 1
datebook_update_clist()
get_days_appointments()
Entering jp_read_DB_files: DatebookDB
Leaving jp_read_DB_files
Leaving get_days_appointments()
get_days_appointments==>0
datebook_category = 0xffff
set_new_button_to new 1 old 1
get_days_appointments()
Entering jp_read_DB_files: DatebookDB
Leaving jp_read_DB_files
Leaving get_days_appointments()
datebook_find(), glob_find_id = 0
x=900, y=410
w=908, h=1121
alarms_init()
UPTODATE 2006 11 4 11 32
alarms_find_next()
get_days_appointments()
Entering jp_read_DB_files: DatebookDB
Leaving jp_read_DB_files
Leaving get_days_appointments()
alarms_write_file()
jp_pref_write_rc_file()
cb_check_version
jp_pref_write_rc_file()
setting PILOTRATE=[9600]
pref port=[/dev/ttyS0]
num_backups=2
forking sync process
sync:calling load_plugins
opening dir /usr/lib/jpilot/plugins/
found plugin libbackup.so
opened plugin [/usr/lib/jpilot/plugins/libbackup.so]
This plugin is version (0.99).
getting plugin_get_name
getting plugin_get_menu_name
getting plugin_get_help_name
getting plugin_get_db_name
plugin name is [Backup 0.53]
opening dir /home/dev/.jpilot/plugins/
****************************************
Syncing on device /dev/ttyS0
Press the HotSync button now
****************************************
dlp_ReadSysInfo error
Exiting with status SYNC_ERROR_PI_CONNECT
Finished
sync child exiting
caught signal SIGCHLD
x=900, y=410
jp_pref_write_rc_file()
jp_pref_write_rc_file()
jp_pref_write_rc_file()
calling plugin_exit_cleanup
plugin_exit_cleanup()
jp_pref_write_rc_file()
cleanup_pc_file for DatebookDB
No compacting needed
max_id was 0
cleanup_pc_file for AddressDB
No compacting needed
max_id was 0
cleanup_pc_file for ToDoDB
No compacting needed
max_id was 0
cleanup_pc_file for MemoDB
No compacting needed
max_id was 0
cleanup_pc_file for Memo32DB
No compacting needed
max_id was 0
not calling cleanup_pc_file for: []
[EMAIL PROTECTED]:~$
--
Jeff
Jeff Abrahamson <http://jeff.purple.com/> +1 215/837-2287
GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
